Return-Path: 
 <dev-return-13525-apmail-avro-dev-archive=avro.apache.org@avro.apache.org>
X-Original-To: apmail-avro-dev-archive@www.apache.org
Delivered-To: apmail-avro-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 1E206110DE
	for <apmail-avro-dev-archive@www.apache.org>;
 Tue, 15 Apr 2014 07:50:06 +0000 (UTC)
Received: (qmail 72247 invoked by uid 500); 15 Apr 2014 07:50:04 -0000
Delivered-To: apmail-avro-dev-archive@avro.apache.org
Received: (qmail 71800 invoked by uid 500); 15 Apr 2014 07:50:01 -0000
Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@avro.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@avro.apache.org>
List-Post: <mailto:dev@avro.apache.org>
List-Id: <dev.avro.apache.org>
Reply-To: dev@avro.apache.org
Delivered-To: mailing list dev@avro.apache.org
Received: (qmail 71564 invoked by uid 99); 15 Apr 2014 07:49:58 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Apr 2014 07:49:58 +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 mika.ristimaki@gmail.com
 designates 209.85.215.49 as permitted sender)
Received: from [209.85.215.49] (HELO mail-la0-f49.google.com) (209.85.215.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Apr 2014 07:49:52 +0000
Received: by mail-la0-f49.google.com with SMTP id mc6so6534435lab.36
        for <multiple recipients>; Tue, 15 Apr 2014 00:49:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=content-type:mime-version:subject:from:in-reply-to:date:cc
         :message-id:references:to;
        bh=JIm2om2E4GWKNa5Tv6zz43o342fkldNa2++R2uESCE0=;
        b=yfJAEM8w8OM6w65hE9qlIb/7q42k3QL1uYmXN2hXRerVfHvQOtFHwdpv+v654nH2fm
         grdqgmMWXu8jZb0szVQ7X28UAe0yXfh0F01w9dHUUy5LV8T5ycjqWza0n1J1gPneNTSp
         6nd+BZW/Q1Jy0dGf2EytMcSwJFCXM9DVPGH4QUoOUitXSIU4WIRlBnsKkFMtoUCrtyrQ
         52vetRhdlUpm0VyqKDVCUqmYHYC8Ty6Mv5VMH/qinNuaNCWnU2o0BXkVTXfrOKMuFQax
         T9NVzFL4z15E+KDBxsLKxXqECOJMXWCGpjzS3lqK64EM459ZoyJRS9+qM8GnT0FysWcv
         Oiag==
X-Received: by 10.152.22.37 with SMTP id a5mr233488laf.4.1397548170257;
        Tue, 15 Apr 2014 00:49:30 -0700 (PDT)
Received: from [192.168.1.112] ([194.157.117.5])
        by mx.google.com with ESMTPSA id
 k2sm16516813lbm.23.2014.04.15.00.49.29
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Tue, 15 Apr 2014 00:49:29 -0700 (PDT)
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_54D2531B-754F-4ACA-B60B-57F66F391402"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Invalid sync! error
From: Mika Ristimaki <mika.ristimaki@gmail.com>
In-Reply-To: 
 <CANGA=eeLdyaD34VMfjSgEK-G_63FY_+rGuh05PN44=CVUgJ0jg@mail.gmail.com>
Date: Tue, 15 Apr 2014 10:49:28 +0300
Cc: dev@avro.apache.org
Message-Id: <DB093530-17B9-4F1F-B64C-83DA1FEA2FB9@gmail.com>
References: 
 <CANGA=eeveNraTVWr+Dof6dutrT3qhzcfUERYGhEa0Tm3hPyUTg@mail.gmail.com>
 <587B8E9A-C795-41F4-AB3E-8AD318F27DFC@gmail.com>
 <CANGA=eetseGUeWffFC9pr59R-joEq2eB+2NCLKrB_CVPHJcM1A@mail.gmail.com>
 <854D541E-70D1-46CB-8800-C0E0D2BD4C7C@gmail.com>
 <CANGA=eeLdyaD34VMfjSgEK-G_63FY_+rGuh05PN44=CVUgJ0jg@mail.gmail.com>
To: user@avro.apache.org
X-Mailer: Apple Mail (2.1510)
X-Virus-Checked: Checked by ClamAV on apache.org

--Apple-Mail=_54D2531B-754F-4ACA-B60B-57F66F391402
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Only updating the reading part should be enough.=20

-Mika
=20
On Apr 15, 2014, at 8:54 AM, amit nanda <amitwip@gmail.com> wrote:

> So do i need to update to 1.7.6 both while reading and writing, or =
only updating writing part is sufficient?
>=20
>=20
> On Mon, Apr 14, 2014 at 3:50 PM, Mika Ristimaki =
<mika.ristimaki@gmail.com> wrote:
> At least one issue related to reading data was fixed. Might be the one =
that you are facing or it might not. But the first thing I would =
recommend you to do is update the Avro lib.
>=20
> -Mika
>=20
> On Apr 14, 2014, at 11:59 AM, amit nanda <amitwip@gmail.com> wrote:
>=20
>> So is the issue fixed in Avro-C 1.7.6
>>=20
>>=20
>> On Mon, Apr 14, 2014 at 4:32 AM, Mika Ristimaki =
<mika.ristimaki@gmail.com> wrote:
>> Hi,
>>=20
>> Try first with Avro-C 1.7.6. There was at least one related bug fixed =
in that release.
>>=20
>> -Mika
>>=20
>> On Apr 14, 2014, at 11:28 AM, amit nanda <amitwip@gmail.com> wrote:
>>=20
>> > Hi,
>> >
>> > I am getting "Invalid sync!" error, while reading some of the while =
from HDFS. I can see there is already an jira ticket, but i am not sure =
is this is a problem is Hadoop core or Avro,
>> > Meaning is this is problem while writing the write and some =
precaution needs to be taken at that time?
>> >
>> > I am using avro 1.7.5 C library.
>> >
>> >
>> > Thanks
>> > Amit
>>=20
>>=20
>=20
>=20


--Apple-Mail=_54D2531B-754F-4ACA-B60B-57F66F391402--