[
https://issues.apache.org/jira/browse/HIVE-14669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817445#comment-16817445
]
Laszlo Bodor edited comment on HIVE-14669 at 4/15/19 9:24 AM:
--------------------------------------------------------------
[~kgyrtkirk]: it's a small patch about propagating CommandProcessorResponse
(containing exception) instead of a single error code from CliDriver to the
world, that can be used in test cli drivers
was (Author: abstractdog):
[~kgyrtkirk]
> Have the actual error reported when a q test fails instead of having to go
> through the logs
> -------------------------------------------------------------------------------------------
>
> Key: HIVE-14669
> URL: https://issues.apache.org/jira/browse/HIVE-14669
> Project: Hive
> Issue Type: Sub-task
> Reporter: Siddharth Seth
> Assignee: Laszlo Bodor
> Priority: Major
> Attachments: 01_mvn_out.png, 02_hive_log.png, HIVE-14469.01.patch,
> HIVE-14469.02.patch, Screen Shot 2019-04-11 at 4.54.41 PM.png
>
>
> QTest runs end up invoking CliDriver.processLine. This, in most cases,
> reports a numeric exit code - 0 for success. Non-zero for various different
> error types (which are defined everywhere in the code).
> Internally CliDriver does have more information via CommandResult. A lot of
> this is not exposed though. That's alright for the end user cli - (Command
> line tool translating the error to a code and message). However, it makes
> debugging very difficult for QTests - since the log needs to be looked at
> each time.
> Errors generated by the actual backend execution are mostly available to the
> client, and information about these should show up as well. (If it doesn't -
> we have a usability issues to fix).
> cc [~ekoifman]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
