[
https://issues.apache.org/jira/browse/LUCENE-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737486#action_12737486
]
Michael McCandless commented on LUCENE-1504:
--------------------------------------------
I've emailed Patrick privately and it looks like he's pretty swamped, so I'll
take a stab at cutting over to DocIdSet, here.
Actually I think we can use FilteredDocIdSet to do the "serial" chaining (I
think it has the same motivation as "SERIALAND": to efficiently AND two filters
together such that the 2nd filter only "does work" if the first filter accepted
the doc). FilteredDocIdSet doesn't handle the SERIALOR case, but, nothing uses
SERIALOR now (I think?) so I think that's OK. I'll change
LatLong/GeoHashDistanceFilter to extend FilteredDocIdSet.
> SerialChainFilter should use DocSet API rather then deprecated BitSet API
> -------------------------------------------------------------------------
>
> Key: LUCENE-1504
> URL: https://issues.apache.org/jira/browse/LUCENE-1504
> Project: Lucene - Java
> Issue Type: Improvement
> Components: contrib/spatial
> Reporter: Ryan McKinley
> Assignee: Uwe Schindler
> Fix For: 2.9
>
> Attachments: LUCENE-1504.patch, LUCENE-1504.patch
>
>
> From erik's comments in LUCENE-1387
> * Maybe the Filter's should be using the DocIdSet API rather than the
> BitSet deprecated stuff? We can refactor that after being committed I
> supposed, but not something we want to leave like that.
> We should also look at moving SerialChainFilter out of the spatial contrib
> since it is more generally useful then just spatial search.
--
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: [email protected]
For additional commands, e-mail: [email protected]
