avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-2034) Nested schema types with unexpected fields causes json parse failure
Date Thu, 11 May 2017 18:30:04 GMT

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

ASF GitHub Bot commented on AVRO-2034:
--------------------------------------

GitHub user tnine opened a pull request:

    https://github.com/apache/avro/pull/224

    AVRO-2034 Nested schema types with unexpected fields causes json parse failure

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sandwich-expert/avro nested-field-fix

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/avro/pull/224.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 #224
    
----
commit b57d9609f41ae4a7255698fda20129383274d3ec
Author: Todd Nine <todd@thelastpickle.com>
Date:   2017-05-11T18:24:15Z

    AVRO-2034 Created test to prove issue

----


> Nested schema types with unexpected fields causes json parse failure
> --------------------------------------------------------------------
>
>                 Key: AVRO-2034
>                 URL: https://issues.apache.org/jira/browse/AVRO-2034
>             Project: Avro
>          Issue Type: Bug
>          Components: java
>    Affects Versions: 1.8.1
>            Reporter: Todd Nine
>
> When parsing a nested type with an unexpected field using the JSON parser, this results
in an error.  To reproduce, see the class {{TestNestedRecords}} in the referenced PR.
> Note that this only occurs when the following pattern exists in the schema.
> # regular field
> # nested type with additional field
> # any subsequent nested type.  Using a regular field following the nested type does not
appear to reproduce the problem.
> I'm currently working on a fix. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message