You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/10/10 11:06:20 UTC
[jira] [Commented] (AVRO-1932) Allow setting the SchemaStore on
generated classes
[ https://issues.apache.org/jira/browse/AVRO-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15561990#comment-15561990 ]
ASF GitHub Bot commented on AVRO-1932:
--------------------------------------
GitHub user nielsbasjes opened a pull request:
https://github.com/apache/avro/pull/141
AVRO-1932: Java: Allow setting the SchemaStore on generated classes.
This change is needed to allow setting a different SchemaStore in the IDL generated classes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nielsbasjes/avro AVRO-1932
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/avro/pull/141.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #141
----
commit eb2bdbe10bb75e842deaa1d04e35c8bfb19e3069
Author: Niels Basjes <nb...@bol.com>
Date: 2016-10-10T11:04:06Z
AVRO-1932: Java: Allow setting the SchemaStore on generated classes.
----
> Allow setting the SchemaStore on generated classes
> --------------------------------------------------
>
> Key: AVRO-1932
> URL: https://issues.apache.org/jira/browse/AVRO-1932
> Project: Avro
> Issue Type: Improvement
> Reporter: Niels Basjes
> Assignee: Niels Basjes
>
> With AVRO-1704 we can now create a binary form of a record that can be put in Kafka. I tried to use this new feature in my own application and soon noticed that if a class is generated from the IDL you cannot set/change the schema resolution system.
> Goal:
> - Allow setting the schema resolution in a generated class
> - Allow simply adding a single schema in a generated class
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)