-
Notifications
You must be signed in to change notification settings - Fork 31
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
176 descriptor set optimizations under constrained knn query is inefficient #220
176 descriptor set optimizations under constrained knn query is inefficient #220
Conversation
…descriptor use new ID property names
Target CPP Coverage: 63.9716% Target Python Coverage: 98.02% |
Target CPP Coverage: 63.9716% Target Python Coverage: 98.02% |
Target CPP Coverage: 63.9716% Target Python Coverage: 98.02% |
Target CPP Coverage: 63.9716% Target Python Coverage: 98.02% |
Target CPP Coverage: 64.0287% Target Python Coverage: 98.02% |
@@ -785,23 +784,25 @@ def test_findDescByBlobWithLink(self): | |||
all_queries.append(query) | |||
|
|||
response, blob_array = db.query(all_queries, [descriptor_blob]) | |||
self.assertEqual(response[0]["status"], -1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still need test_findDescByBlobWithLink since we no longer have capability to link the knn search using _ref? This is basically just a AddDescriptor/AddEntity test now. Or should we change KNN search to search by constraints to leverage defined _ref?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question, left it in for the moment for us to discuss. It does technically exercise a slightly different path above when its doing its setup, but the search itself is mostly a repeat of the early KNN test.
Target CPP Coverage: 64.0287% Target Python Coverage: 98.02% |
Target CPP Coverage: 64.0287% Target Python Coverage: 98.02% |
Target CPP Coverage: 64.0287% Target Python Coverage: 98.02% |
Target CPP Coverage: 64.0287% Target Python Coverage: 98.02% |
Target CPP Coverage: 64.0287% Target Python Coverage: 98.02% |
Target CPP Coverage: 64.0287% Target Python Coverage: 98.02% |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All looks good!
No description provided.