[
https://issues.apache.org/jira/browse/AVRO-3436?focusedWorklogId=738406&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-738406
]
ASF GitHub Bot logged work on AVRO-3436:
----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Mar/22 22:09
Start Date: 08/Mar/22 22:09
Worklog Time Spent: 10m
Work Description: opwvhk opened a new pull request #1587:
URL: https://github.com/apache/avro/pull/1587
Make sure you have checked _all_ steps below.
### Jira
- [X] My PR addresses the following [Avro
Jira](https://issues.apache.org/jira/browse/AVRO/) issues and references them
in the PR title. For example, "AVRO-1234: My Avro PR"
- https://issues.apache.org/jira/browse/AVRO-3436
- ~In case you are adding a dependency, check if the license complies with
the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).~
### Tests
- [X] My PR ~adds the following unit tests __OR__~ does not need testing for
this extremely good reason:
It's a documentation update. Human review is important.
### Commits
- [X] My commits all reference Jira issues in their subject lines. In
addition, my commits follow the guidelines from "[How to write a good git
commit message](https://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [X] In case of new functionality, my PR adds documentation that describes
how to use it.
- All the public functions and the classes in the PR contain Javadoc that
explain what it does
--
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: 738406)
Remaining Estimate: 0h
Time Spent: 10m
> [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
> Reporter: Ryan Skraba
> Priority: Major
> Fix For: 1.11.1
>
> Time Spent: 10m
> 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.1#820001)
