[
https://issues.apache.org/jira/browse/HIVE-13025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137897#comment-15137897
]
Sushanth Sowmyan commented on HIVE-13025:
-----------------------------------------
Looks reasonable to me. +1.
That said, any preferences on setting the cause of the SchemaException
generated as ex itself? I see both sides to this : On the plus side, it's
additional info, and can be used to reason about where the isssue came from in
debugging at some point. On the negative side, it is additional info, and
clutter, and most of the time, unneeded extra elements in exception stack that
gets passed on back.
> need a better error message for when one needs to run schematool
> ----------------------------------------------------------------
>
> Key: HIVE-13025
> URL: https://issues.apache.org/jira/browse/HIVE-13025
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Priority: Blocker
> Attachments: HIVE-13025.patch
>
>
> Might as well fix it, since the RC is sunk and this was not obvious to the
> people testing it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
