FAQ
[ https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Miller reopened LUCENE-584:
--------------------------------


I think I have tracked down this issue as the one changing things most regarding Scorer documentation in org.apache.lucene.search.package.html.

I've started updating it, but it needs a tad more work I think - reopening this issue as a convenient marker for this work.
Decouple Filter from BitSet
---------------------------

Key: LUCENE-584
URL: https://issues.apache.org/jira/browse/LUCENE-584
Project: Lucene - Java
Issue Type: Improvement
Components: Search
Affects Versions: 2.1
Reporter: Peter Schäfer
Assignee: Michael Busch
Priority: Minor
Fix For: 2.4

Attachments: bench-diff.txt, bench-diff.txt, CHANGES.txt.patch, ContribQueries20080111.patch, lucene-584-take2.patch, lucene-584-take3-part1.patch, lucene-584-take3-part2.patch, lucene-584-take4-part1.patch, lucene-584-take4-part2.patch, lucene-584-take5-part1.patch, lucene-584-take5-part2.patch, lucene-584.patch, Matcher-20070905-2default.patch, Matcher-20070905-3core.patch, Matcher-20071122-1ground.patch, Some Matchers.zip, Test20080111.patch


{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.
-
You can reply to this email to add a comment to the issue online.


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

Search Discussions

  • Michael Busch (JIRA) at Aug 21, 2009 at 8:35 am
    [ https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Michael Busch updated LUCENE-584:
    ---------------------------------

    Fix Version/s: (was: 2.4)
    2.9
    Decouple Filter from BitSet
    ---------------------------

    Key: LUCENE-584
    URL: https://issues.apache.org/jira/browse/LUCENE-584
    Project: Lucene - Java
    Issue Type: Improvement
    Components: Search
    Affects Versions: 2.1
    Reporter: Peter Schäfer
    Assignee: Michael Busch
    Priority: Minor
    Fix For: 2.9

    Attachments: bench-diff.txt, bench-diff.txt, CHANGES.txt.patch, ContribQueries20080111.patch, lucene-584-take2.patch, lucene-584-take3-part1.patch, lucene-584-take3-part2.patch, lucene-584-take4-part1.patch, lucene-584-take4-part2.patch, lucene-584-take5-part1.patch, lucene-584-take5-part2.patch, lucene-584.patch, Matcher-20070905-2default.patch, Matcher-20070905-3core.patch, Matcher-20071122-1ground.patch, Some Matchers.zip, Test20080111.patch


    {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.
    -
    You can reply to this email to add a comment to the issue online.


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-dev-help@lucene.apache.org
  • Michael Busch (JIRA) at Aug 21, 2009 at 3:28 pm
    [ https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746017#action_12746017 ]

    Michael Busch commented on LUCENE-584:
    --------------------------------------

    Mark, are you working on this? Wanna assign this to you?
    Decouple Filter from BitSet
    ---------------------------

    Key: LUCENE-584
    URL: https://issues.apache.org/jira/browse/LUCENE-584
    Project: Lucene - Java
    Issue Type: Improvement
    Components: Search
    Affects Versions: 2.1
    Reporter: Peter Schäfer
    Assignee: Michael Busch
    Priority: Minor
    Fix For: 2.9

    Attachments: bench-diff.txt, bench-diff.txt, CHANGES.txt.patch, ContribQueries20080111.patch, lucene-584-take2.patch, lucene-584-take3-part1.patch, lucene-584-take3-part2.patch, lucene-584-take4-part1.patch, lucene-584-take4-part2.patch, lucene-584-take5-part1.patch, lucene-584-take5-part2.patch, lucene-584.patch, Matcher-20070905-2default.patch, Matcher-20070905-3core.patch, Matcher-20071122-1ground.patch, Some Matchers.zip, Test20080111.patch


    {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.
    -
    You can reply to this email to add a comment to the issue online.


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-dev-help@lucene.apache.org
  • Mark Miller (JIRA) at Aug 21, 2009 at 3:30 pm
    [ https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Mark Miller reassigned LUCENE-584:
    ----------------------------------

    Assignee: Mark Miller (was: Michael Busch)
    Decouple Filter from BitSet
    ---------------------------

    Key: LUCENE-584
    URL: https://issues.apache.org/jira/browse/LUCENE-584
    Project: Lucene - Java
    Issue Type: Improvement
    Components: Search
    Affects Versions: 2.1
    Reporter: Peter Schäfer
    Assignee: Mark Miller
    Priority: Minor
    Fix For: 2.9

    Attachments: bench-diff.txt, bench-diff.txt, CHANGES.txt.patch, ContribQueries20080111.patch, lucene-584-take2.patch, lucene-584-take3-part1.patch, lucene-584-take3-part2.patch, lucene-584-take4-part1.patch, lucene-584-take4-part2.patch, lucene-584-take5-part1.patch, lucene-584-take5-part2.patch, lucene-584.patch, Matcher-20070905-2default.patch, Matcher-20070905-3core.patch, Matcher-20071122-1ground.patch, Some Matchers.zip, Test20080111.patch


    {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.
    -
    You can reply to this email to add a comment to the issue online.


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-dev-help@lucene.apache.org
  • Mark Miller (JIRA) at Aug 23, 2009 at 2:45 am
    [ https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Mark Miller resolved LUCENE-584.
    --------------------------------

    Resolution: Fixed

    Its better now I think - could prob be improved still (by someone who has sunk their head into the new Scorer stuff more than I have) - but I read over the code and did what I could. At the least, its no longer wildly out of whack.
    Decouple Filter from BitSet
    ---------------------------

    Key: LUCENE-584
    URL: https://issues.apache.org/jira/browse/LUCENE-584
    Project: Lucene - Java
    Issue Type: Improvement
    Components: Search
    Affects Versions: 2.1
    Reporter: Peter Schäfer
    Assignee: Mark Miller
    Priority: Minor
    Fix For: 2.9

    Attachments: bench-diff.txt, bench-diff.txt, CHANGES.txt.patch, ContribQueries20080111.patch, lucene-584-take2.patch, lucene-584-take3-part1.patch, lucene-584-take3-part2.patch, lucene-584-take4-part1.patch, lucene-584-take4-part2.patch, lucene-584-take5-part1.patch, lucene-584-take5-part2.patch, lucene-584.patch, Matcher-20070905-2default.patch, Matcher-20070905-3core.patch, Matcher-20071122-1ground.patch, Some Matchers.zip, Test20080111.patch


    {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.
    -
    You can reply to this email to add a comment to the issue online.


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

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupjava-dev @
categorieslucene
postedAug 21, '09 at 1:28a
activeAug 23, '09 at 2:45a
posts5
users1
websitelucene.apache.org

1 user in discussion

Mark Miller (JIRA): 5 posts

People

Translate

site design / logo © 2021 Grokbase