Replies: 1 comment
-
|
Sorry, I'll fix the link, that notebook is now at: https://github.com/Azure/azure-search-vector-samples/blob/main/demo-python/code/integrated-vectorization/azure-search-integrated-vectorization-sample.ipynb Our RAG app indexes JSON by chunking them and storing chunks in the content field. That works fairly well from our tests (and for the customer who that was originally written for). However, there may be situations where you'd also want to store metadata or structure, or you want to specifically map one JSON to an index. If you went that route, you'd need to decide how you were going to translate user queries into searches on more complex structure, however. I present one approach here: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Data ingestion page has link to this notebook with additional detail for document indexing but the notebook page is 404.
The other samples page says JSON document indexing is not part of existing functionality:

Although if you present JSON document azure-search-openai-demo is capable of indexing them however it doesn't create an index using the JSON structure (even if only JSON documents of the same structure are present) instead it creates the default index with 2 fields (content & embeddings).
@pamelafox is my understanding incorrect (based on reading of how to index JSON blobs ) .... in that the index should create fields as per JSON structure? Can you advise which file(s) index creation is found?
Beta Was this translation helpful? Give feedback.
All reactions