[
https://issues.apache.org/jira/browse/AVRO-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17776336#comment-17776336
]
ASF subversion and git services commented on AVRO-3833:
-------------------------------------------------------
Commit 90710b71802168847defb4d1a82e1eab221c04d2 in avro's branch
refs/heads/dependabot/maven/lang/java/org.apache.thrift-libthrift-0.19.0 from
Oscar Westra van Holthe - Kind
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=90710b718 ]
AVRO-3833: [Spec] Clarify usage of names and aliases (#2448)
Also includes a section explaining schema fixes
> Spec: clarify usage names and aliases
> -------------------------------------
>
> Key: AVRO-3833
> URL: https://issues.apache.org/jira/browse/AVRO-3833
> Project: Apache Avro
> Issue Type: Improvement
> Components: spec
> Affects Versions: 1.11.2
> Reporter: Oscar Westra van Holthe - Kind
> Assignee: Oscar Westra van Holthe - Kind
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.12.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The specification currently says nothing about the uniqueness of names. At
> most it says something about equality of names, assuming readers understand
> that a name must uniquely identify a type.
> I suggest making the rules for uniqueness explicit.
> This would mean:
> # Full names and aliases of types (including namespace) must be unique
> # For each enum type, symbol names must be unique
> # For each record/error type, field names and aliases must be unique
> Also, I propose to add that aliases should be, but to not need be, valid
> names. Using an invalid name as alias allows schema evolution to correct
> illegal names used in the past.
> This allows us to explicitly describe how to fix invalid, but previously
> accepted, schemata.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
