// The iterator returns null when no elements, doesn't throw exception
        assertNull(iterator.next(), "Should return null when no next element");
    }

    /**
     * Test multiple iterations with mixed filtering results.
     */
    @Test
    void testMultipleIterationsWithFilter() throws Exception {
        // Given
        when(mockDelegate.hasNext()).thenReturn(true, true, true, false);

- [Use `mc` with MinIO Server](https://docs.min.io/community/minio-object-store/reference/minio-mc.html)
- [Use `aws-cli` with MinIO Server](https://docs.min.io/community/minio-object-store/integrations/aws-cli-with-minio.html)
- [Use `minio-go` SDK with MinIO Server](https://docs.min.io/community/minio-object-store/developers/go/minio-go.html)

The first part of the communication is just to establish the connection between the client and the server and to decide the cryptographic keys they will use, etc.

<img src="/img/deployment/https/https02.drawio.svg">

This interaction between the client and the server to establish the TLS connection is called the **TLS handshake**.

### TLS with SNI Extension { #tls-with-sni-extension }

      ListenableFuture<?> unused = serializer.submitAsync(() -> settableFuture, directExecutor());
      for (int i = 0; i < 50_000; i++) {
        if (i % DIRECT_EXECUTIONS_PER_THREAD == 0) {
          // after some number of iterations, switch threads
          unused =
              serializer.submit(
                  () -> {
                    holder.count++;
                    return null;
                  },

HDFS atomic rename functionality to complete writing data to the datastore. Object storage operations are atomic by nature and they do not require/implement rename API. The default S3A committer emulates renames through copy and delete APIs. This interaction pattern causes significant loss of performance because of the write amplification. _Netflix_, for example, developed two new staging committers - the Directory staging committer and the Partitioned staging committer - to take full advantage of native...

    /**
     * Flag indicating whether the client has been initialized.
     */
    protected volatile boolean isInit = false;

    /**
     * The GCS Storage client instance for interacting with Google Cloud Storage.
     */
    protected Storage storage;

    /**
     * Creates a new GcsClient instance.
     */
    public GcsClient() {
        super();
    }

    @Override

### 自动生成文档 { #automatic-docs }

交互式 API 文档以及具探索性 web 界面。因为该框架是基于 OpenAPI，所以有很多可选项，FastAPI 默认自带两个交互式 API 文档。

* [**Swagger UI**](https://github.com/swagger-api/swagger-ui)，可交互式操作，能在浏览器中直接调用和测试你的 API。

![Swagger UI interaction](https://fastapi.tiangolo.com/img/index/index-03-swagger-02.png)

* 另外的 API 文档：[**ReDoc**](https://github.com/Rebilly/ReDoc)

![ReDoc](https://fastapi.tiangolo.com/img/index/index-06-redoc-02.png)

## Üçüncü taraf entegrasyonları hakkında { #about-third-party-integrations }

Bu örnekte OAuth2 "password" flow'unu kullanıyoruz.

Bu, kendi uygulamamıza giriş yaptığımız durumlar için uygundur; muhtemelen kendi frontend'imiz vardır.

    @Resource
    protected LabelTypeBhv labelTypeBhv;

    /** Configuration settings for Fess application */
    @Resource
    protected FessConfig fessConfig;

    /** Client for interacting with the search engine */
    @Resource
    protected SearchEngineClient searchEngineClient;

    /**
     * Retrieves a paginated list of elevate words based on the provided pager criteria.
     *

### 能夠自動生成文件 { #automatic-docs }

FastAPI 能生成互動式 API 文件和探索性的 Web 使用者介面。由於該框架基於 OpenAPI，因此有多種選擇，預設提供了兩種。

* [**Swagger UI**](https://github.com/swagger-api/swagger-ui) 提供互動式探索，讓你可以直接從瀏覽器呼叫並測試你的 API 。

![Swagger UI interaction](https://fastapi.tiangolo.com/img/index/index-03-swagger-02.png)

* 使用 [**ReDoc**](https://github.com/Rebilly/ReDoc) 的替代 API 文件。

![ReDoc](https://fastapi.tiangolo.com/img/index/index-06-redoc-02.png)