[ 
https://issues.apache.org/jira/browse/LUCENE-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903885#action_12903885
 ] 

Robert Muir commented on LUCENE-2628:
-------------------------------------

I think things like this should stay in Lucene and their implementations should 
remain specialized towards our use cases.

If we put them in apache commons and depend on them ourselves, then other use 
cases might want to make tradeoffs that
are bad for lucene (but perhaps good for other use cases).

Additionally the lucene core has no external dependencies, and I dont think we 
should add any.

In short, I don't see what we would gain here.

> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to