[
https://issues.apache.org/jira/browse/HIVE-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770417#comment-13770417
]
Hive QA commented on HIVE-5198:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12603733/HIVE-5198.patch
{color:green}SUCCESS:{color} +1 3126 tests passed
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/793/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/793/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
> WebHCat returns exitcode 143 (w/o an explanation)
> -------------------------------------------------
>
> Key: HIVE-5198
> URL: https://issues.apache.org/jira/browse/HIVE-5198
> Project: Hive
> Issue Type: Bug
> Components: WebHCat
> Affects Versions: 0.11.0
> Reporter: Eugene Koifman
> Assignee: Eugene Koifman
> Fix For: 0.12.0, 0.13.0
>
> Attachments: HIVE-5198.patch
>
>
> The message might look like this:
> {"statement":"use default; show table extended like xyz;","error":"unable to
> show table: xyz","exec":{"stdout":"","stderr":"","exitcode":143}}
> WebHCat has a templeton.exec.timeout property which kills an HCat request
> (i.e. something like a DDL statement that gets routed to HCat CLI) if it
> takes longer than this timeout.
> Since WebHCat does a fork/exec to 'hcat' script, the timeout is implemented
> as SIGTERM sent to the subprocess. SIGTERM value is 15. So it's reported as
> 128 + 15 = 143.
> Error logging/reporting should be improved in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
