Thanks!
So is there any option to build daily segments not in monotonic order?
It's sometimes the case that data are partitioned and due to some problems
in processing
more recent partitions are ready earlier than older ones.
How can it be handled in Kylin in daily refresh scenario?
Marek
2015-12-07 17:11 GMT+01:00 yu feng <olaptes...@gmail.com>:
> Kylin will ignore startTime while building a segment, It will take 1)
> start time you set in building cube if you are build first segment, 2)
> end time of last segment if you append new segment as start time of
> new segment.
>
> 2015-12-07 20:22 GMT+08:00, Marek Wiewiorka <marek.wiewio...@gmail.com>:
> > Hi All,
> > I came across a weird situation with Kylin cube incremental refresh.
> > I will try to describe it:
> > I've a cube with data up to 2015.12.03.
> > When tried to to build a cube segment for 2015.12.06 by specify a json
> like
> > this:
> > {
> > "startTime": "1449360000000",
> > "endTime": "1449446400000",
> > "buildType": "BUILD"
> > }
> > Kylin ignored startTime and started building a segment 2015-12-03 --
> > 2015-12-07
> > instead 2015-12-06 -- 2015-12-07 - so starting to build a segment
> starting
> > from the most
> > recent date in segment already available not the one I specified in a
> json
> > file.
> >
> > So is it a bug or a feature that it's not possible to build a one-day
> > segment in such a scenario - it seems like Kylin does not allow gaps
> > between segments?
> >
> > Thanks in advance!
> >
>
