[
https://issues.apache.org/jira/browse/HIVE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905675#action_12905675
]
John Sichi commented on HIVE-1546:
----------------------------------
New dependencies: we don't prevent anyone from using it, but we can Javadoc
it as unstable. We can work out the language now in an updated patch since
there's currently no Javadoc on the factory interface.
Dependencies on AST/ANTLR: it does make such changes more expensive in terms
of impact analysis and migration, but it doesn't really prevent us in any way,
does it?
Given that we've agreed at the high level on the approach of creating Howl as a
wrapper around Hive (reusing as much as possible of what's already there), can
you suggest an alternative mechanism that addresses the requirements while
minimizing the injection of Howl behavior directly into Hive itself? If it
were something generic like a bitmask of allowed operations, I could kind of
see it, but the validation logic is more involved than that (and may become
even more so over time). I wasn't able to come up with anything clean on that
front myself, which is why I suggested the factoring approach to Pradeep
originally. Apologies for not getting stuff aired out sooner.
> Ability to plug custom Semantic Analyzers for Hive Grammar
> ----------------------------------------------------------
>
> Key: HIVE-1546
> URL: https://issues.apache.org/jira/browse/HIVE-1546
> Project: Hadoop Hive
> Issue Type: Improvement
> Components: Metastore
> Affects Versions: 0.7.0
> Reporter: Ashutosh Chauhan
> Assignee: Ashutosh Chauhan
> Fix For: 0.7.0
>
> Attachments: hive-1546-3.patch, hive-1546-4.patch, hive-1546.patch,
> hive-1546_2.patch
>
>
> It will be useful if Semantic Analysis phase is made pluggable such that
> other projects can do custom analysis of hive queries before doing metastore
> operations on them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
