You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Ryan Skraba (Jira)" <ji...@apache.org> on 2022/06/21 18:00:00 UTC
[jira] [Resolved] (AVRO-3436) [Spec] Clarify which names are allowed to be qualified with namespaces
[ https://issues.apache.org/jira/browse/AVRO-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Skraba resolved AVRO-3436.
-------------------------------
Resolution: Fixed
Cherry-picked to [branch-1.11|https://github.com/apache/avro/commit/913bf36d81984d9bc44d873cc8d1655cda2347e2]. Thanks!
> [Spec] Clarify which names are allowed to be qualified with namespaces
> ----------------------------------------------------------------------
>
> Key: AVRO-3436
> URL: https://issues.apache.org/jira/browse/AVRO-3436
> Project: Apache Avro
> Issue Type: Improvement
> Components: spec
> Reporter: Ryan Skraba
> Assignee: Oscar Westra van Holthe - Kind
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The doc specifies that
> {quote}the name portion of a fullname, record field names, and enum symbols must match _[an alphanumeric regex without periods]_
> {quote}
> [https://github.com/apache/avro/blob/release-1.11.0/doc/src/content/xdocs/spec.xml#L277-L282]
> At first glance this could be read to imply that record field names and enum symbols have a "name portion" or that they could be fully qualified with a namespace, which is not the case.
> It would be simple and clear to specify that they are unqualified names at the definition of a field or enum symbol, as well as word this differently.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)