avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Hammerbacher (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-447) document protocol system error
Date Fri, 04 Jun 2010 01:23:54 GMT

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

Jeff Hammerbacher commented on AVRO-447:
----------------------------------------

Hey Doug,

Also, I used the term "declared errors" instead of "specified errors" in my patch for AVRO-560.
Perhaps "declared" can be used?

Thanks,
Jeff

> 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
>            Priority: Blocker
>             Fix For: 1.4.0
>
>         Attachments: AVRO-447.patch
>
>
> 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.


Mime
View raw message