Alfonso Nishikawa created AVRO-1613:
---
Summary: Support for non-standard JSON when reading schemas
Key: AVRO-1613
URL: https://issues.apache.org/jira/browse/AVRO-1613
Project: Avro
Issue
[
https://issues.apache.org/jira/browse/AVRO-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alfonso Nishikawa updated AVRO-1613:
Description:
It would be good to:
* Allow unquoted field names
* Allow single quotes
* Allow
[
https://issues.apache.org/jira/browse/AVRO-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alfonso Nishikawa updated AVRO-1613:
Description:
It would be good to:
* Allow unquoted field names
* Allow single quotes
* Allow
[
https://issues.apache.org/jira/browse/AVRO-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14226260#comment-14226260
]
Michael Pershyn commented on AVRO-1564:
---
I am using patched version already 4 month
Hi,
I have a Java project where I'm using Avro as the serialization technology.
I have a deep nested structure and many fields are optional.
Because of the 'random' nature of my application I want to be able to
simply 'set' a value in that tree easily.
So I want to have a setter in my class
Oops,
That should be
public Foo getFoo()
and
public Foo getAlwaysFoo()
ofcourse
On Wed, Nov 26, 2014 at 6:28 PM, Niels Basjes ni...@basjes.nl wrote:
Hi,
I have a Java project where I'm using Avro as the serialization technology.
I have a deep nested structure and many fields are
[
https://issues.apache.org/jira/browse/AVRO-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14226674#comment-14226674
]
ASF subversion and git services commented on AVRO-1564:
---
Commit
[
https://issues.apache.org/jira/browse/AVRO-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated AVRO-1564:
---
Resolution: Fixed
Fix Version/s: 1.8.0
Assignee: Michael Pershyn (was: Doug Cutting)
[
https://issues.apache.org/jira/browse/AVRO-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14226678#comment-14226678
]
Doug Cutting commented on AVRO-1611:
Sounds reasonable. Can you please provide unit
[
https://issues.apache.org/jira/browse/AVRO-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated AVRO-1407:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
I committed this. Thanks, Gareth!
[
https://issues.apache.org/jira/browse/AVRO-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14226684#comment-14226684
]
ASF subversion and git services commented on AVRO-1407:
---
Commit
[
https://issues.apache.org/jira/browse/AVRO-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14226692#comment-14226692
]
ASF subversion and git services commented on AVRO-1604:
---
Commit
[
https://issues.apache.org/jira/browse/AVRO-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting resolved AVRO-1604.
Resolution: Fixed
I committed this. Thanks, Ryan!
ReflectData.AllowNull fails to generate schemas
[
https://issues.apache.org/jira/browse/AVRO-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14226698#comment-14226698
]
Hudson commented on AVRO-1564:
--
SUCCESS: Integrated in AvroJava #501 (See
[
https://issues.apache.org/jira/browse/AVRO-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14226701#comment-14226701
]
Ryan Blue commented on AVRO-1608:
-
The current patch looks fine to me, except for making
[
https://issues.apache.org/jira/browse/AVRO-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14226728#comment-14226728
]
Doug Cutting commented on AVRO-1608:
I agree that we should avoid making Name public if
What does an example schema look like in this case?
Shouldn't the extant builders give you this behavior if you've made the
default for the optional fields non-null?
--
Sean
On Nov 26, 2014 11:34 AM, Niels Basjes ni...@basjes.nl wrote:
Oops,
That should be
public Foo getFoo()
and
[
https://issues.apache.org/jira/browse/AVRO-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14226804#comment-14226804
]
Hudson commented on AVRO-1407:
--
SUCCESS: Integrated in AvroJava #502 (See
[
https://issues.apache.org/jira/browse/AVRO-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14226803#comment-14226803
]
Hudson commented on AVRO-1604:
--
SUCCESS: Integrated in AvroJava #502 (See
Yes, the builders would do that for mandatory (= non-null) fields.
The schemas I'm using have a lot of this pattern
record Thing {
union { null, Foo } optionalFoo;
union { null, Bar } optionalBar;
}
record Bar {
union { null, Blabla } optionalBlabla;
}
etc.
So creating a record with a
I usually use Schemas directly rather than IDL, so apologies if some of
this doesn't map directly.
In a Schema with an optional field, or really any union, the default value
has to be of the first mentioned type. For optional fields this usually
means making the first value the null type and the
You can instead list the non-null type first and give a default appropriate
for the field type. I'd be surprised if the IDL couldn't also do this.
I'm not sure that works for avro where null is used for an optional field.
2014-11-26 23:28 GMT+01:00 Sean Busbey bus...@cloudera.com:
I usually
On Wed, Nov 26, 2014 at 2:33 PM, svante karlsson s...@csi.se wrote:
I'm not sure that works for avro where null is used for an optional field.
It should work. If it doesn't, it's a bug. For example:
record Foo {
union {string, null} name = default;
}
record Bar {
union {Foo, null} foo =
23 matches
Mail list logo
