lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 32921] - Some utilities for a compact sparse filter
Date Mon, 20 Jun 2005 20:14:30 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32921>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32921





------- Additional Comments From paul.elschot@xs4all.nl  2005-06-20 22:14 -------
(In reply to comment #12) 
> Paul, 
> What was the status with this code - its been a while since you posted it. 
 
It's working nicely for me. 
 
> I've got some extensions which could be added here: 
> * BitSet and IntArray based implementations of DocNrSkipper 
 
These would be useful because they have different tradeoffs in memory use 
and runtime. 
 
> * OrDocNoSkipper and AndDocNoSkipper wrapper implementations which both take 
2 
> DocNrSkippers in their constructor and offer "OR" or "AND" based iteration 
> across the sets' intersections. These are DocNrSkipper implementations too so 
> can be arbitrarily nested within each other (like BooleanQuery does). 
 
In case you prefer DocNoSkipper or something else I don't mind. 
Using both DocNo and DocNr in names will cause confusion, though. 
 
The OrDocNoSkipper and AndDocNoSkipper would be good to implement 
constant scoring queries. The top level OR iterator could then be 
implemented by iterating on the DocNrSkippers separately into 
a BitSet. 
Did you also consider more than two arguments to these AND and OR 
iterators? 
For completeness a "NOT" based iteration 
would also be needed, but that can be added when needed. 
 
I'm interested in extending QueryParser to use these 
mechanisms on 'boolean' fields like dates and primary keys. 
 
To easily implement boolean operations with a constant scoring term, 
a "close relative" of TermScorer might directly implement the 
Doc{No/Nr}Skipper interface. Any opinions on a: 
 
class TermConstantScorer 
extends Scorer 
implements DocNrSkipper { 
  ... 
} 
 
? 
 
It might also be good to put all new things related 
to skipping filters and constant scoring queries 
in (a) new subpackage(s) of org.apache.lucene.search. 
 
Regards, 
Paul Elschot 
 
 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message