1.8.2 release

[Ryan Blue]

I didn't end up having any time to put together a release candidate this
weekend. Sorry for the delay, we'll have to push for a release in January.

rb

-- 
Ryan Blue

[jira] [Commented] (AVRO-1971) AvroAlias Annotation should work on field elements

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15762183#comment-15762183
 ] 

ASF GitHub Bot commented on AVRO-1971:
--

GitHub user baunz opened a pull request:

https://github.com/apache/avro/pull/175

Allow alias annotation on fields

Sorry for the confusion, here's the f(fow now) final pul request to this 
issue I created:

https://issues.apache.org/jira/browse/AVRO-1971

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/baunz/avro AVRO-1971-AvroAlias-On-Fields

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/avro/pull/175.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #175


commit ea94c703e6df801d6832cf1167a9b326a87af83a
Author: baunz 
Date:   2016-12-18T20:48:33Z

Allow alias annotation on fields




> AvroAlias Annotation should work on field elements
> --
>
> Key: AVRO-1971
> URL: https://issues.apache.org/jira/browse/AVRO-1971
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.8.1
>Reporter: Johannes Schulte
>Priority: Minor
>
> @AvroAlias annotation works only for records / classes but not for fields 
> when using ReflectData-generated schemas. The specification allows aliases 
> for comple types AND for fields.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] avro pull request #175: Allow alias annotation on fields

[baunz]

GitHub user baunz opened a pull request:

https://github.com/apache/avro/pull/175

Allow alias annotation on fields

Sorry for the confusion, here's the f(fow now) final pul request to this 
issue I created:

https://issues.apache.org/jira/browse/AVRO-1971

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/baunz/avro AVRO-1971-AvroAlias-On-Fields

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/avro/pull/175.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #175


commit ea94c703e6df801d6832cf1167a9b326a87af83a
Author: baunz 
Date:   2016-12-18T20:48:33Z

Allow alias annotation on fields




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AVRO-1971) AvroAlias Annotation should work on field elements

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15762174#comment-15762174
 ] 

ASF GitHub Bot commented on AVRO-1971:
--

Github user baunz closed the pull request at:

https://github.com/apache/avro/pull/174


> AvroAlias Annotation should work on field elements
> --
>
> Key: AVRO-1971
> URL: https://issues.apache.org/jira/browse/AVRO-1971
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.8.1
>Reporter: Johannes Schulte
>Priority: Minor
>
> @AvroAlias annotation works only for records / classes but not for fields 
> when using ReflectData-generated schemas. The specification allows aliases 
> for comple types AND for fields.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] avro pull request #174: Allow alias annotation on fields

[baunz]

Github user baunz closed the pull request at:

https://github.com/apache/avro/pull/174


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request #171: Allow alias annotation on fields

[baunz]

Github user baunz closed the pull request at:

https://github.com/apache/avro/pull/171


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request #174: Allow alias annotation on fields

[baunz]

GitHub user baunz opened a pull request:

https://github.com/apache/avro/pull/174

Allow alias annotation on fields

See https://issues.apache.org/jira/browse/AVRO-1971

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/baunz/avro AVRO-1971-AvroAlias-On-Fields

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/avro/pull/174.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #174


commit fdbf13551ddebd6fd814d6cd4d3cb3645663a21a
Author: baunz 
Date:   2016-12-18T20:48:33Z

Allow alias annotation on fields




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AVRO-1971) AvroAlias Annotation should work on field elements

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15762171#comment-15762171
 ] 

ASF GitHub Bot commented on AVRO-1971:
--

GitHub user baunz opened a pull request:

https://github.com/apache/avro/pull/174

Allow alias annotation on fields

See https://issues.apache.org/jira/browse/AVRO-1971

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/baunz/avro AVRO-1971-AvroAlias-On-Fields

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/avro/pull/174.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #174


commit fdbf13551ddebd6fd814d6cd4d3cb3645663a21a
Author: baunz 
Date:   2016-12-18T20:48:33Z

Allow alias annotation on fields




> AvroAlias Annotation should work on field elements
> --
>
> Key: AVRO-1971
> URL: https://issues.apache.org/jira/browse/AVRO-1971
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.8.1
>Reporter: Johannes Schulte
>Priority: Minor
>
> @AvroAlias annotation works only for records / classes but not for fields 
> when using ReflectData-generated schemas. The specification allows aliases 
> for comple types AND for fields.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AVRO-1971) AvroAlias Annotation should work on field elements

[Johannes Schulte (JIRA)]

Johannes Schulte created AVRO-1971:
--

 Summary: AvroAlias Annotation should work on field elements
 Key: AVRO-1971
 URL: https://issues.apache.org/jira/browse/AVRO-1971
 Project: Avro
  Issue Type: Improvement
  Components: java
