[
https://issues.apache.org/jira/browse/AVRO-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903540#action_12903540
]
Doug Cutting commented on AVRO-639:
-----------------------------------
In retrospect, I agree. The "namespace" keyword should perhaps never have been
introduced, and fully-qualified names should instead be used everywhere. But
that would be an incompatible change, rendering some existing data unreadable.
If you'd like to propose that, along with a migration plan, please file a
separate issue.
Short-term, I'd like to roll a release candidate today that passes data interop
tests. The bug in Ruby (AVRO-635) is not a regression, so needn't block the
release. I'd certainly rather fix that bug than mask it here, and I tried, but
I couldn't bluff my way far enough with Ruby to do it. (Whereas I could bluff
my way far-enough with Python!) Perhaps Jeff will come through with a patch
for AVRO-635 soon. But, if that doesn't happen, fixing this is an expedient
way to move forward with a 1.4.0 release.
> python should print short name of records
> ------------------------------------------
>
> Key: AVRO-639
> URL: https://issues.apache.org/jira/browse/AVRO-639
> Project: Avro
> Issue Type: Improvement
> Components: python
> Reporter: Doug Cutting
> Fix For: 1.4.0
>
> Attachments: AVRO-639.patch
>
>
> When printing a reference to a named schema, the non-full-name is preferred
> when the type's namespace is the same as its enclosing schema.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
