hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laszlo Bodor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-14669) Have the actual error reported when a q test fails instead of having to go through the logs
Date Fri, 03 May 2019 11:09:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-14669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Laszlo Bodor updated HIVE-14669:
--------------------------------
    Attachment: HIVE-14469.03.patch

> 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,
HIVE-14469.03.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)

Mime
View raw message