[
https://issues.apache.org/jira/browse/KYLIN-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862616#comment-15862616
]
Dayue Gao commented on KYLIN-2443:
----------------------------------
Commit
https://github.com/apache/kylin/commit/43c0566728092d537201d751d3e8f6e3c0d5f051
Changes highlight
* Update CubeVisitResponse message with ErrorInfo and report error message back
to end user
* Renamed GTScanTimeoutException to KylinTimeoutException,
GTScanExceedThresholdException to ResourceLimitExceededException. Deleted
GTScanSelfTerminatedException.
* Make SQLResponse#totalScanCount reflect hbase scan count rather than query
server scan count. Rename StorageContext#totalScanCount to processedRowCount
[~mahongbin], could you peer review the commit?
> Report coprocessor error information back to client
> ---------------------------------------------------
>
> Key: KYLIN-2443
> URL: https://issues.apache.org/jira/browse/KYLIN-2443
> Project: Kylin
> Issue Type: Improvement
> Components: Storage - HBase
> Affects Versions: v1.6.0
> Reporter: Dayue Gao
> Assignee: Dayue Gao
>
> When query aborts in coprocessor, the current error message (list below)
> doesn't carry any concrete reason. User has to check regionserver's log in
> order to figure out what's happening, which is a tedious work and not always
> possible in a cloud environment.
> {noformat}
> <sub-thread for Query 4fb68974-de70-4f6e-a2ee-7048202e51a7 GTScanRequest
> 4d65f9bf>The coprocessor thread stopped itself due to scan timeout or scan
> threshold(check region server log), failing current query...
> {noformat}
> It would be better to report error message to client.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
