Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7BD0DD312 for ; Mon, 10 Sep 2012 21:17:09 +0000 (UTC) Received: (qmail 38231 invoked by uid 500); 10 Sep 2012 21:17:08 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 38157 invoked by uid 500); 10 Sep 2012 21:17:08 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 38081 invoked by uid 99); 10 Sep 2012 21:17:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Sep 2012 21:17:08 +0000 Date: Tue, 11 Sep 2012 08:17:08 +1100 (NCT) From: "Hadoop QA (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1451241558.60065.1347311828730.JavaMail.jiratomcat@arcas> In-Reply-To: <153118434.52209.1342251455222.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HADOOP-8597) FsShell's Text command should be able to read avro data files MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-8597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452457#comment-13452457 ] Hadoop QA commented on HADOOP-8597: ----------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12544521/HADOOP-8597.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 1 new or modified test files. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 javadoc. The javadoc tool did not generate any warning messages. +1 eclipse:eclipse. The patch built with eclipse:eclipse. -1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in hadoop-common-project/hadoop-common. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/1427//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HADOOP-Build/1427//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-common.html Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1427//console This message is automatically generated. > FsShell's Text command should be able to read avro data files > ------------------------------------------------------------- > > Key: HADOOP-8597 > URL: https://issues.apache.org/jira/browse/HADOOP-8597 > Project: Hadoop Common > Issue Type: New Feature > Components: fs > Affects Versions: 2.0.0-alpha > Reporter: Harsh J > Assignee: Ivan Vladimirov Ivanov > Labels: newbie > Attachments: HADOOP-8597-2.patch, HADOOP-8597.patch, HADOOP-8597.patch > > > Similar to SequenceFiles are Apache Avro's DataFiles. Since these are getting popular as a data format, perhaps it would be useful if {{fs -text}} were to add some support for reading it, like it reads SequenceFiles. Should be easy since Avro is already a dependency and provides the required classes. > Of discussion is the output we ought to emit. Avro DataFiles aren't simple as text, nor have they the singular Key-Value pair structure of SequenceFiles. They usually contain a set of fields defined as a record, and the usual text emit, as available from avro-tools via http://avro.apache.org/docs/current/api/java/org/apache/avro/tool/DataFileReadTool.html, is in proper JSON format. > I think we should use the JSON format as the output, rather than a delimited form, for there are many complex structures in Avro and JSON is the easiest and least-work-to-do way to display it (Avro supports json dumping by itself). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira