lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Commented: (LUCENE-2628) Extract OpenBitSet to Apache Commons
Date Sun, 29 Aug 2010 15:10:55 GMT


Robert Muir commented on LUCENE-2628:

I still wanna throw one possible solution in for discussion. Since Lucene has many very useful
classes in its utils package we could consider package the utils package as its own jar decoupled
somehow from the core. That way people could use those classes without pulling in the whole
lucene core and the interface would remain unchanged. It still feels odd that core would depend
on utils jar but it would be an option and it would fit into the modules concept.

I'm not sure I like this. Most of the stuff in the util package should be marked lucene.internal
anyway, so such a jar would be of minimal use.

Furthermore, I think search related modules make sense, (spatial search, text analyzers, queries,
queryparsers) because this is a search engine library project.
But i don't think we should deviate from that.

Although some might consider utility stuff like this useful, I don't think we should be creating
artifacts that arent focused on search. 
we should keep this stuff internal.

> Extract OpenBitSet to Apache Commons
> ------------------------------------
>                 Key: LUCENE-2628
>                 URL:
>             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 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:
For additional commands, e-mail:

View raw message