-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
query endpoint not returning data with Milvus #61
Comments
This could be related with #51 |
Could you add a filter to the query and try again?
Also, check the zip and extracted docs are adding the right source type, like #32 |
1 similar comment
Could you add a filter to the query and try again?
Also, check the zip and extracted docs are adding the right source type, like #32 |
Pulled latest changes and retested, not working as I would expect (no results). I tried changing the query string to all sorts of things like "This is an example markdown document", "example" etc. No dice. Not getting any results. Import process
Server running
|
@filip-halt Are you able to comment on this? How did you verify it working locally? |
@nkeilar Did you set the environment variable MILVUS_COLLECTION? The script directly connects to the vector store, it doesn't use the poetry server. I just tested it and it worked. If the collection isn't set, the server will run on its own uuid named collection and the script will push data into another uuid named collection. |
@filip-halt thank you! That was indeed the issue. I can confirm after setting MILVUS_COLLECTION=somevalue for poetry server and also scripts/process_zip/process_zip.py it works as expected. Recommendation: That we improve the documentation, as it appears to be an optional argument, which while may be true for the server, if not specified when importing data then data is imported somewhere random. Perhaps instead of a random UUID the defaults could be set to be the same for the script and server when using milvus. I'm happy to make the change. Will just leave the comment here for a couple of days in case anyone has an opinion on best way to avoid others falling into this trap. |
I set the name to be randomly generated as running the server twice or running two separate instances of retrieval on the same milvus server would result in shared data. I think a better route would be to have the scripts use the poetry server instead of creating their own DataStore instance. What do you think @isafulf ? |
oh man, i have the same trouble like you , when i post a document and query it , it's return well, when i restart the api , nothing return you notice me,
when i restart the api , the uuid has changes |
@lastrei Ill see if I can add something into the documentation. I picked this route due to it being a lesser of two evils. If I hardcoded a value, then the information stores could clash if people share the Milvus server or if wanting to use two separate retrieval services. |
you are right ,hard code may cause these problems , but the code must save the connection name .. i write them in to a json file with connection name and Description |
I've setup the project locally, inserted the example zip file using the Milvus datastore.
When I run a query command in Postman I'm not getting any results. Am I missing something?
Starting application
process_zip
Query
The text was updated successfully, but these errors were encountered: