The splitting code calls commit before it starts the splitting. It creates a LiveDocsReader using a bitset created by the split. This reader is merged to an index using addIndexes.
Shouldn't the addIndexes code then ignore all such 0-document segments? On Tue, Aug 13, 2013 at 6:08 PM, Robert Muir <rcm...@gmail.com> wrote: > Well, i meant before, but i just took a look and this is implemented > differently than the "merge" one. > > In any case, i think its the same bug, because I think the only way > this can happen is if somehow this splitter is trying to create a > 0-document "split" (or maybe a split containing all deletions). > > On Tue, Aug 13, 2013 at 8:22 AM, Srivatsan <ranjith.venkate...@gmail.com> > wrote: > > Ya i am performing commit after split request is submitted to server. > > > > > > > > -- > > View this message in context: > http://lucene.472066.n3.nabble.com/Split-Shard-Error-maxValue-must-be-non-negative-tp4084220p4084256.html > > Sent from the Solr - User mailing list archive at Nabble.com. > -- Regards, Shalin Shekhar Mangar.
