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 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 > <shalinman...@gmail.com> wrote: > > On Tue, Aug 13, 2013 at 9:15 PM, Robert Muir <rcm...@gmail.com> wrote: > >> On Tue, Aug 13, 2013 at 11:39 AM, Shalin Shekhar Mangar > >> <shalinman...@gmail.com> 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 all such 0-document segments? > >>> > >>> > >> > >> Not in 4.4: https://issues.apache.org/jira/browse/LUCENE-5116 > > > > > > Sorry, I didn't notice that. So 4.4 users must call commit/optimize > > with expungeDeletes="true" until 4.5 is released if they run into this > > problem. > > > > -- > > Regards, > > Shalin Shekhar Mangar. > > > > -- > Regards, > Shalin Shekhar Mangar. >
