Return-Path: 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 8C3BC9355 for ; Fri, 23 Sep 2011 04:13:51 +0000 (UTC) Received: (qmail 97784 invoked by uid 500); 23 Sep 2011 04:13:51 -0000 Delivered-To: apmail-avro-dev-archive@avro.apache.org Received: (qmail 97615 invoked by uid 500); 23 Sep 2011 04:13:50 -0000 Mailing-List: contact dev-help@avro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@avro.apache.org Delivered-To: mailing list dev@avro.apache.org Received: (qmail 97601 invoked by uid 99); 23 Sep 2011 04:13:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Sep 2011 04:13:50 +0000 X-ASF-Spam-Status: No, hits=-2000.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Sep 2011 04:13:47 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 5ED9DAAC80 for ; Fri, 23 Sep 2011 04:13:26 +0000 (UTC) Date: Fri, 23 Sep 2011 04:13:26 +0000 (UTC) From: "Lucas Martin-King (JIRA)" To: dev@avro.apache.org Message-ID: <1899888608.4963.1316751206385.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1935255381.4951.1316750966136.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (AVRO-893) New value_t API does not write out spec compatible files - header, metadata and blocks are missing. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/AVRO-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Martin-King updated AVRO-893: ----------------------------------- Description: We have switched over to the new value_t API for our application, as it provides more AVRO types that we need (enum, array, etc), however we have noticed that there isn't a way to write out a spec compatible AVRO file. The old API was able to write out a header as well as the schema, the finally each data block (and sync marker). I could possibly try and re-implement this myself, however I am unsure as to the design (how it would fit into the new datum API). was: We have switched over to the new datum_t API for our application, as it provides more AVRO types that we need (enum, array, etc), however we have noticed that there isn't a way to write out a spec compatible AVRO file. The old API was able to write out a header as well as the schema, the finally each data block (and sync marker). I could possibly try and re-implement this myself, however I am unsure as to the design (how it would fit into the new datum API). Summary: New value_t API does not write out spec compatible files - header, metadata and blocks are missing. (was: New datum_t API does not write out spec compatible files - header, metadata and blocks are missing.) > New value_t API does not write out spec compatible files - header, metadata and blocks are missing. > --------------------------------------------------------------------------------------------------- > > Key: AVRO-893 > URL: https://issues.apache.org/jira/browse/AVRO-893 > Project: Avro > Issue Type: Improvement > Components: c > Affects Versions: 1.5.4 > Environment: N/A > Reporter: Lucas Martin-King > Labels: file > Original Estimate: 24h > Remaining Estimate: 24h > > We have switched over to the new value_t API for our application, as it provides more AVRO types that we need (enum, array, etc), however we have noticed that there isn't a way to write out a spec compatible AVRO file. > The old API was able to write out a header as well as the schema, the finally each data block (and sync marker). > I could possibly try and re-implement this myself, however I am unsure as to the design (how it would fit into the new datum API). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira