Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AVRO-2022: Allow schema as identifier in IDL (1.7) #211

Closed
wants to merge 1 commit into from
Closed

AVRO-2022: Allow schema as identifier in IDL (1.7) #211

wants to merge 1 commit into from

Conversation

erikvanoosten
Copy link

@erikvanoosten erikvanoosten commented Apr 11, 2017

Currently the word schema is not allowed as identifier in IDL, even not when it is escaped in backticks. This patch fixed that for the 1.7 branch.

@erikvanoosten erikvanoosten changed the title Allow schema as identifier (1.7) Allow schema as identifier in IDL (1.7) Apr 11, 2017
@erikvanoosten erikvanoosten changed the title Allow schema as identifier in IDL (1.7) AVRO-2022: Allow schema as identifier in IDL (1.7) Apr 11, 2017
@erikvanoosten
Copy link
Author

After working with this change for some time we decided to abandon this idea and change the schema after all. The problem is that much code generation tools assume they can create method Schema getSchema(). Unfortunately this collides with the value we want it to return.

SingingBush pushed a commit to SingingBush/avro that referenced this pull request Jun 29, 2023
Add 'additionalVelocityTool' capability.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant