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 D88D6F51E for ; Thu, 4 Apr 2013 18:15:17 +0000 (UTC) Received: (qmail 38422 invoked by uid 500); 4 Apr 2013 18:15:17 -0000 Delivered-To: apmail-avro-dev-archive@avro.apache.org Received: (qmail 37669 invoked by uid 500); 4 Apr 2013 18:15:16 -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 37647 invoked by uid 99); 4 Apr 2013 18:15:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Apr 2013 18:15:16 +0000 Date: Thu, 4 Apr 2013 18:15:15 +0000 (UTC) From: "Jeremy Kahn (JIRA)" To: dev@avro.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AVRO-1289) Python: Schema objects should polymorphically interact with data-walker interface MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jeremy Kahn created AVRO-1289: --------------------------------- Summary: Python: Schema objects should polymorphically interact with data-walker interface Key: AVRO-1289 URL: https://issues.apache.org/jira/browse/AVRO-1289 Project: Avro Issue Type: Improvement Components: python Affects Versions: 1.7.5 Reporter: Jeremy Kahn Assignee: Jeremy Kahn Priority: Minor Fix For: 1.8.0 Python {{avro.schema}} objects should be able to call back to a general data-and-schema parallel-walker ("validate" would be one of those, but so could be "default-filler"). There should be an {{avro.walker}} interface that owns the parallel state (a datum-reader/deserializer, a datum-writer/serializer, a validator, or a default-filler -- see AVRO-1265). Schema polymorphism would allow us to eliminate the large (and highly redundant) function-dispatch methods in {{avro.io}} by making the {{avro.schema.Schema}} subclass responsible for calling back to the {{avro.walker}} object. Assigning this to v1.8.0 because it may be difficult to duplicate *every* behavior of 1.7.* with the same function signatures, especially where this refactor may be eliminate entire classes. This factoring ought to make it easier to improve or extend objects that meet this {{walker}} interface -- validators & serializers might be able to store more state about their position within a record, for example, to yield more informative error messages upon mismatch (as requested by Jonathan Coveney on the user mailing list). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira