hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pengcheng Xiong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-14669) Have the actual error reported when a q test fails instead of having to go through the logs
Date Sat, 25 Mar 2017 20:24:41 GMT

    [ https://issues.apache.org/jira/browse/HIVE-14669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941936#comment-15941936
] 

Pengcheng Xiong commented on HIVE-14669:
----------------------------------------

I am deferring this to Hive 3.0 as we are going to cut the first RC and it is not marked as
blocker. Please feel free to commit to the branch if this can be resolved before the release.

> 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
>
> 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
(v6.3.15#6346)

Mime
View raw message