[jira] [Commented] (AVRO-1340) use default to allow old readers to specify default enum value when encountering new enum symbols

2017-08-29 Thread Doug Cutting (JIRA)
[ https://issues.apache.org/jira/browse/AVRO-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16146369#comment-16146369 ] Doug Cutting commented on AVRO-1340: I haven't had a chance to evaluate this thoroughly

Re: Avro schema resolution

2017-08-29 Thread Doug Cutting
I'm not sure why both SchemaCompatibility and SchemaValidator exist. I think folks perhaps just didn't realize the former existed when the latter was added. https://issues.apache.org/jira/browse/AVRO-1409 https://issues.apache.org/jira/browse/AVRO-1315 The latter looks like a probably more effic

[jira] [Updated] (AVRO-2039) Ruby encoding performance improvement

2017-08-29 Thread Sean Busbey (JIRA)
[ https://issues.apache.org/jira/browse/AVRO-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated AVRO-2039: -- Priority: Critical (was: Major) > Ruby encoding performance improvement > --

[jira] [Updated] (AVRO-2039) Ruby encoding performance improvement

2017-08-29 Thread Sean Busbey (JIRA)
[ https://issues.apache.org/jira/browse/AVRO-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated AVRO-2039: -- Component/s: ruby > Ruby encoding performance improvement > - > >

Re: Ruby encoding performance

2017-08-29 Thread Sean Busbey
I'd love to get this change pushed in. If someone can spend some time reviewing and confirming perf changes that'll speed up my ability to merge it. On Mon, Aug 28, 2017 at 7:51 AM, Tim Perkins wrote: > A few months ago, I submitted a patch for Ruby encoding apache/avro#230 >

Re: [VOTE] Convert to gitbox

2017-08-29 Thread Suraj Acharya
+1 On Tue, Aug 29, 2017 at 11:49 AM, Sean Busbey wrote: > +1 > > On 2017-08-29 11:29, "Sean Busbey" wrote: > > Way back in May we had consensus[1] on using gitbox so that we could > start making use of pull requests. > > > > In the subsequent JIRAs to implement, it became clear that the entry ba

Re: [VOTE] Convert to gitbox

2017-08-29 Thread Sean Busbey
+1 On 2017-08-29 11:29, "Sean Busbey" wrote: > Way back in May we had consensus[1] on using gitbox so that we could start > making use of pull requests. > > In the subsequent JIRAs to implement, it became clear that the entry bar to > start is convert our repo to use gitbox. this means the wr

Re: [VOTE] Convert to gitbox

2017-08-29 Thread Niels Basjes
+1 On Aug 29, 2017 18:50, "Gabor Szadovszky" wrote: > +1 > > On Tue, Aug 29, 2017 at 6:43 PM, Ryan Blue > wrote: > > > +! > > > > On Tue, Aug 29, 2017 at 9:29 AM, Sean Busbey wrote: > > > > > Way back in May we had consensus[1] on using gitbox so that we could > > start > > > making use of pul

Re: [VOTE] Convert to gitbox

2017-08-29 Thread Gabor Szadovszky
+1 On Tue, Aug 29, 2017 at 6:43 PM, Ryan Blue wrote: > +! > > On Tue, Aug 29, 2017 at 9:29 AM, Sean Busbey wrote: > > > Way back in May we had consensus[1] on using gitbox so that we could > start > > making use of pull requests. > > > > In the subsequent JIRAs to implement, it became clear tha

Re: [VOTE] Convert to gitbox

2017-08-29 Thread Ryan Blue
+! On Tue, Aug 29, 2017 at 9:29 AM, Sean Busbey wrote: > Way back in May we had consensus[1] on using gitbox so that we could start > making use of pull requests. > > In the subsequent JIRAs to implement, it became clear that the entry bar > to start is convert our repo to use gitbox. this means

[VOTE] Convert to gitbox

2017-08-29 Thread Sean Busbey
Way back in May we had consensus[1] on using gitbox so that we could start making use of pull requests. In the subsequent JIRAs to implement, it became clear that the entry bar to start is convert our repo to use gitbox. this means the writeable repository will be on github and some committer

[jira] [Created] (AVRO-2071) Change of signatures in release

2017-08-29 Thread Suraj Acharya (JIRA)
Suraj Acharya created AVRO-2071: --- Summary: Change of signatures in release Key: AVRO-2071 URL: https://issues.apache.org/jira/browse/AVRO-2071 Project: Avro Issue Type: Improvement Co

[jira] [Created] (AVRO-2070) Tolerate any Number when writing primitive values in Java in GenericDatumWriter

2017-08-29 Thread Daniil Gitelson (JIRA)
Daniil Gitelson created AVRO-2070: - Summary: Tolerate any Number when writing primitive values in Java in GenericDatumWriter Key: AVRO-2070 URL: https://issues.apache.org/jira/browse/AVRO-2070 Project

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

2017-08-29 Thread Daniil Gitelson (JIRA)
[ https://issues.apache.org/jira/browse/AVRO-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniil Gitelson updated AVRO-2069: -- Description: Currently, for primitive types (such as int, long, etc) generated getters and sette

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

2017-08-29 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/AVRO-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144980#comment-16144980 ] ASF GitHub Bot commented on AVRO-2069: -- GitHub user daniilguit opened a pull request:

[GitHub] avro pull request #243: AVRO-2069: Use primitive fields in generated getters...

2017-08-29 Thread daniilguit
GitHub user daniilguit opened a pull request: https://github.com/apache/avro/pull/243 AVRO-2069: Use primitive fields in generated getters & setters in Java code You can merge this pull request into a Git repository by running: $ git pull https://github.com/daniilguit/avro mas

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

2017-08-29 Thread Daniil Gitelson (JIRA)
Daniil Gitelson created AVRO-2069: - Summary: Use primitive fields in generated getters & setters in Java code Key: AVRO-2069 URL: https://issues.apache.org/jira/browse/AVRO-2069 Project: Avro