Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Message-ID: <1109484649.39931267637427232.JavaMail.jira@brutus.apache.org>
Date: Wed, 3 Mar 2010 17:30:27 +0000 (UTC)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: avro-dev@hadoop.apache.org
Subject: [jira] Assigned: (AVRO-447) document protocol system error
In-Reply-To: <426577664.20771267578447183.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AVRO-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Cutting reassigned AVRO-447:
---------------------------------

    Assignee: Doug Cutting

> document protocol system error
> ------------------------------
>
>                 Key: AVRO-447
>                 URL: https://issues.apache.org/jira/browse/AVRO-447
>             Project: Avro
>          Issue Type: Bug
>          Components: spec
>    Affects Versions: 1.3.0
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>
> Currently Java internally adds a type at the start of each protocol message's error list for system errors.  This is used when an exception is encountered on the server while executing an RPC that does not match one of the messages declared errors.  The type is "string", so it will never conflict with another error, since all other errors are defined as records.
> For example, if a protocol has a message like:
> {code}
> "foo": {
>   "request": [],
>   "response": "null",
>   "errors": ["MyError"]
> }
> {code}
> Then errors are written and read with the schema ["string", "MyError"], although that schema never appears publicly.
> This should either be documented or changed.

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