[
https://issues.apache.org/jira/browse/HIVE-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737895#comment-16737895
]
Mani M commented on HIVE-8346:
------------------------------
HI [~pvary],
As of the ticket is raised only the error message was written in the log
Component. But after subsequent fix this had been changed to include the full
exception in the log file
changed as the part of HIVE-9860
and subsequently changed in HIVE-13183
!image-2019-01-09-17-31-15-247.png!
Screenshot is attached herewith.
So, I think, this Jira ticket is no-longer valid, we can close this.
> MapRedLocalTask Error Handling
> ------------------------------
>
> Key: HIVE-8346
> URL: https://issues.apache.org/jira/browse/HIVE-8346
> Project: Hive
> Issue Type: Bug
> Components: Logging
> Affects Versions: 0.14.0
> Reporter: Szehon Ho
> Assignee: Mani M
> Priority: Minor
> Labels: newbie
> Attachments: image-2019-01-09-17-31-15-247.png
>
>
> If there are any exceptions trying to fork a local task, the exception
> message is logged but not the stack trace. There can be a lot of issues
> forking a process, so we should log the stack trace for better debuggability.
> Code in MapRedLocalTask.executeInChildJVM(DriverContext ctx):
> {code}
> } catch (Exception e) {
> e.printStackTrace();
> LOG.error("Exception: " + e.getMessage());
> return (1);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
