Streaming & Batch are different behaviour, that's why we should leave this option to user to allow them choose which exactly result they want.
Add one setting option for each cube/streaming say "AllowEmptySegment", default to be true Then when cubing engine could raise error when it set to false, and continue if true. Even in streaming case, some of them are ok to merge empty later but some need alert. Thanks. Best Regards! --------------------- Luke Han On Thu, Aug 6, 2015 at 9:08 PM, hongbin ma <[email protected]> wrote: > how about in the streaming case? even if we label a segment as warning, it > might get merged before we notice it. > > On Thu, Aug 6, 2015 at 5:51 PM, Li Yang <[email protected]> wrote: > > > Luke and me discussed this once. I remember the conclusion is let the > build > > pass, but leave a warn on GUI to remind user there might be error about > the > > input source. > > > > On Mon, Aug 3, 2015 at 11:59 AM, hongbin ma <[email protected]> > wrote: > > > > > Do we have any resolution on how to deal with segment with 0 records > now? > > > > > > I found a ticket https://issues.apache.org/jira/browse/KYLIN-345, it > is > > > closed now, > > > but i'm not aware of this by far. > > > > > > -- > > > Regards, > > > > > > *Bin Mahone | 马洪宾* > > > Apache Kylin: http://kylin.io > > > Github: https://github.com/binmahone > > > > > > > > > -- > Regards, > > *Bin Mahone | 马洪宾* > Apache Kylin: http://kylin.io > Github: https://github.com/binmahone >
