[
https://issues.apache.org/jira/browse/SOLR-15257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436934#comment-17436934
]
Collins Abanda commented on SOLR-15257:
---------------------------------------
Since we are moving away from Filter in solr, my initial thought is to try to
combine the functionality of Filter and Query, and then gradually delete the
Filter class entirely. Is this a reasonable approach? I was also hoping to get
some context and clarification on how something like a .makeQuery helps this
issue, and what specific changes need to be made to DocSet's API?
> Add DocSetQuery in lieu of DocSet.getTopFilter
> ----------------------------------------------
>
> Key: SOLR-15257
> URL: https://issues.apache.org/jira/browse/SOLR-15257
> Project: Solr
> Issue Type: Sub-task
> Components: search
> Reporter: David Smiley
> Priority: Major
>
> With Filter going away, we still need the ability to have a Query based on a
> DocSet. This currently happens via {{DocSet.getTopFilter}}. We could add a
> {{.makeQuery}} or just provide it.
> This issue depends on changes to DocSet's API to provide a DocIdSetIterator
> given a LeafReaderContext.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
