Avro schema resolution

Hi all, While I was trying to understand how schema evolution works in Avro, I noticed that the schema resolution logic ( https://avro.apache.org/docs/1.8.1/spec.html#Schema+Resolution) is implemented in two different places in Avro: in ResolvingGrammarGenerator and in SchemaCompatibility. Could

Re: Avro schema resolution

reading & writing of data, simplifying maintenance. > > Doug > > On Wed, Aug 23, 2017 at 6:01 AM, Nandor Kollar <nkol...@cloudera.com> > wrote: > > > Hi all, > > > > While I was trying to understand how schema evolution works in Avro, I > > noticed

Re: [jira] [Commented] (AVRO-2072) ResolvingGrammarGenerator doesn't implement schema resolution correctly for unions

loat. But YMMV, > > Thanks for your time, > /Anders Sundelin > > > Original Message > Subject: [jira] [Commented] (AVRO-2072) ResolvingGrammarGenerator doesn't > implement schema resolution correctly for unions > From: "Nandor Kollar (J

Re: 1.7.8 Release of Apache Avro

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

Re: Licensing problem (LGPL in codebase!!)

I've one question regarding this: why do we execute Rat plugin *only* in rat profile, is there any specific reason? Should include this into test phase, so Maven test would fail, thus we can avoid similar problems? On Wed, Dec 13, 2017 at 2:14 PM, Niels Basjes wrote: > Hi all,

Re: [ANNOUNCE] new committer Nándor Kollár

Thanks for all of you! On Mon, Nov 6, 2017 at 7:11 PM, Ryan Blue wrote: > Congratulations, Nandor! > > On Mon, Nov 6, 2017 at 10:09 AM, Niels Basjes wrote: > > > Welcome ! > > > > On Nov 6, 2017 17:04, "Sean Busbey" wrote: > > > > >

Re: Giving credit for contributions through Github Pull Requests

+1 for both, especially for removing CHANGES.txt. On Thu, May 3, 2018 at 11:18 PM, Doug Cutting wrote: > Maybe we should loosen the permissions on Avro's Jira so that any user can > assign an issue? That would make things a bit simpler. I doubt we'd see > much if any abuse.

Re: [jira] [Commented] (AVRO-2164) Make Decimal a first class type.

ndy Coates wrote: > Hi [~nkollar], > > I'd say that's a rule for decimal comparison, not evolution. > > On Fri, 20 Jul 2018 at 13:10, Nandor Kollar (JIRA) > wrote: > > > > > [ > > https://issues.apache.org/jira/browse/AVRO-2164?page= > com.atlassian.j

Re: Feature freeze Apache Avro 1.9

I totally support making JSR310 as the default instead of Joda time. Should we consider removing the JSR310 from the class names, for example rename Jsr310TimeConversions to TimeConversions and the existing TimeConversions to JodaTimeConversions, and deprecate the latter? On Thu, Mar 28, 2019 at

[DISCUSS] Support additional timestamp semantic

Hi all, There is an ongoing effort to harmonize timestamp types for various popular SQL engines for Hadoop (see details here ). As part of this effort, on disk file formats should be able to support all of

Re: [VOTE] Release Apache Avro 1.9.0 RC4

nal testing against Apache Spark > (similar to > > > > Nandor :-) and Apache Flink and did not find any blocking issues. > There > > > are > > > > some incompatibilities, but most of them are; revoking Jackson from > the > > > > public API and

Re: [ANNOUNCE] Please welcome Fokko Driesprong to the Apache Avro PMC

Congratulations Fokko, well-earned! On Tue, May 14, 2019 at 10:15 AM Niels Basjes wrote: > Welcome aboard! > > On Tue, May 14, 2019, 09:28 Sean Busbey wrote: > > > Hi folks! > > > > On behalf of the Apache Avro PMC I am pleased to announce that Fokko > > Driesprong has accepted our invitation

Re: [Avro] How to represent naive timestamps?

Hi Tim, Yes, there is already an email thread and an open Jira (AVRO-2328) about this topic. Feel free to comment on the design doc or Jira if you have any thoughts to share. Thanks, Nandor On Wed, May 8, 2019 at 11:30 PM Tim Swast wrote: > Oops, just saw >

Re: [VOTE] Release Apache Avro 1.9.0 RC4

+1 (non-binding) * verified signatures and checksums * ran unit tests, passed * did a quick sanity test against Spark master: upgraded Spark Avro dependency to this release candidate, ran spark-avro tests, all passed (for the record, two minor Maven changes are required due to removal of Hadoop 1

Re: [VOTE] Release Apache Avro 1.9.0 RC3

Hi Katrin, It appears to me, that these methods didn't exist in previous Avro versions, they were added in https://github.com/apache/avro/pull/350 and were renamed and reduced their visibility in https://github.com/apache/avro/pull/350/commits/d320b6b536c49b485be45286dbdb73226eef4b35. Actually it

Re: [VOTE] Release Apache Avro 1.9.0 RC3

ields": [ > { > "name": "someField", > "type": "int" > } > ] > } > }] > } > > And an example from the generated code: > > @Override protected void customEncode(or

Re: [VOTE] Release Apache Avro 1.9.0 RC3

n't have a Jira account, should I sign up for one? > > On 2019-05-03, 12:09, "Nandor Kollar" > wrote: > > Ah, okay, I see. Well, in this case it is a release blocker then, > since it > is indeed a regression. If you've an account to Apache Jira, plea

Re: [DISCUSS] Support additional timestamp semantic

e/time, this can > > eventually be unified in the language-specific API tools without breaking > > the schema specification. > > > > TL;DR: I read it, I appreciated it, I agree with your conclusions. > > > > Thanks again for the thorough and articulate work! Ryan

Re: [ANNOUNCE] Please welcome Brian Lachniet to the Apache Avro PMC

Congrats Brian! On Sat, Aug 24, 2019 at 7:51 PM Driesprong, Fokko wrote: > Congrats Brian! Well deserved! > > Cheers, Fokko > > Op za 24 aug. 2019 om 18:57 schreef Niels Basjes > > > Welcome aboard > > > > On Sat, Aug 24, 2019, 17:40 Sean Busbey wrote: > > > > > Hi folks! > > > > > > On

Re: [VOTE] Release Apache Avro RC3

Brian, Updated Jira, and also added you to the Jira admins. Regards, Nandor On Sat, Sep 7, 2019 at 6:34 PM Brian Lachniet wrote: > Hi all, > > The version in 1.9.1 version in Jira still shows up as "unreleased": > https://issues.apache.org/jira/projects/AVRO/versions/12345552 > > Could

Re: New Committer: Ryan Skraba

Welcome and congrats! On 2019. Dec 17., Tue at 10:43, Driesprong, Fokko wrote: > Folks, > > The Project Management Committee (PMC) for Apache Avro has invited Ryan > Skraba to become a committer and we are pleased to announce that he has > accepted. Ryan is actively fixing bugs by providing

[jira] [Updated] (AVRO-1857) GenericDatumWriter.write using BufferedBinaryEncoder leaves ByteBuffer in indeterminate state

[ https://issues.apache.org/jira/browse/AVRO-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-1857: Status: Patch Available (was: Open) > GenericDatumWriter.write using BufferedBinaryEncoder lea

[jira] [Assigned] (AVRO-1857) GenericDatumWriter.write using BufferedBinaryEncoder leaves ByteBuffer in indeterminate state

[ https://issues.apache.org/jira/browse/AVRO-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar reassigned AVRO-1857: --- Assignee: Nandor Kollar > GenericDatumWriter.write using BufferedBinaryEncoder lea

[jira] [Assigned] (AVRO-1818) Avoid buffer copy in DeflateCodec.compress and decompress

[ https://issues.apache.org/jira/browse/AVRO-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar reassigned AVRO-1818: --- Assignee: Nandor Kollar > Avoid buffer copy in DeflateCodec.compress and decompr

[jira] [Updated] (AVRO-1954) Schema.Field.defaultVal() generates: Unknown datum type org.apache.avro.JsonProperties$Null

[ https://issues.apache.org/jira/browse/AVRO-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-1954: Status: Patch Available (was: Open) > Schema.Field.defaultVal() generates: Unknown datum t

[jira] [Assigned] (AVRO-1954) Schema.Field.defaultVal() generates: Unknown datum type org.apache.avro.JsonProperties$Null

[ https://issues.apache.org/jira/browse/AVRO-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar reassigned AVRO-1954: --- Assignee: Nandor Kollar > Schema.Field.defaultVal() generates: Unknown datum t

[jira] [Commented] (AVRO-1881) Avro (Java) Memory Leak when reusing JsonDecoder instance

[ https://issues.apache.org/jira/browse/AVRO-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801220#comment-15801220 ] Nandor Kollar commented on AVRO-1881: - Yes, I have, and it didn't get OutOfMemory error. I also noticed

[jira] [Assigned] (AVRO-1881) Avro (Java) Memory Leak when reusing JsonDecoder instance

[ https://issues.apache.org/jira/browse/AVRO-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar reassigned AVRO-1881: --- Assignee: Nandor Kollar > Avro (Java) Memory Leak when reusing JsonDecoder insta

[jira] [Commented] (AVRO-1931) SchemaCompatibility fails to recognize reader compatible with all branches of a union

[ https://issues.apache.org/jira/browse/AVRO-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127296#comment-16127296 ] Nandor Kollar commented on AVRO-1931: - The patch looks good to me, though it was a bit hard

[jira] [Assigned] (AVRO-2066) Wrong schema file used in one TestSpecificCompiler test case

[ https://issues.apache.org/jira/browse/AVRO-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar reassigned AVRO-2066: --- Assignee: Nandor Kollar > Wrong schema file used in one TestSpecificCompiler test c

[jira] [Updated] (AVRO-2066) Wrong schema file used in one TestSpecificCompiler test case

[ https://issues.apache.org/jira/browse/AVRO-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-2066: Status: Patch Available (was: Open) > Wrong schema file used in one TestSpecificCompiler test c

[jira] [Commented] (AVRO-1658) Add avroDoc on reflect

[ https://issues.apache.org/jira/browse/AVRO-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123468#comment-16123468 ] Nandor Kollar commented on AVRO-1658: - I didn't see any test failure after merging Evan's PR, all unit

[jira] [Commented] (AVRO-2066) Wrong schema file used in one TestSpecificCompiler test case

[ https://issues.apache.org/jira/browse/AVRO-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125438#comment-16125438 ] Nandor Kollar commented on AVRO-2066: - [~blue_impala_48d6] it seems you you did this test, could you

[jira] [Created] (AVRO-2066) Wrong schema file used in one TestSpecificCompiler test case

Nandor Kollar created AVRO-2066: --- Summary: Wrong schema file used in one TestSpecificCompiler test case Key: AVRO-2066 URL: https://issues.apache.org/jira/browse/AVRO-2066 Project: Avro Issue

[jira] [Updated] (AVRO-2066) Wrong schema file used in one TestSpecificCompiler test case

[ https://issues.apache.org/jira/browse/AVRO-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-2066: Attachment: AVRO-2066.patch > Wrong schema file used in one TestSpecificCompiler test c

[jira] [Commented] (AVRO-2050) Clear Array To Allow GC

[ https://issues.apache.org/jira/browse/AVRO-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089518#comment-16089518 ] Nandor Kollar commented on AVRO-2050: - I'm wondering why {{clear()}} method is in overridden. It looks

[jira] [Commented] (AVRO-1485) Specification says Record field type can be record name but implementation allows any named type.

[ https://issues.apache.org/jira/browse/AVRO-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16092826#comment-16092826 ] Nandor Kollar commented on AVRO-1485: - [~gszadovszky] could you please review this item

[jira] [Commented] (AVRO-2049) Remove Superfluous Configuration From AvroSerializer

[ https://issues.apache.org/jira/browse/AVRO-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101553#comment-16101553 ] Nandor Kollar commented on AVRO-2049: - Looks good to me, just one minor comment, in {{AvroSerialization

[jira] [Assigned] (AVRO-1991) Java concat tool -appendToFirst option doesn't work with local filesystem

[ https://issues.apache.org/jira/browse/AVRO-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar reassigned AVRO-1991: --- Assignee: Nandor Kollar > Java concat tool -appendToFirst option doesn't work with lo

[jira] [Comment Edited] (AVRO-1815) Incompatible schema change not detected when wrapped in a UNION

[ https://issues.apache.org/jira/browse/AVRO-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072480#comment-16072480 ] Nandor Kollar edited comment on AVRO-1815 at 7/3/17 2:16 PM: - [~gdeschut

[jira] [Commented] (AVRO-1815) Incompatible schema change not detected when wrapped in a UNION

[ https://issues.apache.org/jira/browse/AVRO-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072480#comment-16072480 ] Nandor Kollar commented on AVRO-1815: - [~gdeschut] it looks like this issue is similar to AVRO-1883

[jira] [Commented] (AVRO-1991) Java concat tool -appendToFirst option doesn't work with local filesystem

[ https://issues.apache.org/jira/browse/AVRO-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16068341#comment-16068341 ] Nandor Kollar commented on AVRO-1991: - [~busbey] I think I just found a reference to this feature! Here

[jira] [Assigned] (AVRO-2021) uuid logical type is not documented

[ https://issues.apache.org/jira/browse/AVRO-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar reassigned AVRO-2021: --- Assignee: Nandor Kollar > uuid logical type is not documen

[jira] [Updated] (AVRO-2021) uuid logical type is not documented

[ https://issues.apache.org/jira/browse/AVRO-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-2021: Attachment: AVRO-2021_1.patch > uuid logical type is not documen

[jira] [Commented] (AVRO-2021) uuid logical type is not documented

[ https://issues.apache.org/jira/browse/AVRO-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16066548#comment-16066548 ] Nandor Kollar commented on AVRO-2021: - [~gszadovszky] could you please have a look at the patch? I'm

[jira] [Updated] (AVRO-2021) uuid logical type is not documented

[ https://issues.apache.org/jira/browse/AVRO-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-2021: Status: Patch Available (was: Open) > uuid logical type is not documen

[jira] [Commented] (AVRO-2061) Improve Invalid File Format Error Message

[ https://issues.apache.org/jira/browse/AVRO-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116446#comment-16116446 ] Nandor Kollar commented on AVRO-2061: - Looks good to me. > Improve Invalid File Format Error Mess

[jira] [Commented] (AVRO-1957) TimeConversions do not implement getRecommendedSchema()

[ https://issues.apache.org/jira/browse/AVRO-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116500#comment-16116500 ] Nandor Kollar commented on AVRO-1957: - Looks good to me, {{mvn clean verify}} passed

[jira] [Updated] (AVRO-1821) Avro (Java) Memory Leak in ReflectData Caching

[ https://issues.apache.org/jira/browse/AVRO-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-1821: Fix Version/s: 1.8.1 > Avro (Java) Memory Leak in ReflectData Cach

[jira] [Commented] (AVRO-1821) Avro (Java) Memory Leak in ReflectData Caching

[ https://issues.apache.org/jira/browse/AVRO-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055373#comment-16055373 ] Nandor Kollar commented on AVRO-1821: - [~alunarbeach] it looks like [this|https://github.com/apache

[jira] [Updated] (AVRO-1064) Encoder.writeString throws NullPointerException when the charSequence is null

[ https://issues.apache.org/jira/browse/AVRO-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-1064: Resolution: Not A Bug Status: Resolved (was: Patch Available) > Encoder.writeString thr

[jira] [Commented] (AVRO-1965) Reparsing an existing schema mutates the schema

[ https://issues.apache.org/jira/browse/AVRO-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16059305#comment-16059305 ] Nandor Kollar commented on AVRO-1965: - Looks good to me too. > Reparsing an existing schema muta

[jira] [Commented] (AVRO-1991) Java concat tool -appendToFirst option doesn't work with local filesystem

[ https://issues.apache.org/jira/browse/AVRO-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063060#comment-16063060 ] Nandor Kollar commented on AVRO-1991: - [~busbey] is -appendToFirst a valid option for concat? I

[jira] [Commented] (AVRO-1990) CreateRandomFileTool should validate arguments

[ https://issues.apache.org/jira/browse/AVRO-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026366#comment-16026366 ] Nandor Kollar commented on AVRO-1990: - [~busbey] could you please review my pull request

[jira] [Updated] (AVRO-1990) CreateRandomFileTool should validate arguments

[ https://issues.apache.org/jira/browse/AVRO-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-1990: Status: Patch Available (was: Open) > CreateRandomFileTool should validate argume

[jira] [Assigned] (AVRO-1990) CreateRandomFileTool should validate arguments

[ https://issues.apache.org/jira/browse/AVRO-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar reassigned AVRO-1990: --- Assignee: Nandor Kollar > CreateRandomFileTool should validate argume

[jira] [Commented] (AVRO-1575) Platform specific end of line hardcoded in unit test causes test failure on Windows.

[ https://issues.apache.org/jira/browse/AVRO-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029218#comment-16029218 ] Nandor Kollar commented on AVRO-1575: - It seems this is fixed with the duplicate issue. [~zolyfarkas

[jira] [Commented] (AVRO-1575) Platform specific end of line hardcoded in unit test causes test failure on Windows.

[ https://issues.apache.org/jira/browse/AVRO-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029388#comment-16029388 ] Nandor Kollar commented on AVRO-1575: - Thanks, resolved as duplicate. > Platform specific end of l

[jira] [Resolved] (AVRO-1575) Platform specific end of line hardcoded in unit test causes test failure on Windows.

[ https://issues.apache.org/jira/browse/AVRO-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar resolved AVRO-1575. - Resolution: Duplicate > Platform specific end of line hardcoded in unit test causes test fail

[jira] [Commented] (AVRO-1401) @Nullable does not work with byte[]

[ https://issues.apache.org/jira/browse/AVRO-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043568#comment-16043568 ] Nandor Kollar commented on AVRO-1401: - [~gszadovszky] could you please review my pull request

[jira] [Updated] (AVRO-1401) @Nullable does not work with byte[]

[ https://issues.apache.org/jira/browse/AVRO-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-1401: Status: Patch Available (was: Open) > @Nullable does not work with b

[jira] [Assigned] (AVRO-1401) @Nullable does not work with byte[]

[ https://issues.apache.org/jira/browse/AVRO-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar reassigned AVRO-1401: --- Assignee: Nandor Kollar > @Nullable does not work with b

[jira] [Commented] (AVRO-2019) Improve documentation for logical type annotations in IDL

[ https://issues.apache.org/jira/browse/AVRO-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16053733#comment-16053733 ] Nandor Kollar commented on AVRO-2019: - Indeed, looks like this is missing from the documentation

[jira] [Updated] (AVRO-1990) CreateRandomFileTool should validate arguments

[ https://issues.apache.org/jira/browse/AVRO-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-1990: Resolution: Fixed Status: Resolved (was: Patch Available) > CreateRandomFileTool sho

[jira] [Updated] (AVRO-1990) CreateRandomFileTool should validate arguments

[ https://issues.apache.org/jira/browse/AVRO-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-1990: Fix Version/s: 1.9.0 > CreateRandomFileTool should validate argume

[jira] [Commented] (AVRO-1574) Suboptimal arraylist creation

[ https://issues.apache.org/jira/browse/AVRO-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048038#comment-16048038 ] Nandor Kollar commented on AVRO-1574: - LGTM > Suboptimal arraylist creat

[jira] [Updated] (AVRO-1485) Specification says Record field type can be record name but implementation allows any named type.

[ https://issues.apache.org/jira/browse/AVRO-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-1485: Status: Patch Available (was: Open) > Specification says Record field type can be record n

[jira] [Assigned] (AVRO-1485) Specification says Record field type can be record name but implementation allows any named type.

[ https://issues.apache.org/jira/browse/AVRO-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar reassigned AVRO-1485: --- Assignee: Nandor Kollar > Specification says Record field type can be record n

[jira] [Updated] (AVRO-1485) Specification says Record field type can be record name but implementation allows any named type.

[ https://issues.apache.org/jira/browse/AVRO-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-1485: Attachment: AVRO-1485_1.patch > Specification says Record field type can be record n

[jira] [Commented] (AVRO-1485) Specification says Record field type can be record name but implementation allows any named type.

[ https://issues.apache.org/jira/browse/AVRO-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16066080#comment-16066080 ] Nandor Kollar commented on AVRO-1485: - [~busbey] modified the doc according to Doug's comment, could

[jira] [Created] (AVRO-2077) Avro tools should have an option to check reader-writer compatibility

Nandor Kollar created AVRO-2077: --- Summary: Avro tools should have an option to check reader-writer compatibility Key: AVRO-2077 URL: https://issues.apache.org/jira/browse/AVRO-2077 Project: Avro

[jira] [Commented] (AVRO-1815) Incompatible schema change not detected when wrapped in a UNION

[ https://issues.apache.org/jira/browse/AVRO-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169932#comment-16169932 ] Nandor Kollar commented on AVRO-1815: - [~busbey], [~gszadovszky] it seems this problem is the same

[jira] [Commented] (AVRO-2074) SchemaValidator can't cope with recursive schemas?

[ https://issues.apache.org/jira/browse/AVRO-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173372#comment-16173372 ] Nandor Kollar commented on AVRO-2074: - Hm, interesting, it seems those lines which stuck in infinite

[jira] [Updated] (AVRO-2078) Avro does not enforce schema resolution rules for Decimal type

[ https://issues.apache.org/jira/browse/AVRO-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-2078: Assignee: Nandor Kollar Status: Patch Available (was: Open) > Avro does not enforce sch

[jira] [Commented] (AVRO-2078) Avro does not enforce schema resolution rules for Decimal type

[ https://issues.apache.org/jira/browse/AVRO-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174738#comment-16174738 ] Nandor Kollar commented on AVRO-2078: - Looks like a bug for me, the schema resolution logic

[jira] [Commented] (AVRO-2003) Report specific location of schema incompatibilities

[ https://issues.apache.org/jira/browse/AVRO-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173153#comment-16173153 ] Nandor Kollar commented on AVRO-2003: - Thanks [~teabot], I'll help the committers with a review soon

[jira] [Created] (AVRO-2086) Can't create specific record with a single Decimal field with default value

Nandor Kollar created AVRO-2086: --- Summary: Can't create specific record with a single Decimal field with default value Key: AVRO-2086 URL: https://issues.apache.org/jira/browse/AVRO-2086 Project: Avro

[jira] [Updated] (AVRO-2086) Can't create specific record with a single Decimal field with default value

[ https://issues.apache.org/jira/browse/AVRO-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-2086: Status: Patch Available (was: Open) > Can't create specific record with a single Decimal fi

[jira] [Assigned] (AVRO-2086) Can't create specific record with a single Decimal field with default value

[ https://issues.apache.org/jira/browse/AVRO-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar reassigned AVRO-2086: --- Assignee: Nandor Kollar > Can't create specific record with a single Decimal fi

[jira] [Created] (AVRO-2097) Improve documentation: emphasize that default values are interpreted in physical type and not in logical

Nandor Kollar created AVRO-2097: --- Summary: Improve documentation: emphasize that default values are interpreted in physical type and not in logical Key: AVRO-2097 URL: https://issues.apache.org/jira/browse/AVRO

[jira] [Commented] (AVRO-2003) Report specific location of schema incompatibilities

[ https://issues.apache.org/jira/browse/AVRO-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207135#comment-16207135 ] Nandor Kollar commented on AVRO-2003: - [~busbey] I reviewed Elliot's pull request, and looks good to me

[jira] [Updated] (AVRO-2072) ResolvingGrammarGenerator doesn't implement schema resolution correctly for unions

[ https://issues.apache.org/jira/browse/AVRO-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-2072: Component/s: java > ResolvingGrammarGenerator doesn't implement schema resolution correc

[jira] [Updated] (AVRO-2072) ResolvingGrammarGenerator doesn't implement schema resolution correctly for unions

[ https://issues.apache.org/jira/browse/AVRO-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-2072: Affects Version/s: 1.7.7 1.8.1 > ResolvingGrammarGenerator doesn't implem

[jira] [Updated] (AVRO-2072) ResolvingGrammarGenerator doesn't implement schema resolution correctly for unions

[ https://issues.apache.org/jira/browse/AVRO-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-2072: Attachment: AVRO-2072.patch > ResolvingGrammarGenerator doesn't implement schema resolut

[jira] [Updated] (AVRO-2072) ResolvingGrammarGenerator doesn't implement schema resolution correctly for unions

[ https://issues.apache.org/jira/browse/AVRO-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-2072: Attachment: AVRO-2072_3.patch > ResolvingGrammarGenerator doesn't implement schema resolut

[jira] [Commented] (AVRO-2072) ResolvingGrammarGenerator doesn't implement schema resolution correctly for unions

[ https://issues.apache.org/jira/browse/AVRO-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160994#comment-16160994 ] Nandor Kollar commented on AVRO-2072: - [~epkanol] thanks for the review, in AVRO-2072_3.patch I

[jira] [Assigned] (AVRO-2075) Allow SchemaCompatibility to report possibly lossy conversions

[ https://issues.apache.org/jira/browse/AVRO-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar reassigned AVRO-2075: --- Assignee: Anders Sundelin > Allow SchemaCompatibility to report possibly lossy conversi

[jira] [Updated] (AVRO-2072) ResolvingGrammarGenerator doesn't implement schema resolution correctly for unions

[ https://issues.apache.org/jira/browse/AVRO-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-2072: Attachment: AVRO-2072_2.patch > ResolvingGrammarGenerator doesn't implement schema resolut

[jira] [Commented] (AVRO-2072) ResolvingGrammarGenerator doesn't implement schema resolution correctly for unions

[ https://issues.apache.org/jira/browse/AVRO-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16156991#comment-16156991 ] Nandor Kollar commented on AVRO-2072: - Thanks [~epkanol], I uploaded AVRO-2072_2.patch with your

[jira] [Commented] (AVRO-2003) Report specific location of schema incompatibilities

[ https://issues.apache.org/jira/browse/AVRO-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16156938#comment-16156938 ] Nandor Kollar commented on AVRO-2003: - [~teabot] now AVRO-1933 is committed to master, due to this your

[jira] [Commented] (AVRO-2072) ResolvingGrammarGenerator doesn't implement schema resolution correctly for unions

[ https://issues.apache.org/jira/browse/AVRO-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16162605#comment-16162605 ] Nandor Kollar commented on AVRO-2072: - Thanks [~gszadovszky] and [~epkanol] for reviewing

[jira] [Updated] (AVRO-2072) ResolvingGrammarGenerator doesn't implement schema resolution correctly for unions

[ https://issues.apache.org/jira/browse/AVRO-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-2072: Resolution: Fixed Hadoop Flags: Incompatible change,Reviewed (was: Incompatible change

[jira] [Commented] (AVRO-2003) Report specific location of schema incompatibilities

[ https://issues.apache.org/jira/browse/AVRO-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188327#comment-16188327 ] Nandor Kollar commented on AVRO-2003: - [~teabot] I added some comments to the PR. > Report speci

[jira] [Updated] (AVRO-2078) Avro does not enforce schema resolution rules for Decimal type

[ https://issues.apache.org/jira/browse/AVRO-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-2078: Fix Version/s: (was: 1.8.2) > Avro does not enforce schema resolution rules for Decimal t

[jira] [Updated] (AVRO-2078) Avro does not enforce schema resolution rules for Decimal type

[ https://issues.apache.org/jira/browse/AVRO-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-2078: Affects Version/s: 1.8.2 > Avro does not enforce schema resolution rules for Decimal t

[jira] [Created] (AVRO-2083) Add Yetus InterfaceAudience annotations to Avro

Nandor Kollar created AVRO-2083: --- Summary: Add Yetus InterfaceAudience annotations to Avro Key: AVRO-2083 URL: https://issues.apache.org/jira/browse/AVRO-2083 Project: Avro Issue Type

[jira] [Commented] (AVRO-2077) Avro tools should have an option to check reader-writer compatibility

[ https://issues.apache.org/jira/browse/AVRO-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189672#comment-16189672 ] Nandor Kollar commented on AVRO-2077: - [~howellbridger] AVRO-1933 and AVRO-2003 provides details about

[jira] [Commented] (AVRO-2077) Avro tools should have an option to check reader-writer compatibility

[ https://issues.apache.org/jira/browse/AVRO-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189811#comment-16189811 ] Nandor Kollar commented on AVRO-2077: - [~howellbridger] I like the idea you proposed! Let me think

[jira] [Commented] (AVRO-1933) SchemaCompatibility class could be more user-friendly about incompatibilities

[ https://issues.apache.org/jira/browse/AVRO-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134891#comment-16134891 ] Nandor Kollar commented on AVRO-1933: - [~epkanol] since AVRO-1931 is committed to trunk now, it looks

[jira] [Updated] (AVRO-2069) Use primitive fields in generated getters & setters in Java code

[ https://issues.apache.org/jira/browse/AVRO-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandor Kollar updated AVRO-2069: Status: Patch Available (was: Open) > Use primitive fields in generated getters & setters

  1   2   3   >