Return-Path: Delivered-To: apmail-avro-user-archive@www.apache.org Received: (qmail 96154 invoked from network); 6 Nov 2010 18:25:27 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 Nov 2010 18:25:27 -0000 Received: (qmail 2974 invoked by uid 500); 6 Nov 2010 18:25:58 -0000 Delivered-To: apmail-avro-user-archive@avro.apache.org Received: (qmail 2895 invoked by uid 500); 6 Nov 2010 18:25:57 -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 2887 invoked by uid 99); 6 Nov 2010 18:25:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Nov 2010 18:25:57 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [206.190.48.228] (HELO web52705.mail.re2.yahoo.com) (206.190.48.228) by apache.org (qpsmtpd/0.29) with SMTP; Sat, 06 Nov 2010 18:25:48 +0000 Received: (qmail 39599 invoked by uid 60001); 6 Nov 2010 18:25:27 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1289067926; bh=i8BHb7s0wfrGyVC25axEFkpcqnHT64ZoCRpn+nMyjXk=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=oGe0wOZLmic2BnVN8InlFJMsodmeFrCb24z8OmeXvcC9LoTnU4qYHgrM2CEz5qdHIzt7d1YBqvCDL/PBq1EKZoYTo2pAlzd8ChWqITa/9GVbIgV44fS6UVxAbUowYsIYIKkJRtOW5mrH3B+AgKopw76/a5TWiLPRH5dRQAUrgGg= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=SpcB5FcyCjhGwLsB/1F8/S9HHK+f5nLp7EWgASn6YLSpJUAJPwTCodnVqQxO734BHV5oo4dv8W4UYmEvDJTlfIrdQGfrytZlmBM6em2wP+tPZJoojy4x83nTBK1GW0H17Ws7eca33Hamb18gh2AWco+bT2ltAbSLkp9GnAjQD88=; Message-ID: <974461.39510.qm@web52705.mail.re2.yahoo.com> X-YMail-OSG: 7fd.zC0VM1l2zNiYoxThxCJi21kPF5wOMQSeUbhPYARy4E0 06KqCcpBgVjSEoc3pw33yfIRpbMNomXGrQOhQeWeGebrCWhCTqyBOZMqihcS Fpe42lavJR7IiO1cvmnoWPwWLaqZQBSRhdK70PuDZYi0D8WcJ0j6z_FDcS9c t408.7VsotKic9iKy4XyFOECo2KlOpQ4A3rsC6vGzisyD.8EgOSNdz.l7iRE mv67vTikni.drxq_dxTi02CtDKtje8InqybzyiebgcxjXoOPBNYNtaD17h6d DdwH.gj9BSw7YIfs1ueGKL8vwXeTZy6LAEHAYfw7OJ192Td_X9vubYrbKeyY ZlGDv6x8tUfULvPi2xD_63hW9cTgNnhHEgm4- Received: from [24.4.123.61] by web52705.mail.re2.yahoo.com via HTTP; Sat, 06 Nov 2010 11:25:26 PDT X-Mailer: YahooMailWebService/0.8.107.284920 Date: Sat, 6 Nov 2010 11:25:26 -0700 (PDT) From: Douglas Campbell Reply-To: Douglas Campbell Subject: Re: 1.2 to 1.4 datafile conversion To: "user@avro.apache.org" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1520806454-1289067926=:39510" X-Virus-Checked: Checked by ClamAV on apache.org --0-1520806454-1289067926=:39510 Content-Type: text/plain; charset=us-ascii Thanks for the info Doug and the patch looks promising. So our logic for replacement could be something like upon datafile read request, try to load with 1.4 if fail, try with 1.2 reader you provided, get records, save out with 1.4 after update Should that be doable with what you've provided? From: Doug Cutting To: user@avro.apache.org Cc: Sent: Thursday, November 4, 2010 2:33:10 PM Subject: Re: 1.2 to 1.4 datafile conversion On 11/03/2010 03:11 PM, Douglas Campbell wrote: > Are there any tools for this because as far as we can tell 1.2 datafiles > are unreadable by 1.4 apis? Not that I know of. I didn't think anyone had used the 1.2 datafile format! But, if some did, a format converter would be a good tool to have. I filed a Jira issue about this: https://issues.apache.org/jira/browse/AVRO-692 I attached a patch to that that adds a class that should be able to read 1.2-format files. Rewriting them in the current format should then be simple. Do you require a command-line based tool? Please follow up on that issue. Thanks, Doug --0-1520806454-1289067926=:39510 Content-Type: text/html; charset=us-ascii
Thanks for the info Doug and the patch looks promising.

So our logic for replacement could be something like

upon datafile read request,
try to load with 1.4
    if fail, try with 1.2 reader you provided,
get records, save out with 1.4 after update

Should that be doable with what you've provided?

From: Doug Cutting <cutting@apache.org>
To: user@avro.apache.org
Cc:
Sent: Thursday, November 4, 2010 2:33:10 PM
Subject: Re: 1.2 to 1.4 datafile conversion

On 11/03/2010 03:11 PM, Douglas Campbell wrote:
> Are there any tools for this because as far as we can tell 1.2 datafiles
> are unreadable by 1.4 apis?

Not that I know of.  I didn't think anyone had used the 1.2 datafile format!  But, if some did, a format converter would be a good tool to have.

I filed a Jira issue about this:

https://issues.apache.org/jira/browse/AVRO-692

I attached a patch to that that adds a class that should be able to read 1.2-format files.  Rewriting them in the current format should then be simple.  Do you require a command-line based tool?

Please follow up on that issue.

Thanks,

Doug



--0-1520806454-1289067926=:39510--