i remember we had other customers having same problem when we're back in the 0.6 versions, and back at that time building an empty segment was possible(with no "no dictionary issue"). In 0.7 versions we refactored job build engine and we might have failed to consider such scenarios.
In short, your requirement is theoretically feasible, however we'll need to further check why it's blocking. On Fri, May 15, 2015 at 6:03 PM, dong wang <[email protected]> wrote: > As we know, currently, if we select a date range to build the cube and > there is no data for this segment, the build process will fail due to no > values for the dictionary, however, image a frequent case that at the > beginning of a project, the data is prepared by other teams ONLY with the > latest several days or months, but we actually want to fill the data in the > cube from the beginning of 2 years ago and build the cube segment by > segment by each month, since lack of the previous old data of the earlier > months, currently, we have to produce some fake data with specified > requirement for the earlier months and build those segments, which > sometimes is really a hard,tired, and time-consuming work > > thus, can we make the build process successful even though the data for > that month is empty, and just leave these segments empty, then, at the end > of the project, all the data may be ready, and we can "REFRESH" the earlier > months to fill the data~ > -- Regards, *Bin Mahone | 马洪宾* Apache Kylin: http://kylin.io Github: https://github.com/binmahone
