You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/04/30 23:09:00 UTC
[jira] [Updated] (IMPALA-6835) Improve Kudu scanner error messages
to include the table name and the plan node id
[ https://issues.apache.org/jira/browse/IMPALA-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong updated IMPALA-6835:
----------------------------------
Labels: kudu observability supportability (was: kudu observability)
> Improve Kudu scanner error messages to include the table name and the plan node id
> ----------------------------------------------------------------------------------
>
> Key: IMPALA-6835
> URL: https://issues.apache.org/jira/browse/IMPALA-6835
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.11.0, Impala 3.0, Impala 2.12.0
> Reporter: yyzzjj
> Priority: Major
> Labels: kudu, observability, supportability
>
> E.g: [https://github.com/apache/impala/blob/830e3346f186aebc879e4ef2927e08db97143100/be/src/exec/kudu-scanner.cc#L338]
> big sql usually contains dozens of tables， when query fail kudu tserver or master response error info which not contain table name
> Inconvenient positioning problem which table
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org