[
https://issues.apache.org/jira/browse/LUCENE-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662685#action_12662685
]
Paul Elschot commented on LUCENE-1345:
--------------------------------------
Marvin,
bq. In KS svn trunk (and potentially in Lucy), there is no "Filter"; all
classes that perform filtering are just subclasses of Query which you're
expected to apply using an ANDQuery. Can you think of any downside to that
model?
In Lucene the class model is that Scorer extends DocIdSetIterator by some
methods involved with document score values. To prepare searching in
Lucene the following 'transformations' are done:
Query -> Weight -> Scorer
and
Filter -> DocIdSetIterator
I've never seen the KS classes, but on the face of it, the downside of using
ANDQuery (KS) for filtering is that it has to provide a score value, which
somehow must be ignored during search.
> Allow Filter as clause to BooleanQuery
> --------------------------------------
>
> Key: LUCENE-1345
> URL: https://issues.apache.org/jira/browse/LUCENE-1345
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Reporter: Paul Elschot
> Priority: Minor
> Fix For: 2.9
>
> Attachments: booleansetperf.txt, DisjunctionDISI.java,
> DisjunctionDISI.patch, DisjunctionDISI.patch, LUCENE-1345.patch,
> LUCENE-1345.patch, OpenBitSetIteratorExperiment.java, TestIteratorPerf.java,
> TestIteratorPerf.java
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
