[
https://issues.apache.org/jira/browse/AVRO-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277699#comment-14277699
]
ASF subversion and git services commented on AVRO-1628:
-------------------------------------------------------
Commit 1651831 from [~cutting] in branch 'avro/trunk'
[ https://svn.apache.org/r1651831 ]
AVRO-1628. Java: Add Schema#createUnion(Schema ...) convenience method.
Contributed by Clément Mahtieu.
> Add Schema.createUnion(Schema... type)
> --------------------------------------
>
> Key: AVRO-1628
> URL: https://issues.apache.org/jira/browse/AVRO-1628
> Project: Avro
> Issue Type: Improvement
> Components: java
> Reporter: Clément MAHTIEU
> Priority: Trivial
> Attachments: AVRO-1628.patch, AVRO-1628.patch
>
>
> Quite often, when I declare mapreduce jobs I have to create the union of two
> or three schemas. For example:
> {code}
> AvroJob.setMapOutputKeySchema(job,
> Schema.createUnion(Arrays.asList(Foo.SCHEMA$, Bar.SCHEMA$))
> {code}
> Having Schema.createUnion only accept a List hurts readability and force
> users to write boilerplate code for such trivial, but I believe common, use
> cases. It would be create to add {{Schema.createUnion(Schema... type)}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
