[
https://issues.apache.org/jira/browse/LUCENE-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903931#action_12903931
]
Stu Hood commented on LUCENE-2628:
----------------------------------
> then other use cases might want to make tradeoffs that are bad for lucene
I can't claim to see the future, but I think this datastructure is already so
specialized and solid that the chances of it evolving much further are slim.
> Additionally the lucene core has no external dependencies, and I dont think
> we should add any.
While this is definitely admirable and worth trying to preserve, it should be
weighed against the duplication it incurs: especially within the Apache project
itself. For example if the Cassandra project takes the same stance, then we end
up with two copies of this class.
> Extract OpenBitSet to Apache Commons
> ------------------------------------
>
> Key: LUCENE-2628
> URL: https://issues.apache.org/jira/browse/LUCENE-2628
> Project: Lucene - Java
> Issue Type: Wish
> Reporter: Stu Hood
>
> o.a.l.util.OpenBitSet is a great alternative to java.util.BitSet, and it is
> generally useful outside of the search field. It would be great if OpenBitSet
> were available outside of Lucene proper, perhaps as part of Apache Commons.
> Aside from the communication required to accomplish this, there is the small
> issue of OpenBitSet extending o.a.l.search.DocIdSet in Lucene 3.0. There is
> very little logic contained in DocIdSet, so it could probably become an
> interface: Lucene proper could then extend the extract version of OpenBitSet
> to implement DocIdSet.
--
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]