Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Message-ID: <1739625629.1239639315228.JavaMail.jira@brutus>
Date: Mon, 13 Apr 2009 09:15:15 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: avro-dev@hadoop.apache.org
Subject: [jira] Commented: (AVRO-5) Add java versus python RPC
 interoperability tests
In-Reply-To: <19002670.1239447314834.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AVRO-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698424#action_12698424 ] 

Doug Cutting commented on AVRO-5:
---------------------------------

> it would be good to separate the interoperability tests from the other tests.

This is a good idea.  We should have both a self-contained test target for each implementation and an interop target for each.  The interop targets require that all other implementations are capable of correctly writing data and of making and receiving RPCs, which is difficult to ensure as we develop a new feature in each implementation.

> Add java versus python RPC interoperability tests
> -------------------------------------------------
>
>                 Key: AVRO-5
>                 URL: https://issues.apache.org/jira/browse/AVRO-5
>             Project: Avro
>          Issue Type: Test
>            Reporter: Sharad Agarwal
>            Assignee: Sharad Agarwal
>
> Add java versus python RPC interoperability tests.

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