* @param settings The suggest settings.
     * @param threadPool The thread pool.
     */
    public SuggestIndexer(final Client client, final String index, final ReadingConverter readingConverter,
            final ReadingConverter contentsReadingConverter, final Normalizer normalizer, final SuggestAnalyzer analyzer,
            final SuggestSettings settings, final ExecutorService threadPool) {
        this.client = client;

    ExecutorService threadPool = newFixedThreadPool(nThreads);
    CountDownLatch tasksFinished = new CountDownLatch(nTasks);
    for (int i = 0; i < nTasks; i++) {
      String s = "a" + i;
      @SuppressWarnings("unused") // https://errorprone.info/bugpattern/FutureReturnValueIgnored
      Future<?> possiblyIgnoredError =
          threadPool.submit(
              new Runnable() {

        ForkJoinPool pool1 = new ForkJoinPool(2);
        ForkJoinPool pool2 = new ForkJoinPool(4);

        // Multiple threadPool calls should work
        request.threadPool(pool1);
        request.threadPool(pool2);

        assertNotNull(request);
    }

    @Test
    public void testOnConnectWithNull() {

        connected = false;
    }

    /**
     * Gets the thread pool from the underlying client.
     *
     * @return The thread pool.
     */
    @Override
    public ThreadPool threadPool() {
        return client.threadPool();
    }

    /**
     * Gets the admin client for cluster and index operations.
     *
     * @return The admin client.
     */
    @Override

///

### Funciones de *path operation* { #path-operation-functions }

Cuando declaras una *path operation function* con `def` normal en lugar de `async def`, se ejecuta en un threadpool externo que luego es esperado, en lugar de ser llamado directamente (ya que bloquearía el servidor).

  // TODO(b/113217601): This is needed for EagerContext::runner_ to use a
  // threadpool, so that we avoid the possibility of running the runner_ in the
  // threadpool of GPU event mgr, as that can trigger more callbacks to be
  // scheduled on that same threadpool, causing a deadlock in cases where the
  // caller of event_mgr->ThenExecute() blocks on the completion of the callback

///

### Funções de operação de rota { #path-operation-functions }

Quando você declara uma *função de operação de rota* com `def` normal ao invés de `async def`, ela é rodada em uma threadpool externa que é então aguardada, ao invés de ser chamada diretamente (já que ela bloquearia o servidor).

///

### Path operation functions { #path-operation-functions }

When you declare a *path operation function* with normal `def` instead of `async def`, it is run in an external threadpool that is then awaited, instead of being called directly (as it would block the server).

///

### Fonctions de chemin

Quand vous déclarez une *fonction de chemin* avec un `def` normal et non `async def`, elle est exécutée dans un groupe de threads (threadpool) externe qui est ensuite attendu, plutôt que d'être appelée directement (car cela bloquerait le serveur).

///

### Pfadoperation-Funktionen { #path-operation-functions }

Wenn Sie eine *Pfadoperation-Funktion* mit normalem `def` anstelle von `async def` deklarieren, wird sie in einem externen Threadpool ausgeführt, der dann `await`et wird, anstatt direkt aufgerufen zu werden (da dies den Server blockieren würde).