bharath-techie commented on issue #13188: URL: https://github.com/apache/lucene/issues/13188#issuecomment-2086176227
Thanks for the inputs @jpountz . Let me spend some more time on this. But this is a topic which was thought of as well and one idea was to do query abstraction / planning. Let me know your thoughts : Can the concern with query can be solved by abstracting it by introducing `DataCubeOrOriginalQuery` similar to `IndexOrDocValuesQuery` ? In fact the input can remain the same as of the original query , we can do a check if that can be solved via `DataCubesIndex` . Terms / multi terms/ range / boolean queries and associated fields are something we can parse and check if there are any `DataCubeField` that contains the same fields as dims and if so we can choose to pick the optimal `DataCubeField` and form associated query in the background. Or we can also think of query rewriting if a particular query can be solved using `DataCubes`. But there is an issue in `collection` still, user needs to pass two collector implementations which needs to be picked based on which query path is taken. We can see how to better implement this if the above idea works. -- 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
