lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From eks dev <eks...@yahoo.co.uk>
Subject Re: [jira] Commented: (LUCENE-584) Decouple Filter from BitSet
Date Thu, 14 Sep 2006 20:14:10 GMT
not being inpatient, just asking if all holes are covered, Matcher rocks and I'd like to clean
up a lot of mess we created in our local copy in order to simulate what Matcher will permit
us to do in really elegant way...

if being patient is all what it takes, cool ;)

----- Original Message ----
From: Paul Elschot (JIRA) <jira@apache.org>
To: java-dev@lucene.apache.org
Sent: Thursday, 14 September, 2006 8:41:25 PM
Subject: [jira] Commented: (LUCENE-584) Decouple Filter from BitSet

    [ http://issues.apache.org/jira/browse/LUCENE-584?page=comments#action_12434763 ] 
            
Paul Elschot commented on LUCENE-584:
-------------------------------------

> Do you, or someone else see now things to be done before commiting this?

Yes. In the steps listed here:
http://wiki.apache.org/jakarta-lucene/HowToContribute
the next step is to be patient.
Wether being patient is something that can be done
is open question...

Paul Elschot.



> Decouple Filter from BitSet
> ---------------------------
>
>                 Key: LUCENE-584
>                 URL: http://issues.apache.org/jira/browse/LUCENE-584
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>    Affects Versions: 2.0.1
>            Reporter: Peter Schäfer
>            Priority: Minor
>         Attachments: BitsMatcher.java, Filter-20060628.patch, HitCollector-20060628.patch,
IndexSearcher-20060628.patch, MatchCollector.java, Matcher.java, Matcher20060830b.patch, Scorer-20060628.patch,
Searchable-20060628.patch, Searcher-20060628.patch, Some Matchers.zip, SortedVIntList.java,
TestSortedVIntList.java
>
>
> {code}
> package org.apache.lucene.search;
> public abstract class Filter implements java.io.Serializable 
> {
>   public abstract AbstractBitSet bits(IndexReader reader) throws IOException;
> }
> public interface AbstractBitSet 
> {
>   public boolean get(int index);
> }
> {code}
> It would be useful if the method =Filter.bits()= returned an abstract interface, instead
of =java.util.BitSet=.
> Use case: there is a very large index, and, depending on the user's privileges, only
a small portion of the index is actually visible.
> Sparsely populated =java.util.BitSet=s are not efficient and waste lots of memory. It
would be desirable to have an alternative BitSet implementation with smaller memory footprint.
> Though it _is_ possibly to derive classes from =java.util.BitSet=, it was obviously not
designed for that purpose.
> That's why I propose to use an interface instead. The default implementation could still
delegate to =java.util.BitSet=.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



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





---------------------------------------------------------------------
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