[
https://issues.apache.org/jira/browse/AVRO-3275?focusedWorklogId=737646&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-737646
]
ASF GitHub Bot logged work on AVRO-3275:
----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Mar/22 17:20
Start Date: 07/Mar/22 17:20
Worklog Time Spent: 10m
Work Description: RyanSkraba commented on pull request #1439:
URL: https://github.com/apache/avro/pull/1439#issuecomment-1060931442
Oh, I also agree with Oscar's interpretation : named types have namespaces
because they are reused (as type references), while fields (and enum symbols)
can only be used in the context of their enclosing record (or enum).
If you have a use case for fields with a namespace, I'd be interested in
hearing it. Maybe we could suggest an alternative? But `[email protected]`
or a new JIRA might get more visibility!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 737646)
Time Spent: 2h 20m (was: 2h 10m)
> Spec on naming can be better
> ----------------------------
>
> Key: AVRO-3275
> URL: https://issues.apache.org/jira/browse/AVRO-3275
> Project: Apache Avro
> Issue Type: Improvement
> Components: spec
> Affects Versions: 1.11.0, 1.10.2
> Reporter: Oscar Westra van Holthe - Kind
> Assignee: Oscar Westra van Holthe - Kind
> Priority: Trivial
> Labels: pull-request-available
> Fix For: 1.11.1
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Because of a question on the mailing list, it became clear that the spec on
> naming can be improved.
> Specifically, the spec doesn't explicitly repeat in all cases on naming how
> the fullname is created.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
