You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2009/11/15 22:41:48 UTC

[jira] Created: (AVRO-198) "protocol declaration" of spec lists a "name" attribute rather than "protocol"

"protocol declaration" of spec lists a "name" attribute rather than "protocol"
------------------------------------------------------------------------------

                 Key: AVRO-198
                 URL: https://issues.apache.org/jira/browse/AVRO-198
             Project: Avro
          Issue Type: Bug
          Components: spec
    Affects Versions: 1.2.0
            Reporter: Patrick Hunt


The protocol declaration section of the spec has

----
A protocol is a JSON object with the following attributes:

    * name, string, to distinguish it from other protocols;
----

while the subsequent example lists "protocol" (and the code afaict).

also the spec makes no mention of which attributes are required and which are optional (and what the defaults
are if not specified).

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


[jira] Commented: (AVRO-198) "protocol declaration" of spec lists a "name" attribute rather than "protocol"

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AVRO-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778480#action_12778480 ] 

Doug Cutting commented on AVRO-198:
-----------------------------------

Good catch.

Java's protocol parser currently only requires "name", although I suspect that we have not tested protocols that lack namespaces, types and messages, so these may be required by other parts.

In general we've permitted the lack of a top-level namespace.  Should we continue to do so?

> "protocol declaration" of spec lists a "name" attribute rather than "protocol"
> ------------------------------------------------------------------------------
>
>                 Key: AVRO-198
>                 URL: https://issues.apache.org/jira/browse/AVRO-198
>             Project: Avro
>          Issue Type: Bug
>          Components: spec
>    Affects Versions: 1.2.0
>            Reporter: Patrick Hunt
>
> The protocol declaration section of the spec has
> ----
> A protocol is a JSON object with the following attributes:
>     * name, string, to distinguish it from other protocols;
> ----
> while the subsequent example lists "protocol" (and the code afaict).
> also the spec makes no mention of which attributes are required and which are optional (and what the defaults
> are if not specified).

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


[jira] Resolved: (AVRO-198) "protocol declaration" of spec lists a "name" attribute rather than "protocol"

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AVRO-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Cutting resolved AVRO-198.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3.0

I just fixed this.

> "protocol declaration" of spec lists a "name" attribute rather than "protocol"
> ------------------------------------------------------------------------------
>
>                 Key: AVRO-198
>                 URL: https://issues.apache.org/jira/browse/AVRO-198
>             Project: Avro
>          Issue Type: Bug
>          Components: spec
>    Affects Versions: 1.2.0
>            Reporter: Patrick Hunt
>             Fix For: 1.3.0
>
>
> The protocol declaration section of the spec has
> ----
> A protocol is a JSON object with the following attributes:
>     * name, string, to distinguish it from other protocols;
> ----
> while the subsequent example lists "protocol" (and the code afaict).
> also the spec makes no mention of which attributes are required and which are optional (and what the defaults
> are if not specified).

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