You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "BELUGA BEHR (JIRA)" <ji...@apache.org> on 2018/07/12 22:34:00 UTC
[jira] [Created] (HIVE-20159) Do Not Print StackTraces to STDERR in
ConditionalResolverSkewJoin
BELUGA BEHR created HIVE-20159:
----------------------------------
Summary: Do Not Print StackTraces to STDERR in ConditionalResolverSkewJoin
Key: HIVE-20159
URL: https://issues.apache.org/jira/browse/HIVE-20159
Project: Hive
Issue Type: Improvement
Components: Query Planning
Affects Versions: 3.0.0, 4.0.0
Reporter: BELUGA BEHR
https://github.com/apache/hive/blob/6d890faf22fd1ede3658a5eed097476eab3c67e9/ql/src/java/org/apache/hadoop/hive/ql/plan/ConditionalResolverSkewJoin.java#L121
{code}
} catch (IOException e) {
e.printStackTrace();
}
{code}
Introduce an SLF4J logger to this class and print a WARN level log message if the {{IOException}} from {{Utilities.listStatusIfExists}} is generated. I suggest WARN because the entire operation doesn't fail if this error happens. It continues on its way with the data that it was able to collect. I'm not sure if this is the intended behavior, but for now, an error message in the logging would be better.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)