[
https://issues.apache.org/jira/browse/FLINK-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729909#comment-14729909
]
ASF GitHub Bot commented on FLINK-1674:
---------------------------------------
GitHub user vimalk78 opened a pull request:
https://github.com/apache/flink/pull/1091
[FLINK-1674] Add test with nested avro type
Modified User definition in user.avsc to include a nested definition.
Modified the corresponding test cases to reflect the changed User
definition
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vimalk78/flink avro-1674
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1091.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 #1091
----
commit f5b92c82cad308371cca85fd8497b689729b4e9d
Author: Vimal <vima...@gmail.com>
Date: 2015-09-03T22:13:35Z
Modified test cases for nested avro type
----
> Add test with nested avro type
> ------------------------------
>
> Key: FLINK-1674
> URL: https://issues.apache.org/jira/browse/FLINK-1674
> Project: Flink
> Issue Type: Improvement
> Components: Java API
> Affects Versions: 0.9
> Reporter: Robert Metzger
> Labels: starter
>
> Right now our tests with avro only include flat types.
> I recently discovered a bug caused by a nested avro types.
> Since avro pojos are handled a bit differently than regular POJOs AND because
> we have users using Avro in production, we should make sure it is always
> working.
> (Thats the reason why I mad this a "Major" issue).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
