mikemccand commented on PR #13568: URL: https://github.com/apache/lucene/pull/13568#issuecomment-2250274471
> I think the big one for me to resolve is this whole concept of trying to make non-taxonomy faceting "look like" taxonomy faceting by making it fit this "ordinal iteration" paradigm. One possible example of where this unification could be helpful is in treating range faceting as a hierarchy, like Taxonomy based facets already support (parent/children/sibling, etc.). Range faceting to the end user should sometimes be a hierarchy. E.g. I narrow by price $50 - $100 (after seeing multiple $50 ranges), and after that I can narrow by $20 ranges, and then after that maybe $5 ranges. Lucene's faceting today doesn't really model this hierarchy well, I think? The user must hold this implicit hierarchy and change their ranges as the user drills down, or dynamically / iteratively build the ranges based on the prices seen in the full match set. I'm not sure whether the new paradigm actually helps in this use case :) I just wanted to point out that range faceting is really also a hierarchy and we don't seem to model that well in our facet impl today... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
