[jira] [Updated] (AVRO-1912) C++ Resolving Decoding doesn't work if element removed from record in array.

[ https://issues.apache.org/jira/browse/AVRO-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thiruvalluvan M. G. updated AVRO-1912: -- Component/s: c++ > C++ Resolving Decoding doesn't work if element removed from record in

[jira] [Commented] (AVRO-1912) C++ Resolving Decoding doesn't work if element removed from record in array.

[ https://issues.apache.org/jira/browse/AVRO-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15696603#comment-15696603 ] John McClean commented on AVRO-1912: Can this be merged to trunk? > C++ Resolving Decoding doesn't

Checking if schema evolution will work.

Hi, I have been looking but I have not been able to find a tool that simply tells me if a schema and evolve into another schema. I want to create a test in my application that simply checks (unit test) if the current schema can be used in conjuction with an older schema or if we will have

[jira] [Commented] (AVRO-1961) [JAVA] Generate getters that return an Optional

[ https://issues.apache.org/jira/browse/AVRO-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695411#comment-15695411 ] Niels Basjes commented on AVRO-1961: Just now (as an experiment) I added the option to the code

Re: [jira] [Commented] (AVRO-1961) [JAVA] Generate getters that return an Optional

There are many arguments for/against Optionals on the web, but the consensus seem to be that Optionals are best used as method return types, not as method parameters. Therefore, I think the setters should still use the plain objects, as there are anyway no practical way to enforce non-nullity