[
https://issues.apache.org/jira/browse/AVRO-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853534#action_12853534
]
Jeff Hodges commented on AVRO-447:
----------------------------------
For those interested, the current ruby implementation only has the string as a
valid type if there is no value given for the errors key. That is:
{code}
writers_schema = remote_message_schema.errors || SYSTEM_ERROR_SCHEMA
readers_schema = local_message_schema.errors || SYSTEM_ERROR_SCHEMA
{code}
I will be changing this to be inclusive in a new ticket.
> 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.
