-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to upload data with DI in portal? #1604
Comments
Just wondering did you check below: https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/docs/data_ingestion.md specifically indexing additional documents section. Maybe this is what you are looking for? |
Hi @zedhaque Yes I read the indexing additional documents section. I saw that there is an index called "gptkbindex" created and I also upload new PDF files in the blob container "content" folder(the sample PDFs were all uploaded to here). |
Just to confirm - when you click on the "indexer" in the AI Search menu item - nothing is there/it's an empty page? and your .env has below item as true: correct? Not sure why the indexer and scheduler didn't get created. (https://learn.microsoft.com/en-us/azure/search/vector-search-integrated-vectorization). You could set up the schedular in the portal manually and see if it picks up the document that you uploaded earlier. |
I had a similar question like the original poster here, demo creates an index automatically question is how to index documents that are directly uploaded to storage containers. I know that scheduling indexing requires setting up a new indexer, but how to associate the indexer to the existing index and make sure new documents or updates to existing pdfs are automatically reindexed and made available in chatApp. |
interested to know this as well. i am getting auth issues trying to index locally by running |
This issue is for a: (mark with an
x
)Minimal steps to reproduce
Any log messages given by the failure
Expected/desired behavior
OS and Version?
azd version?
Versions
Mention any other details that might be useful
The text was updated successfully, but these errors were encountered: