Splitting an index by modifying the segments file

I'm wondering whether anyone has written an index splitter that does nothing more than generate a new segments file containing only selected segments of the original index. Obviously, there are a lot of limitations on how useful this would be, since all it can really do is remove SegName entries

DO NOT REPLY [Bug 34154] - Further improvements to BooleanScorer2

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35823] - [PATCH] BooleanScorer2 ArrayIndexOutOfBoundsException

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34154] - Further improvements to BooleanScorer2

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35823] - [PATCH] BooleanScorer2 ArrayIndexOutOfBoundsException

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35879] New: - Merge error during add to index (IndexOutOfBoundsException)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35823] - [PATCH] BooleanScorer2 ArrayIndexOutOfBoundsException

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35838] - Java NIO patch against Lucene 1.9

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35838] - Java NIO patch against Lucene 1.9

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35838] - Java NIO patch against Lucene 1.9

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: DO NOT REPLY [Bug 34154] - Further improvements to BooleanScorer2

On Jul 26, 2005, at 3:04 AM, Paul Elschot wrote: +(spanNear([FULLTEXT:cat, FULLTEXT:dog, FULLTEXT:bird], 1, true) spanNear([FULLTEXT:horse, FULLTEXT:cow, FULLTEXT:pig], 1, true) spanNear([FULLTEXT:snake, FULLTEXT:camel], 0, true)) +(FULLTEXT:zebra FULLTEXT:insect spanNear([FULLTEXT:feline, FULLT

Re: DO NOT REPLY [Bug 34154] - Further improvements to BooleanScorer2

On Tuesday 26 July 2005 03:01, Erik Hatcher wrote: > ... > > Let me know if there is other information I can provide, or other > variants of BooleanScorer2 I can try. In case this is cricital you can use this to revert to the 1.4 version of BooleanScorer: BooleanQuery.setUseScorer14(true) Re

Re: DO NOT REPLY [Bug 34154] - Further improvements to BooleanScorer2

On Tuesday 26 July 2005 03:01, Erik Hatcher wrote: > > On Jul 24, 2005, at 11:23 AM, Paul Elschot wrote: > > > On Friday 22 July 2005 21:18, Erik Hatcher wrote: > > > >> Paul, > >> > >> I don't have a test case handy (yet), but we're still seeing the > >> exception even after applying the patch f