Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0707DD5BA for ; Tue, 21 May 2013 16:53:08 +0000 (UTC) Received: (qmail 66779 invoked by uid 500); 21 May 2013 16:53:03 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 66648 invoked by uid 500); 21 May 2013 16:53:03 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 66639 invoked by uid 99); 21 May 2013 16:53:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 May 2013 16:53:03 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rahul.rec.dgp@gmail.com designates 209.85.128.177 as permitted sender) Received: from [209.85.128.177] (HELO mail-ve0-f177.google.com) (209.85.128.177) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 May 2013 16:52:57 +0000 Received: by mail-ve0-f177.google.com with SMTP id ox1so661537veb.36 for ; Tue, 21 May 2013 09:52:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=V+aCxS94RWyX//o2nqZu+tMh12YnR7TAVKq3oQ0R8jU=; b=ad52r9oCGkG1jNHjMNQ4qgOlxFfvE5THgSoU1jipHbw21sszUSTQ8aPzX212VtzEtq ONRvbD7snH1+0+Z5GR0JMiZxlKGPWGyDLAXTiz8CMn2rccJG0lBO08ArBywwAYASGShB 6SnSNi1fjZ74KzBx3aAzFmDSY5AJO9d/9UJnQzN9jJloDUntYcffuNASzVeEd7pIUvSS SEQjm7gL0mehycWYgYgjZbrt2homVCi5IYaMud7TmjVVuWKGhYmH4jRhwdnIx87Q1qKt JBZQb+2FqZgfSpU97EvQdVJUGkh8DAIHAG2d8fovl0AJgbkII4KNWUn7QZUrks8mFDdR XDew== X-Received: by 10.58.200.131 with SMTP id js3mr1254535vec.33.1369155156793; Tue, 21 May 2013 09:52:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.59.6.68 with HTTP; Tue, 21 May 2013 09:52:16 -0700 (PDT) In-Reply-To: <9240AD66F4BBBA4088ACAAC15099237B1EB514E4@CH1PRD0811MB430.namprd08.prod.outlook.com> References: <9240AD66F4BBBA4088ACAAC15099237B1EB514E4@CH1PRD0811MB430.namprd08.prod.outlook.com> From: Rahul Bhattacharjee Date: Tue, 21 May 2013 22:22:16 +0530 Message-ID: Subject: Re: Viewing snappy compressed files To: "user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=047d7bd6b2dac3957a04dd3d463a X-Virus-Checked: Checked by ClamAV on apache.org --047d7bd6b2dac3957a04dd3d463a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I haven't tried this with snappy , but you can try using hadoop fs -text On Tue, May 21, 2013 at 8:28 PM, Robert Rapplean < robert.rapplean@trueffect.com> wrote: > Hey, there. My Google skills have failed me, and I hope someone here can > point me in the right direction.**** > > ** ** > > We=E2=80=99re storing data on our Hadoop cluster in Snappy compressed for= mat. When we pull a raw file down and try to read it, however, the Snappy l= ibraries don=E2=80=99t know how to read the files. They tell me that the st= ream is missing the snappy identifier. I tried inserting 0xff 0x06 0x00 0x0= 0 0x73 0x4e 0x61 0x50 0x70 0x59 into the beginning of the file, but that di= dn=E2=80=99t do it. > > Can someone point me to resources for figuring out how to uncompress thes= e files without going through Hadoop?**** > > ** ** > > ________________________________________**** > > Robert Rapplean**** > > Senior Software Engineer**** > > 303-872-2256 direct | 303.438.9597 main | www.trueffect.com**** > > ** ** > --047d7bd6b2dac3957a04dd3d463a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I haven't tried this with snappy , but =
you can try using hadoop fs -text <path>

On Tue, May 21, 2013 at 8:28 PM, Robert = Rapplean <robert.rapplean@trueffect.com> wrote:<= br>

Hey, there. My Google skills have failed me, and I h= ope someone here can point me in the right direction.

=C2=A0
We=E2=80=99re storing data on our Hadoop cluster in Snappy compressed =
format. When we pull a raw file down and try to read it, however, the Snapp=
y libraries don=E2=80=99t know how to read the files. They tell me that the=
 stream is missing the snappy identifier. I tried inserting 0xff 0x06 0x00 =
0x00 0x73 0x4e 0x61 0x50 0x70 0x59 into the beginning of the file, but that=
 didn=E2=80=99t do it.



Can someone point me to resources for figuring out how to uncompress th=
ese files without going through Hadoop?
=C2=A0

________________________________________

Robert Rapplean

Senior Software Engineer

303-872-2256=C2=A0 direct=C2=A0 | 303.438.9597=C2=A0 m= ain | www.trueffect.= com

=C2=A0

--047d7bd6b2dac3957a04dd3d463a--