[
https://issues.apache.org/jira/browse/AVRO-3305?focusedWorklogId=709190&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-709190
]
ASF GitHub Bot logged work on AVRO-3305:
----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jan/22 17:14
Start Date: 14/Jan/22 17:14
Worklog Time Spent: 10m
Work Description: mluiten commented on pull request #1457:
URL: https://github.com/apache/avro/pull/1457#issuecomment-1013307316
Hopefully this can make the next release đ 1.11.0 breaks our package names
which results in mismatches; AVRO registry reports the packages as
`com.blabla.record` while it can only find `com.blabla.record$` at runtime,
crashing our application.
--
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: 709190)
Time Spent: 20m (was: 10m)
> Avro Compiler(s) should only mangle contextual reserved keyword when used in
> reserved context
> ---------------------------------------------------------------------------------------------
>
> Key: AVRO-3305
> URL: https://issues.apache.org/jira/browse/AVRO-3305
> Project: Apache Avro
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.11.0
> Reporter: Kyle Carter
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In AVRO-3116 it was correctly called out that new reserved keywords had been
> added to the Java language in recent versions that could lead to uncompilable
> Avro schemas in Java. While the fix developed for that issue does resolve the
> issue it treats all keywords identically. Some of the keywords (record,
> yield, var) targeted by that change are only keywords when used in particular
> contexts, specifically as a type identifier. Nevertheless, the Avro compiler
> code treats all keywords the same and will mangle them wherever they show up
> (for example in a package name) even if it would have been valid without
> mangling (ex: com.example.record). This can be surprising and result in
> unnecessary code updates.Â
> I suggest that these contextual keywords only be mangled when used in the
> context they are reserved.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
