Hello lakshmi,
Both indexers are required. The openai-indexer-chunk
divides the data into small chunks with a maximum of 1,024 tokens, and the other openai-indexer
writes the preprocessed data into Azure AI Search.
This is mentioned in the Microsoft Learn document.
How data is ingested into Azure AI search
Data is ingested into Azure AI search using the following process:
- Ingestion assets are created in Azure AI Search resource and Azure storage account. Currently these assets are: indexers, indexes, data sources, a custom skill in the search resource, and a container (later called the chunks container) in the Azure storage account. You can specify the input Azure storage container using the Azure OpenAI studio, or the ingestion API (preview).
- Data is read from the input container, contents are opened and chunked into small chunks with a maximum of 1,024 tokens each. If vector search is enabled, the service calculates the vector representing the embeddings on each chunk. The output of this step (called the "preprocessed" or "chunked" data) is stored in the chunks container created in the previous step.
- The preprocessed data is loaded from the chunks container, and indexed in the Azure AI Search index.
Best regards,
Charlie
If you find my response helpful, please consider accepting this answer
and voting yes
to support the community. Thank you!