[
https://issues.apache.org/jira/browse/HIVE-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415980#comment-13415980
]
Santhosh Raman commented on HIVE-3169:
--------------------------------------
Since the old diff and new diff are pretty different, I have created a new diff
for this:
https://reviews.facebook.net/D4167
> Add a way to differentiate between hooks that should/should not fail a query
> ----------------------------------------------------------------------------
>
> Key: HIVE-3169
> URL: https://issues.apache.org/jira/browse/HIVE-3169
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Santhosh Raman
> Assignee: Santhosh Raman
>
> Right now, if any hook fails the query fails. In particular if a post hook
> fails, even if the query itself succeeded, it will fail because of this.
> In some cases, this may be desired behavior, e.g. if the Replication Hook
> fails the output will not be replicated (there are arguments for and against
> this but that is probably best left for a separated discussion).
> However, if something like the sample concurrency hook fails, we could just
> leave concurrency untouched, display a warning to the user (to hopefully
> either provoke a Hive Users post from the user or at least have it show up in
> the log monitor), and continue the query.
> We need to add a way to differentiate between these hooks and to add that
> error handling.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
