I'm running into the same issue using composite routing keys when all of
the shard keys end up in one of the subshards.
-Greg
On Tue, Aug 13, 2013 at 9:34 AM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:
> Scratch that. I obviously didn't pay attention to the stack trace.
> There is n
Scratch that. I obviously didn't pay attention to the stack trace.
There is no workaround until 4.5 for this issue because we split the
range by half and thus cannot guarantee that all segments will have
numDocs > 0.
On Tue, Aug 13, 2013 at 9:25 PM, Shalin Shekhar Mangar
wrote:
> On Tue, Aug 13,
On Tue, Aug 13, 2013 at 9:15 PM, Robert Muir wrote:
> On Tue, Aug 13, 2013 at 11:39 AM, Shalin Shekhar Mangar
> wrote:
>> 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
On Tue, Aug 13, 2013 at 11:39 AM, Shalin Shekhar Mangar
wrote:
> 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 al
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 Mui
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
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.
did you do a (real) commit before trying to use this?
I am not sure how this splitting works, but at least the merge option
requires that.
i can't see this happening unless you are somehow splitting a 0
document index (or, if the splitter is creating 0 document splits)
so this is likely just a sym
