> I don't think we can change the behavior of the "default" key. Otherwise,
> older
readers would use the wrong value.
This is true, but the "human-readable default" feature is inherently
incompatible with older readers. My hope was that giving an invalid type
for the default would cause an error
[
https://issues.apache.org/jira/browse/AVRO-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated AVRO-1827:
---
Assignee: Karel Fuka
Status: Patch Available (was: Open)
> Handling correctly optional fields wh
I don't think we can change the behavior of the "default" key. Otherwise,
older readers would use the wrong value.
I suggest that we add an optional key, like "default-as-string", that is
used to fill in a missing "default" key if there is a reasonable
conversion. On write, the write schema would
[
https://issues.apache.org/jira/browse/AVRO-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209356#comment-16209356
]
Karel Fuka commented on AVRO-1827:
--
Hello,
we would like to check if there is any plan to
Hi Suraj,
Though I'm not a committer, I'd be happy to help you with the release
(verification, or anything else you need help with, and I can also do it)!
By the way, is there a wiki about the steps required for an Avro release?
Thanks,
Nandor
On Fri, Oct 13, 2017 at 3:00 AM, Suraj Acharya wrot
