Return-Path: X-Original-To: apmail-avro-user-archive@www.apache.org Delivered-To: apmail-avro-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 8BDD517B3E for ; Fri, 26 Jun 2015 14:12:52 +0000 (UTC) Received: (qmail 93415 invoked by uid 500); 26 Jun 2015 14:12:52 -0000 Delivered-To: apmail-avro-user-archive@avro.apache.org Received: (qmail 93341 invoked by uid 500); 26 Jun 2015 14:12:52 -0000 Mailing-List: contact user-help@avro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@avro.apache.org Delivered-To: mailing list user@avro.apache.org Received: (qmail 93331 invoked by uid 99); 26 Jun 2015 14:12:52 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Jun 2015 14:12:52 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id BAC011A61C9 for ; Fri, 26 Jun 2015 14:12:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3 X-Spam-Level: *** X-Spam-Status: No, score=3 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id yjpZTABnfrET for ; Fri, 26 Jun 2015 14:12:45 +0000 (UTC) Received: from mail-lb0-f177.google.com (mail-lb0-f177.google.com [209.85.217.177]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id D14744C0E8 for ; Fri, 26 Jun 2015 14:12:44 +0000 (UTC) Received: by lbnk3 with SMTP id k3so65310802lbn.1 for ; Fri, 26 Jun 2015 07:11:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=mHPmp62XiWS5tpnf9tuM3DUS+3cIy7LPIpAOyx8Veio=; b=XjlAUGpwSimHwP9lfVZ7zMmgEkcScFflItH1KC/0gCt8gMv+gLet7Z5o2XCa75h3oC 6cjVSc+yTXNdfvACaKEME7V0P9cKNDdcRPC1AastTOes22gaaMGj/tedoow0f6nwSwSH PPgg2r9vwO2cg1klD4262aqm6TKPAgtZPgziNzLAwXcPvpQyECHC/hnqIJrPqbyrF3fa 1BDQSm5SQSo5QnBE37AjRnvhoiuB79R6LMPbODShASt97ycv3aLE9tVTu+V7NBnp0S2Y coEHh3MR5ZLFSbkbRE28So/II2yVtM63wXfR+gB5FiNfKZFm+CUmiMf8pkZnQIwAXzL2 hY7w== X-Gm-Message-State: ALoCoQl4LexRpV4ZzRhTHN1a8vrp1tunsu4KoX6RBJGcvetAT/xG167C04Y7Nz+hLLoKmYdrL4X9 X-Received: by 10.112.210.137 with SMTP id mu9mr1714302lbc.95.1435327918782; Fri, 26 Jun 2015 07:11:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.148.135 with HTTP; Fri, 26 Jun 2015 07:11:39 -0700 (PDT) In-Reply-To: <2C72C62BF031534A989ACB0F0E5DC174E1570B15@HYDMAIL006.yash.com> References: <2C72C62BF031534A989ACB0F0E5DC174E1570B15@HYDMAIL006.yash.com> From: Sean Busbey Date: Fri, 26 Jun 2015 09:11:39 -0500 Message-ID: Subject: Re: Is Avro Splittable? To: "user@avro apache. org" Content-Type: multipart/alternative; boundary=001a11c3d7dcbc500705196c5227 --001a11c3d7dcbc500705196c5227 Content-Type: text/plain; charset=UTF-8 Avro Container Files are always splittable[1]. They're the way you will commonly interact with Avro serialized data. Data serialized as Avro's binary encoding is not splittable by itself, because the encoding includes no markers[2]. This may be the source of the disconnect you're finding in online docs. [1]: http://avro.apache.org/docs/1.7.7/spec.html#Object+Container+Files [2]: http://avro.apache.org/docs/1.7.7/spec.html#Data+Serialization On Thu, Jun 25, 2015 at 12:54 AM, Ankur Jain wrote: > Hello, > > > > I am reading various forms and docs, somewhere it is mentioned that avro > is splittable and somewhere non-splittable. > > So which one is right?? > > > > Regards, > > Ankur > > > Information transmitted by this e-mail is proprietary to YASH > Technologies and/ or its Customers and is intended for use only by the > individual or entity to which it is addressed, and may contain information > that is privileged, confidential or exempt from disclosure under applicable > law. If you are not the intended recipient or it appears that this mail has > been forwarded to you without proper authority, you are notified that any > use or dissemination of this information in any manner is strictly > prohibited. In such cases, please notify us immediately at info@yash.com > and delete this mail from your records. > -- Sean --001a11c3d7dcbc500705196c5227 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Avro Container Files are always splittable[1]. They're= the way you will commonly interact with Avro serialized data.

Data serialized as Avro's binary encoding is not splittable by i= tself, because the encoding includes no markers[2]. This may be the source = of the disconnect you're finding in online docs.
[2]:=C2=A0<= a href=3D"http://avro.apache.org/docs/1.7.7/spec.html#Data+Serialization">h= ttp://avro.apache.org/docs/1.7.7/spec.html#Data+Serialization

On Thu, Jun 25,= 2015 at 12:54 AM, Ankur Jain <ankur.jain@yash.com> wrote:=

Hello,

=C2=A0

I am reading various forms and docs, somewhere it is= mentioned that avro is splittable and somewhere non-splittable.<= /u>

So which one is right??

=C2=A0

Regards,

Ankur

=C2=A0

Information transmitted by this e-mail is proprietary to YASH Technologies = and/ or its Customers and is intended for use only by the individual or ent= ity to which it is addressed, and may contain information that is privilege= d, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears = that this mail has been forwarded to you without proper authority, you are = notified that any use or dissemination of this information in any manner is= strictly prohibited. In such cases, please notify us immediately at info@yash.com and delete this mail from your records.



--
Sean
--001a11c3d7dcbc500705196c5227--