# Maximum document cache size for data in the indexer.
indexer.data.max.document.cache.size=10000
# Maximum document request size (bytes) for data in the indexer.
indexer.data.max.document.request.size=1048576
# Maximum delete cache size for data in the indexer.
indexer.data.max.delete.cache.size=100
# Maximum redirect count for data in the indexer.
indexer.data.max.redirect.count=10

...entonces, porque `description` tiene un valor por defecto, si **no devuelves nada** para ese campo, aún tendrá ese **valor por defecto**.

### Modelo para Datos de Response de Salida { #model-for-output-response-data }

Si interactúas con la documentación y revisas el response, aunque el código no agregó nada en uno de los campos `description`, el response JSON contiene el valor por defecto (`null`):

labels.crawling_info_DataCrawlStartTime=Hora de inicio del rastreo (Almacén de datos)
labels.crawling_info_DataCrawlEndTime=Hora de finalización del rastreo (Almacén de datos)
labels.crawling_info_DataIndexExecTime=Tiempo de ejecución de indexación (Almacén de datos)
labels.crawling_info_DataIndexSize=Tamaño del índice (Almacén de datos)
labels.webauth_configuration=Autenticación web

        assertNotNull(extraFieldNames);
        assertTrue(extraFieldNames.contains("custom_tags"), "Config-defined array field should appear even without doc data");
        assertTrue(extraFieldNames.contains("custom_publish_date"), "Config-defined date field should appear even without doc data");

        @SuppressWarnings("unchecked")

of `--older-than` needs to be used to trigger re-syncing of previously replicated objects. This command generates a ResetID which is a unique UUID saved to the remote target config along with the applicable date(defaults to time of initiating the reset). All objects created prior to this date are eligible for re-replication if existing object replication is enabled for the replication rule the object satisfies. At the time of completion of replication, `x-minio-internal-replication-reset-arn:<arn>`...

labels.crawling_info_DataCrawlExecTime=Crawl Execution Time (Data Store)
labels.crawling_info_DataCrawlStartTime=Crawl Start Time (Data Store)
labels.crawling_info_DataCrawlEndTime=Crawl End Time (Data Store)
labels.crawling_info_DataIndexExecTime=Indexing Execution Time (Data Store)
labels.crawling_info_DataIndexSize=Index Size (Data Store)
labels.webauth_configuration=Web Authentication

import org.gradle.util.internal.VersionNumber
import org.jetbrains.annotations.VisibleForTesting
import org.jsoup.Jsoup

/**
 * Fetch the latest AGP versions and write a properties file.
 * Never up-to-date, non-cacheable.
 *
 * AGP major versions are aligned with Gradle major versions.
 * IOW, AGP X.y officially only supports Gradle X.z.
 *
 * This task leverages that alignment to automatically select which

  }

  /**
   * For Last-Modified and Date headers, we should echo the date back in the exact format we were
   * served.
   */
  @Test
  fun retainServedDateFormat() {
    // Serve a response with a non-standard date format that OkHttp supports.
    val lastModifiedDate = Date(System.currentTimeMillis() + TimeUnit.HOURS.toMillis(-1))
    val servedDate = Date(System.currentTimeMillis() + TimeUnit.HOURS.toMillis(-2))

sería válida para usar como una dependencia en **FastAPI**.

De hecho, FastAPI usa esos dos decoradores internamente.

///

## Una dependencia de base de datos con `yield` { #a-database-dependency-with-yield }

Por ejemplo, podrías usar esto para crear una sesión de base de datos y cerrarla después de finalizar.

Solo el código anterior e incluyendo el `yield` statement se ejecuta antes de crear un response:

Como parte disso, eu precisava investigar, testar e usar muitas alternativas.

A história do **FastAPI** é, em grande parte, a história de seus predecessores.

Como dito na seção [Alternativas](alternatives.md):

<blockquote markdown="1">

**FastAPI** não existiria se não pelo trabalho anterior de outros.

Há muitas ferramentas criadas antes que ajudaram a inspirar sua criação.