You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Todd Nine (JIRA)" <ji...@apache.org> on 2017/05/11 18:31:04 UTC
[jira] [Updated] (AVRO-2034) Nested schema types with unexpected
fields causes json parse failure
[ https://issues.apache.org/jira/browse/AVRO-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Nine updated AVRO-2034:
----------------------------
Description:
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.
https://github.com/apache/avro/pull/224
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.
was:
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.
> 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.
> https://github.com/apache/avro/pull/224
> 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)