avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1628) Add Schema.createUnion(Schema... type)
Date Wed, 14 Jan 2015 21:38:34 GMT

    [ https://issues.apache.org/jira/browse/AVRO-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277731#comment-14277731
] 

Hudson commented on AVRO-1628:
------------------------------

SUCCESS: Integrated in AvroJava #511 (See [https://builds.apache.org/job/AvroJava/511/])
AVRO-1628. Java: Add Schema#createUnion(Schema ...) convenience method.  Contributed by Clément
Mahtieu. (cutting: rev 1651831)
* /avro/trunk/CHANGES.txt
* /avro/trunk/lang/java/avro/src/main/java/org/apache/avro/Schema.java
* /avro/trunk/lang/java/avro/src/test/java/org/apache/avro/TestSchema.java


> 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
>            Assignee: Clément MAHTIEU
>            Priority: Trivial
>             Fix For: 1.8.0
>
>         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)

Mime
View raw message