[
https://issues.apache.org/jira/browse/AVRO-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031431#comment-17031431
]
ASF subversion and git services commented on AVRO-1646:
-------------------------------------------------------
Commit 335acc5770f7ad6bd6fdf4caa305373a79912d70 in avro's branch
refs/heads/master from Ben Plommer
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=335acc5 ]
AVRO-1646: Print/parse consistency for nested null namespace (#724)
Fixes print-parse consistency for named types with null namespace,
enclosed in named fields with null namespace, which are themselves
enclosed in named fields with non-null namespace.
Currently, if a type specifies the null namespace, this overrides the
enclosing non-null namespace for the purpose of naming that type, but
not for the purposes of determining the closest enclosing namespace for
more deeply nested types. This fixes that by removing special-casing of
null when setting the default namespace for recursively parsed schemas.
Adapted from the patch that was submitted with the AVRO-1646 ticket.
> null namespace within non-null is not print/parse consistent with deeply
> nested records
> ---------------------------------------------------------------------------------------
>
> Key: AVRO-1646
> URL: https://issues.apache.org/jira/browse/AVRO-1646
> Project: Apache Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.7.7
> Reporter: Nikita Makeev
> Priority: Major
> Fix For: 1.10.0
>
> Attachments: AVRO-1646.patch
>
>
> This was partly addressed in AVRO-1295. If a record with a null namespace and
> containing other record is nested within a record with a non-null namespace
> then, when the outer schema is printed and re-parsed, the most inner schema's
> namespace becomes the outer, rather than null as it should be.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
