sandeshkr419 commented on issue #12553: URL: https://github.com/apache/lucene/issues/12553#issuecomment-2068393874
Thanks @stefanvodita, @Shradha26 for doing a thorough review of gaps with Lucene's faceting. I think that in summary, this is leaning in towards support for aggregation capabilities in Lucene out of the box given the present structure with Faceting is a stepping stone to aggregations but requires a lot of overhead by its consumers to actually implement aggregations. --------------------- Some of the points form my discussion with @msfroh: As you already mentioned, that `Lucene has some unique ideas to make aggregation computation efficient.`, but the caveat is that the gaps makes it very unlikely to actually use them in platforms like Elasticsearch, OpenSearch and any consumers who demand rich aggregations which is usually the case - isn't it that you need full aggregation capabilities?. What we think is that its high time that Lucene should have support for aggregations. To kickstart, the implementations can inspire from some of the already existing open-source projects like OpenSearch, Solr (I haven't checked those myself) but this can be open for discussion. I was looking into OpenSearch's code base for aggregations and it looks like decoupling aggregations for Lucene might not be a very straightforward thing but its worth putting efforts into if the Lucene community thinks that rich aggregations will be a good inclusion in Lucene. -- 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
