[
https://issues.apache.org/jira/browse/HADOOP-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615772#action_12615772
]
Sameer Paranjpye commented on HADOOP-3601:
------------------------------------------
> What's the bar? Releases need to be approved by the Hadoop PMC, and, more
> generally, the PMC must monitor all activity in the project.
> I don't see how a sandbox designation would help oversight.
It's for the community to decide what the bar is. It's clearly lower than that
required for a TLP. What's the bar for moving something from contrib to a
sub-project? It's not well defined, but can be thought about and made concrete.
Sandbox projects wouldn't create traffic on the core lists and wouldn't hold up
core patches or releases. The patch process can be modified to not consider
contrib tests for core patches. But core releases would not be possible without
contrib tests passing.
> We don't need more options. We have well-understood options that serve us
> well: core, contrib, sub-projects, TLPs, etc.
We have well understood options, all of whose shortcomings have been discussed
in this thread. It may be that no better way exists, but I don't follow the
reasoning behind spontaneously rejecting all proposals.
> Hive as a contrib project
> -------------------------
>
> Key: HADOOP-3601
> URL: https://issues.apache.org/jira/browse/HADOOP-3601
> Project: Hadoop Core
> Issue Type: New Feature
> Affects Versions: 0.17.0
> Reporter: Joydeep Sen Sarma
> Priority: Minor
> Attachments: HiveTutorial.pdf
>
> Original Estimate: 1080h
> Remaining Estimate: 1080h
>
> Hive is a data warehouse built on top of flat files (stored primarily in
> HDFS). It includes:
> - Data Organization into Tables with logical and hash partitioning
> - A Metastore to store metadata about Tables/Partitions etc
> - A SQL like query language over object data stored in Tables
> - DDL commands to define and load external data into tables
> Hive's query language is executed using Hadoop map-reduce as the execution
> engine. Queries can use either single stage or multi-stage map-reduce. Hive
> has a native format for tables - but can handle any data set (for example
> json/thrift/xml) using an IO library framework.
> Hive uses Antlr for query parsing, Apache JEXL for expression evaluation and
> may use Apache Derby as an embedded database for MetaStore. Antlr has a BSD
> license and should be compatible with Apache license.
> We are currently thinking of contributing to the 0.17 branch as a contrib
> project (since that is the version under which it will get tested internally)
> - but looking for advice on the best release path.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.