Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Message-ID: <1297931617.1243898947582.JavaMail.jira@brutus>
Date: Mon, 1 Jun 2009 16:29:07 -0700 (PDT)
From: "Scott Banachowski (JIRA)" <jira@apache.org>
To: avro-dev@hadoop.apache.org
Subject: [jira] Created: (AVRO-42) C++ avro
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

C++ avro
--------

                 Key: AVRO-42
                 URL: https://issues.apache.org/jira/browse/AVRO-42
             Project: Avro
          Issue Type: New Feature
            Reporter: Scott Banachowski
            Priority: Minor


I have a C++ implementation for Avro to contribute.  I opened this issue to submit a patch.

Overview:
Serializer/Parser- objects for writing/reading raw binary.
xxxSchema- objects for composing schemas.
ValidSchema- a schema object that has been converted to a parse tree (with some sanity checks).
ValidSchema.toJson() writes the schema as a json object.
ValidatingSerializer/ValidatingParser-  check that reads/writes match the expected schema type (more expensive than the raw serializer/parser but they detect errors, and allow dynamic discovery of parsed data/attributes).
Compiler (compileJsonSchema())-  converts a Json string schema to a ValidSchema.
Code Generation (experimental) - given a schema it generates C++ objects of the same data types, and the code to serialize and parse it.

What's missing: Defaults are not yet supported.  Resolving schema conflicts is not yet supported.  And the file and rpc containers are not yet implemented.  Documentation, sparse.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.