[ https://issues.apache.org/jira/browse/HIVE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905665#action_12905665
]
Carl Steinbach commented on HIVE-1546:
--------------------------------------
bq. Can we get agreement from the Howl team that even though we're introducing this dependency
now, we will not let its existence hinder future semantic analyzer refactoring within Hive?
What about other projects that use this feature? How do we get them to agree to this, or how
do we prevent them from using it? The new configuration property is documented in hive-default.xml,
which implies that it's open to everyone.
bq. one possible refinement would be to limit the public interface to just validation (as
opposed to full semantic analysis). In that case, we would have HiveStmtValidatorFactory producing
HiveStmtValidator with just a single method validate().
This reduces the scope of the dependency, but doesn't eliminate it. Plugins would presumably
depend on the structure of the AST that they are trying to validate, which in turn would limit
our ability to refactor the grammar or to replace ANTLR with another parser generator.
> 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.