[
https://issues.apache.org/jira/browse/HIVE-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988350#action_12988350
]
Ashutosh Chauhan commented on HIVE-1936:
----------------------------------------
Not really. I was just wondering why would you want to do it in a series of
hooks, rather then doing all of it in one hook, because it seems list must all
always be complete and hooks in that list aren't going to be optional.
Regardless of that, I had the similar requirement and what I had done was to
have a top level hook, which keeps a list of hook with it and invokes an
appropriate hook depending on the parse tree and context. Depending on what you
are trying to achieve that may or may not work in your case. I can point you to
code for it, in case you want to take a look.
> hive.semantic.analyzer.hook cannot have multiple values
> -------------------------------------------------------
>
> Key: HIVE-1936
> URL: https://issues.apache.org/jira/browse/HIVE-1936
> Project: Hive
> Issue Type: Bug
> Reporter: Namit Jain
> Assignee: Siying Dong
> Fix For: 0.7.0
>
>
> It should support comma separated values like hive pre/post execution hooks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
