[
https://issues.apache.org/jira/browse/HIVE-23037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17064413#comment-17064413
]
Peter Vary edited comment on HIVE-23037 at 3/22/20, 8:48 PM:
-------------------------------------------------------------
I am not sure we will only get UnsupportedOperationException here, and my guess
the original intent was that at any error we just return null and the caller
should handle the fallback. This would break this behavior (I agree that this
is not the best solution, but I would feel bad to bring this change in when I
do not see all the possible problems :()
Could we just change the logging? Which definitely needs fixing?
was (Author: pvary):
I am not sure we will only get UnsupportedOperationException here, and my guess
the original intent was that at any error we just return null and the caller
should handle the fallback. This would break this behavior (I agree that this
is not the best solution, but I would feel bad to bring this change in when I
do not see all the possible problems :()
> Print Logging Information for Exception in AcidUtils tryListLocatedHdfsStatus
> -----------------------------------------------------------------------------
>
> Key: HIVE-23037
> URL: https://issues.apache.org/jira/browse/HIVE-23037
> Project: Hive
> Issue Type: Improvement
> Reporter: David Mollitor
> Assignee: David Mollitor
> Priority: Minor
> Attachments: HIVE-23037.1.patch, HIVE-23037.2.patch
>
>
> Was recently trying to troubleshoot an issue and all I got for a log
> statement was:
> {code:none}
> Failed to get files with ID; using regular API: null
> {code}
> No stacktrace, no error message, nothing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