Affects Versions: 1.8.1
Reporter: Johannes Schulte
Priority: Minor


@AvroAlias annotation works only for records / classes but not for fields when 
using ReflectData-generated schemas. The specification allows aliases for 
comple types AND for fields.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] avro pull request #173: Minor cleanups.

[zicl]

GitHub user zicl opened a pull request:

https://github.com/apache/avro/pull/173

Minor cleanups.

Fixed several possible null pointer exceptions and unchecked casts.
These triggered security and code health warnings in our static code
analyzer tools.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/zicl/avro sonar-issues

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/avro/pull/173.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #173


commit 86f353024af5e4479006a546587a47d1fc40db32
Author: Zoltan Ivanfi 
Date:   2016-12-19T17:27:45Z

Minor cleanups.

Fixed several possible null pointer exceptions and unchecked casts.
These triggered security and code health warnings in our static code
analyzer tools.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (AVRO-1970) Flaky test: TestInputBytes

[Gabor Szadovszky (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AVRO-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gabor Szadovszky updated AVRO-1970:
---
Status: Patch Available  (was: Open)

> Flaky test: TestInputBytes
> --
>
> Key: AVRO-1970
> URL: https://issues.apache.org/jira/browse/AVRO-1970
> Project: Avro
>  Issue Type: Bug
>  Components: java, trevni
>Affects Versions: 1.8.1
>Reporter: Gabor Szadovszky
>Assignee: Gabor Szadovszky
>Priority: Minor
>
> The test {{org.apache.trevni.TestInputBytes}} is flaky. Sometimes it throws 
> the following exception:
> {code}
> java.lang.IllegalArgumentException: bound must be positive
>   at java.util.Random.nextInt(Random.java:388)
>   at 
> org.apache.trevni.TestInputBytes.testRandomReads(TestInputBytes.java:43)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1970) Flaky test: TestInputBytes

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15760593#comment-15760593
 ] 

ASF GitHub Bot commented on AVRO-1970:
--

GitHub user gszadovszky opened a pull request:

https://github.com/apache/avro/pull/172

AVRO-1970: Flaky test: TestInputBytes

Root cause of flaky test (probability: 1/1000):
if `length` is`0` at _line 36_ then `random.nextInt(length)` will fail with 
exception at _line 43_.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gszadovszky/avro AVRO-1970

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/avro/pull/172.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #172


commit 422e9c25377f5ef1f032e1dc8116c1c789f23222
Author: Gabor Szadovszky 
Date:   2016-12-19T08:43:33Z

AVRO-1970: Flaky test: TestInputBytes




> Flaky test: TestInputBytes
> --
>
> Key: AVRO-1970
> URL: https://issues.apache.org/jira/browse/AVRO-1970
> Project: Avro
>  Issue Type: Bug
>  Components: java, trevni
>Affects Versions: 1.8.1
>Reporter: Gabor Szadovszky
>Assignee: Gabor Szadovszky
>Priority: Minor
>
> The test {{org.apache.trevni.TestInputBytes}} is flaky. Sometimes it throws 
> the following exception:
> {code}
> java.lang.IllegalArgumentException: bound must be positive
>   at java.util.Random.nextInt(Random.java:388)
>   at 
> org.apache.trevni.TestInputBytes.testRandomReads(TestInputBytes.java:43)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] avro pull request #172: AVRO-1970: Flaky test: TestInputBytes

[gszadovszky]

GitHub user gszadovszky opened a pull request:

https://github.com/apache/avro/pull/172

AVRO-1970: Flaky test: TestInputBytes

Root cause of flaky test (probability: 1/1000):
if `length` is`0` at _line 36_ then `random.nextInt(length)` will fail with 
exception at _line 43_.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gszadovszky/avro AVRO-1970

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/avro/pull/172.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #172


commit 422e9c25377f5ef1f032e1dc8116c1c789f23222
Author: Gabor Szadovszky 
Date:   2016-12-19T08:43:33Z

AVRO-1970: Flaky test: TestInputBytes




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (AVRO-1970) Flaky test: TestInputBytes

[Gabor Szadovszky (JIRA)]

Gabor Szadovszky created AVRO-1970:
--

 Summary: Flaky test: TestInputBytes
 Key: AVRO-1970
 URL: https://issues.apache.org/jira/browse/AVRO-1970
 Project: Avro
  Issue Type: Bug
  Components: java, trevni
Affects Versions: 1.8.1
Reporter: Gabor Szadovszky
Assignee: Gabor Szadovszky
Priority: Minor


The test {{org.apache.trevni.TestInputBytes}} is flaky. Sometimes it throws the 
following exception:
{code}
java.lang.IllegalArgumentException: bound must be positive
at java.util.Random.nextInt(Random.java:388)
at 
org.apache.trevni.TestInputBytes.testRandomReads(TestInputBytes.java:43)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)