-
Notifications
You must be signed in to change notification settings - Fork 982
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
Add Facets#getSpecificValues (bulk) and bulk path -> ordinal lookup for taxonomy faceting #12180
Comments
Hi, the commit causes test failures like this from time to time:
And hundreds of more threads following. Looks like sometimes the ordinals array is initialized by zero length. The followup random then fail because the upper bound passed to |
OK fixed @uschindler -- sorry! |
And thanks @epotyom! |
Thanks @epotyom! Should we consider a follow up PR that leverages this new bulk lookup by adding something like |
@gsmiller yes, I'll be working on that now as well as adding benchmark task for getSpecificValues, as was discussed with Mike in #12769 (review) . |
@epotyom got it, thanks! Didn't see that earlier conversation. |
Hi, I'd like to ask a clarifying question as part of the 9.9.0 release manager duties, since this currently-unresolved issue is associated with Milestone 9.9.0. It's clear that progress has been made on this issue, with the addition of the new |
Thanks @ChrisHegarty -- this one is done. |
Sorry for confusion, but this issue is not fully done yet. This issue includes:
|
Ahh, thanks @epotyom. Since this issue was partially merged and released in 9.9.0, can you open a new issue for the followon tasks?
This would be great to have, but should not block step 2 -- we are free to introduce new APIs without fully knowing their performance characteristics yet. |
Opened #12919 |
Description
LUCENE-9476 added the ability to do bulk ordinal -> path lookups, but we have no bulk lookup in the other direction. I think we can find some efficiency gains if we add bulk lookup for paths, which we could then put behind a
Facets#getSpecificValues
API for retrieving facet values for multiple paths in bulk. There's some nuance down in the depths of MultiTerms, so maybe there's nothing to be gained here, but I think there ought to be (I'll try to look in more detail later, but wanted to open an issue to track the idea in case I forget). A few thoughts:The text was updated successfully, but these errors were encountered: