Return-Path: 
 <user-return-3430-apmail-avro-user-archive=avro.apache.org@avro.apache.org>
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 0599817ED4
	for <apmail-avro-user-archive@www.apache.org>;
 Sun, 23 Nov 2014 18:40:44 +0000 (UTC)
Received: (qmail 46629 invoked by uid 500); 23 Nov 2014 18:40:43 -0000
Delivered-To: apmail-avro-user-archive@avro.apache.org
Received: (qmail 46549 invoked by uid 500); 23 Nov 2014 18:40:43 -0000
Mailing-List: contact user-help@avro.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@avro.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@avro.apache.org>
List-Post: <mailto:user@avro.apache.org>
List-Id: <user.avro.apache.org>
Reply-To: user@avro.apache.org
Delivered-To: mailing list user@avro.apache.org
Received: (qmail 46538 invoked by uid 99); 23 Nov 2014 18:40:43 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Nov 2014 18:40:43 +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 (athena.apache.org: domain of junrao@gmail.com designates
 209.85.214.180 as permitted sender)
Received: from [209.85.214.180] (HELO mail-ob0-f180.google.com)
 (209.85.214.180)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Nov 2014 18:40:38 +0000
Received: by mail-ob0-f180.google.com with SMTP id wp4so6272754obc.11
        for <user@avro.apache.org>; Sun, 23 Nov 2014 10:40:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=WPZr8VLlq1qFlJX8CWPMZ1lRKDnWJYj79lWrH1fIBeM=;
        b=Q5p9gtwTzTcTCG6Je5lN09Wk42OzPABRDzwemh+VQsCGg98Tyu/KsddFlA7nzQS7we
         1XGQScDyVqb4ZJjORTrZcxwMyfuo5EU7/8rTd3tS2C00H5AHCDivvMLzR9JiN8UEQQdX
         qI0an3FpibI6Sp7Ldi6e/mywg5ebI35GLTdp1lV4qLlMC9pAaOWWr3NKsNCrtBX85Xfn
         qZmPU3mysO/a3iELh560eIsNWKr0m2Ouo9H6uau3FikE8tSs2EWKPxfaZIqtNaAtNox0
         NV2i48pytjPdgHj1mPi9OsRLVz4+irqoUDaj09merNJp97+6r/tB7WrqOPbrIeug87V3
         7XcQ==
MIME-Version: 1.0
X-Received: by 10.202.193.135 with SMTP id r129mr8420204oif.66.1416768017587;
 Sun, 23 Nov 2014 10:40:17 -0800 (PST)
Received: by 10.60.33.170 with HTTP; Sun, 23 Nov 2014 10:40:17 -0800 (PST)
Date: Sun, 23 Nov 2014 10:40:17 -0800
Message-ID: 
 <CAFbh0Q2WMn7ixgE44MD5AJViasAe0DsxP+hSVULYwCGRGdZ9gw@mail.gmail.com>
Subject: any optimization in reading a partial schema in the decoder?
From: Jun Rao <junrao@gmail.com>
To: user@avro.apache.org
Content-Type: multipart/alternative; boundary=001a113dc2a66ae66905088b0292
X-Virus-Checked: Checked by ClamAV on apache.org

--001a113dc2a66ae66905088b0292
Content-Type: text/plain; charset=UTF-8

Hi,

Suppose that the writer schema has a header record, if I set the reader
schema to be just the header part in a GenericDatumReader, does it
construct the header record efficiently w/o deserializing the whole record
first?

Thanks,

Jun

--001a113dc2a66ae66905088b0292
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>Suppose that the writer schema has =
a header record, if I set the reader schema to be just the header part in a=
 GenericDatumReader, does it construct the header record efficiently w/o de=
serializing the whole record first?</div><div><br></div><div>Thanks,</div><=
div><br></div><div>Jun</div></div>

--001a113dc2a66ae66905088b0292--