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 B403B9C27 for ; Mon, 3 Oct 2011 22:33:27 +0000 (UTC) Received: (qmail 36074 invoked by uid 500); 3 Oct 2011 22:33:27 -0000 Delivered-To: apmail-avro-user-archive@avro.apache.org Received: (qmail 35932 invoked by uid 500); 3 Oct 2011 22:33:26 -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 35924 invoked by uid 99); 3 Oct 2011 22:33:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Oct 2011 22:33:26 +0000 X-ASF-Spam-Status: No, hits=2.1 required=5.0 tests=FREEMAIL_FROM,HK_RANDOM_ENVFROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of billmcn@gmail.com designates 209.85.214.43 as permitted sender) Received: from [209.85.214.43] (HELO mail-bw0-f43.google.com) (209.85.214.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Oct 2011 22:33:18 +0000 Received: by bkas6 with SMTP id s6so8050014bka.30 for ; Mon, 03 Oct 2011 15:32:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=fgGrCKbjOb7Yeq7hIF/xyHHQmkIFZ+PHVGrnu5Gg6ZY=; b=cxwNbFmvSgj6Y18cSKlFPEQD84rzdIiSCShx3jz0GU5eqIm5X5lo0LdH9/l2bXwcW4 o+CzAoz7wrfJPaXk4kGtK6MiG9fmuOEsS5eUEnV1JZy8zDdilNmjm2YgZ9ORXmxlwUYs aiBTyR3Awk8xv4gYR2W01R0GCxwzjr0lDjEbQ= MIME-Version: 1.0 Received: by 10.204.130.213 with SMTP id u21mr253577bks.170.1317681177979; Mon, 03 Oct 2011 15:32:57 -0700 (PDT) Received: by 10.204.116.136 with HTTP; Mon, 3 Oct 2011 15:32:57 -0700 (PDT) Date: Mon, 3 Oct 2011 15:32:57 -0700 Message-ID: Subject: Data incompatibility between Avro 1.4.1 and 1.5.4 From: "W.P. McNeill" To: Avro Mailing List Content-Type: multipart/alternative; boundary=0015173fe5568a6d0804ae6c8e86 X-Virus-Checked: Checked by ClamAV on apache.org --0015173fe5568a6d0804ae6c8e86 Content-Type: text/plain; charset=UTF-8 I have a bunch of data that I serialized using the Avro 1.4.1 library. I wanted use projection schemas with this data but I can't because of bug 793 (https://issues.apache.org/jira/browse/AVRO-793). So I changed my code to use Avro 1.5.4. When I try to deserialize the Avro 1.4.1 data with the new code built with Avro 1.5.4, I get the same runtime deserialization errors described in JIRA 793. Is this expected? Is there any way around it beyond reserializing all my data using Avro 1.5.4? (I think I'm asking whether JIRA 793 is just a problem with deserialization or a problem with the binary serialization format.) --0015173fe5568a6d0804ae6c8e86 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I have a bunch of data that I serialized using the Avro 1.4.1 library. I wa= nted use projection schemas with this data but I can't because of bug 7= 93 (https://issu= es.apache.org/jira/browse/AVRO-793). So I changed my code to use Avro 1= .5.4. When I try to deserialize the Avro 1.4.1 data with the new code built= with Avro 1.5.4, I get the same runtime deserialization errors described i= n JIRA 793.

Is this expected? Is there any way around it beyond reserial= izing all my data using Avro 1.5.4?

(I think I'= ;m asking whether JIRA 793 is just a problem with deserialization or a prob= lem with the binary serialization format.)

--0015173fe5568a6d0804ae6c8e86--