gsmiller commented on PR #11901: URL: https://github.com/apache/lucene/pull/11901#issuecomment-1320139204
@mdmarshmallow it's similar to FacetSets but a bit different since FacetSets work over stored points, while this would work over stored ranges. I think it would make sense to eventually support multiple dimensions here, since the data (`LongRangeDocValueFields`) allow for it. I'm thinking about a user who is storing multi-dim ranges and creating queries that filter over those same ranges, but has no way to facet over them. As for how to handle faceting of multi-dim ranges, I think the logic would be the same as the "slow" query you reference, and would depend on the `RangeFieldQuery#QueryType` specified. But... as for concrete next steps, I see the value in simplifying the problem to a single dimension to get started. That likely covers most use-cases anyway. But I'd also like to create a path towards supporting multi-dim without having to create a completely new API. Could we re-use `LongRangeDocValueFields` for the indexing piece of this, and create a faceting implementation that functions over that data, but only make it work for single dimensions to start? Maybe the faceting API you create is simplified to the single-dimension case and it validates that the underlying field being faceted is single-dim? That way, in the future, if we add multi-dim support, users can keep using the same field type for their documents but the API gets generalized? -- 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
