[
https://issues.apache.org/jira/browse/LUCENE-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897946#comment-13897946
]
Uwe Schindler commented on LUCENE-5440:
---------------------------------------
bq. I don't think FixedBitSet should be external. Our purpose here is to
provide search APIs, not bitset utility APIs, and we should not have to commit
to API back compatibility for this class or other such utility classes.
I disagree: If this is our case, we have to do more APIs internal and also hide
stuff like AtomicReader, because its not useful for the end user. FixedBitSet
is currently the only way for users to write own filters, unless they write
their own DocIdSets. So to support filtering results, users have to implement
the DocIdSet, Bits and DISI interfaces (which are public), so at least one
implementation (the recommended one) should be public and stable.
> Add LongFixedBitSet and replace usage of OpenBitSet
> ---------------------------------------------------
>
> Key: LUCENE-5440
> URL: https://issues.apache.org/jira/browse/LUCENE-5440
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Reporter: Shai Erera
> Assignee: Shai Erera
> Attachments: LUCENE-5440-solr.patch, LUCENE-5440.patch,
> LUCENE-5440.patch, LUCENE-5440.patch, LUCENE-5440.patch, LUCENE-5440.patch
>
>
> Spinoff from here: http://lucene.markmail.org/thread/35gw3amo53dsqsqj. I
> wrote a LongFixedBitSet which behaves like FixedBitSet, only allows managing
> more than 2.1B bits. It overcome some issues I've encountered with
> OpenBitSet, such as the use of set/fastSet as well the implementation of
> DocIdSet. I'll post a patch shortly and describe it in more detail.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
