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

ASF GitHub Bot commented on AVRO-1902:
--------------------------------------

walshb edited a comment on issue #158: AVRO-1902: C: Namespace "" means space = 
NULL.
URL: https://github.com/apache/avro/pull/158#issuecomment-440397330
 
 
   I have no idea. All the people with commit access in Avro land don't seem to 
understand C. I have 4 patches which they just ignore. I'm no longer using Avro 
so I've just given up.
   
   If you are interested in getting this fixed, I suggest finding the last 
person who committed a significant change to the C code (ie. someone with 
commit access, who cares about C), and contacting them directly.
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> C: namespace "" should mean namespace = NULL
> --------------------------------------------
>
>                 Key: AVRO-1902
>                 URL: https://issues.apache.org/jira/browse/AVRO-1902
>             Project: Apache Avro
>          Issue Type: Bug
>          Components: c
>            Reporter: Ben Walsh
>            Priority: Minor
>         Attachments: AVRO-1902.patch
>
>
> Similar to AVRO-1295 but for the C library. Namespace "" should be the NULL 
> namespace when the schema is parsed. For example this breaks:
> ```
> {"type": "record", "name": "R", "fields": [
>   {"name": "s", "type": {"type": "record", "namespace": "x", "name": "Y", 
> "fields": [
>     {"name": "e", "type": {"type": "record", "namespace": "", "name": "Z", 
> "fields": [
>       {"name": "f", "type": "Z"}
>     ]}}
>   ]}},
>   {"name": "t", "type": "Z"}
> ]}
> ```



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to