[jira] [Commented] (AVRO-2923) GenericDatum::logicalType() API should return the logical type corresponing to one of the constituent types of the union

2021-03-11 Thread Yang Xu (Jira)
[ https://issues.apache.org/jira/browse/AVRO-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17299980#comment-17299980 ] Yang Xu commented on AVRO-2923: --- Can we get this one fixed, it should be a trivial fix and I have a PR ready

[jira] [Updated] (AVRO-2923) GenericDatum::logicalType() API should return the logical type corresponing to one of the constituent types of the union

2021-03-11 Thread Yang Xu (Jira)
[ https://issues.apache.org/jira/browse/AVRO-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Xu updated AVRO-2923: -- Priority: Major (was: Minor) > GenericDatum::logicalType() API should return the logical type corresponing >

Re: [VOTE] Release Apache Avro 1.10.2 RC2

2021-03-11 Thread Ismaël Mejía
+1 (binding) Validated signatures and hashes Built distribution from source for Java Tried with downstream projects (Spark/Parquet) with success On Thu, Mar 11, 2021 at 7:09 PM Daniel Kulp wrote: > > > +1 > > Most of my testing was with RC1, but some followup with RC2 doesn’t reveal > anything

Re: What are the rules when encoding a union of records and/or maps?

2021-03-11 Thread Spencer Nelson
It turns out that the Python implementation takes the last path that matches. Agreed that it's deterministic within a language, but it might round-trip inconsistently. For example, suppose Java takes the first path that matches, and Python takes the last path that matches. Then, if I 1.

Do fully-qualified names imply creation of a namespace?

2021-03-11 Thread Spencer Nelson
When a named type definition has no dots in its 'name' field, and has no 'namespace' field, then the namespace is "taken from the most tightly enclosing schema or protocol." For example: { "type": "record", "name": "X", "namespace": "org.foo", "fields": [ {"type": {"type": "fixed",

Re: [VOTE] Release Apache Avro 1.10.2 RC2

2021-03-11 Thread Daniel Kulp
+1 Most of my testing was with RC1, but some followup with RC2 doesn’t reveal anything problematic. Dan > On Mar 9, 2021, at 12:55 PM, Ryan Skraba wrote: > > Hi everyone, > > I'd like to propose the following RC2 to be released as the official Apache > Avro 1.10.2 release. > > There

[jira] [Created] (AVRO-3077) Ability of select string deserializing by configuration

2021-03-11 Thread Emilio Jose Mena Cebrian (Jira)
Emilio Jose Mena Cebrian created AVRO-3077: -- Summary: Ability of select string deserializing by configuration Key: AVRO-3077 URL: https://issues.apache.org/jira/browse/AVRO-3077 Project:

[jira] [Commented] (AVRO-2838) Schema in generated Java class is different than the original one

2021-03-11 Thread Emilio Jose Mena Cebrian (Jira)
[ https://issues.apache.org/jira/browse/AVRO-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17299458#comment-17299458 ] Emilio Jose Mena Cebrian commented on AVRO-2838: +1 If you are mixing technologies

[jira] [Created] (AVRO-3076) Wrong javadoc documentation for useCustomCoders

2021-03-11 Thread Emilio Jose Mena Cebrian (Jira)
Emilio Jose Mena Cebrian created AVRO-3076: -- Summary: Wrong javadoc documentation for useCustomCoders Key: AVRO-3076 URL: https://issues.apache.org/jira/browse/AVRO-3076 Project: Apache Avro