Return-Path: Delivered-To: apmail-hadoop-pig-dev-archive@www.apache.org Received: (qmail 62778 invoked from network); 29 May 2009 18:36:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 May 2009 18:36:20 -0000 Received: (qmail 54058 invoked by uid 500); 29 May 2009 18:23:09 -0000 Delivered-To: apmail-hadoop-pig-dev-archive@hadoop.apache.org Received: (qmail 54049 invoked by uid 500); 29 May 2009 18:23:09 -0000 Mailing-List: contact pig-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: pig-dev@hadoop.apache.org Delivered-To: mailing list pig-dev@hadoop.apache.org Received: (qmail 54039 invoked by uid 99); 29 May 2009 18:23:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 May 2009 18:23:09 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 May 2009 18:23:06 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 920D8234C004 for ; Fri, 29 May 2009 11:22:45 -0700 (PDT) Message-ID: <1877953782.1243621365587.JavaMail.jira@brutus> Date: Fri, 29 May 2009 11:22:45 -0700 (PDT) From: "Jeff Hammerbacher (JIRA)" To: pig-dev@hadoop.apache.org Subject: [jira] Issue Comment Edited: (PIG-823) Hadoop Metadata Service In-Reply-To: <1032963963.1243619925551.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/PIG-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714539#action_12714539 ] Jeff Hammerbacher edited comment on PIG-823 at 5/29/09 11:20 AM: ----------------------------------------------------------------- Hey, Hadoop already has a metadata service (well defined at http://svn.apache.org/viewvc/hadoop/hive/trunk/metastore/if/hive_metastore.thrift) and a SQL implementation in production use at scale at several organizations. Can any of that work be reused for this purpose? It seems like duplicating effort across subprojects is a bad idea. Later, Jeff was (Author: hammer): Hey, Hadoop already had a metadata service (well defined at http://svn.apache.org/viewvc/hadoop/hive/trunk/metastore/if/hive_metastore.thrift) and a SQL implementation in production use at scale at several organizations. Can any of that work be reused for this purpose? It seems like duplicating effort across subprojects is a bad idea. Later, Jeff > Hadoop Metadata Service > ----------------------- > > Key: PIG-823 > URL: https://issues.apache.org/jira/browse/PIG-823 > Project: Pig > Issue Type: New Feature > Reporter: Olga Natkovich > > This JIRA is created to track development of a metadata system for Hadoop. The goal of the system is to allow users and applications to register data stored on HDFS, search for the data available on HDFS, and associate metadata such as schema, statistics, etc. with a particular data unit or a data set stored on HDFS. The initial goal is to provide a fairly generic, low level abstraction that any user or application on HDFS can use to store an retrieve metadata. Over time a higher level abstractions closely tied to particular applications or tools can be developed. > Over time, it would make sense for the metadata service to become a subproject within Hadoop. For now, the proposal is to make it a contrib to Pig since Pig SQL is likely to be the first user of the system. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.