hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Steinbach (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-1546) Ability to plug custom Semantic Analyzers for Hive Grammar
Date Thu, 02 Sep 2010 21:47:57 GMT

    [ https://issues.apache.org/jira/browse/HIVE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905686#action_12905686

Carl Steinbach commented on HIVE-1546:

bq. we've agreed at the high level on the approach of creating Howl as a wrapper around Hive

I thought Howl was supposed to be a wrapper around (and replacement for) the Hive metastore,
not all of Hive.

I think there are clear advantages to Hive and Howl sharing the same metastore code as long
as they access this facility through the public API, but can't say the same for the two projects
using the same CLI code if it means allowing external projects to depend on loosely defined
set of internal APIs. What benefits are we hoping to achieve by having Howl and Hive share
the same CLI code, especially if Howl is only interested in a small part of it? What are the
drawbacks of instead encouraging the Howl project to copy the CLI code and maintain their
own version?

> 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.

View raw message