[
https://issues.apache.org/jira/browse/KYLIN-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281378#comment-15281378
]
wangxianbin commented on KYLIN-1684:
------------------------------------
yes, it is! two options for us:
1,make the hadoop history server become a prerequisite component for running
kylin.
2,remove the unnecessary check.
> query on table "kylin_sales" return empty resultset after cube
> "kylin_sales_cube" which generated by sample.sh is ready
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: KYLIN-1684
> URL: https://issues.apache.org/jira/browse/KYLIN-1684
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: v1.5.1
> Environment: cluster:
> hadoop-2.6.0
> hbase-0.98.8
> hive-0.14.0
> Reporter: wangxianbin
> Assignee: liyang
> Attachments: log for Build Base Cuboid Data.png, log when run
> query.png
>
>
> there is a check for "InputRecords" in CubeStorageQuery search method which
> seem like unnecessary, as follow:
> List<CubeSegmentScanner> scanners = Lists.newArrayList();
> for (CubeSegment cubeSeg :
> cubeInstance.getSegments(SegmentStatusEnum.READY)) {
> CubeSegmentScanner scanner;
> if (cubeSeg.getInputRecords() == 0) {
> logger.info("Skip cube segment {} because its input record is
> 0", cubeSeg);
> continue;
> }
> scanner = new CubeSegmentScanner(cubeSeg, cuboid, dimensionsD,
> groupsD, metrics, filterD, !isExactAggregation);
> scanners.add(scanner);
> }
> if (scanners.isEmpty())
> return ITupleIterator.EMPTY_TUPLE_ITERATOR;
> return new SequentialCubeTupleIterator(scanners, cuboid, dimensionsD,
> metrics, returnTupleInfo, context);
> this check will cause query return empty resultset, even there is data in
> storage engine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
