[jira] [Resolved] (AVRO-2210) Is The Avro Project Dead? Hopefully not.

[Suraj Acharya (JIRA)]

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

Suraj Acharya resolved AVRO-2210.
-
Resolution: Fixed

No the project is very much alive.

You can join in on the conversation on users@ and at dev@

> Is The Avro Project Dead? Hopefully not.
> 
>
> Key: AVRO-2210
> URL: https://issues.apache.org/jira/browse/AVRO-2210
> Project: Avro
>  Issue Type: Wish
>Reporter: ldawson
>Priority: Major
>
> I'm just curious about it's future. It's an awesome technology that'd I'd 
> love to keep using and supporting. It's been over one year since the last 
> release, which is why I'm asking.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AVRO-1886) Improve error reporting for schema validation

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-1886:
-

Yes that will be perfect.

> Improve error reporting for schema validation
> -
>
> Key: AVRO-1886
> URL: https://issues.apache.org/jira/browse/AVRO-1886
> Project: Avro
>  Issue Type: Improvement
>  Components: ruby
>Reporter: Miroslav Csonka
>Assignee: Miroslav Csonka
>Priority: Major
> Fix For: 1.9.0, 1.8.3
>
>
> In Funding Circle we use avro schema to validate some financial data and 
> we've found ourselves wondering what is invalid. We've noticed that avro 
> [does already 
> validation|https://github.com/apache/avro/blob/master/lang/ruby/lib/avro/schema.rb#L94],
>  but does not report what fields are invalid, so we've decided to change it 
> and we use Avro as a validation library.
> h5. What error messages to expect?
> We communicate errors for a given payload in format "at   
> ".
> For  we've decided to use syntax similar to json path:
> * . refers to root
> * \[0\] first index in array
> * .age would match 42 from {"age": 42}
> Error within object *person* and his optional array *houses* on *second item* 
> with key *number_of_rooms*:
> {quote}
> at .person.houses\[1\].number_of_rooms expected type long, got string 
> with value "not valid at all"
> {quote}
> Example of multiple errors for a single payload:
> {quote}
> at .\[0\] expected type int, got null
> at .\[1\] expected type int, got string with value \"e\"
> {quote}
> More examples can be seen at 
> https://github.com/apache/avro/pull/111/files#diff-830ac80276854fceefa3f92c346d165f



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Issue while importing avro the project

[Suraj Acharya]

So if you are trying to build only java then I would recommend you go to
the java dir in lang and run maven from there.

You can also run ./build.sh and build all the modules from there.

Hope this unblocks you.

Suraj

Sent from my phone.


On Wed, May 9, 2018, 12:35 AM Rumesh Krishnan  wrote:

> Hi everyone,
>
>
> I was able to clone the Avro from git using the bellow commend.
>
> git clone https://github.com/apache/avro.git -o github
>
> where as, building the project without any modification, facing some issue.
>
> D:\Rumesh\OpenSource\avro>mvn compile
> [INFO] Scanning for projects...
> [WARNING] The project org.apache.avro:avro-toplevel:pom:1.9.0-SNAPSHOT
> uses prerequisites which is only intended for maven-plugin projects
> but not for
>  non maven-plugin projects. For such purposes you should use the
> maven-enforcer-plugin. See
> https://maven.apache.org/enforcer/enforcer-rules/requireMa
> venVersion.html
>  >
> [INFO]
> 
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache Avro Toplevel
>  [pom]
> [INFO] Apache Avro Java
>  [pom]
> [INFO] Apache Avro Guava Dependencies
>  [jar]
> [INFO] Apache Avro
>  [bundle]
> [INFO] Apache Avro Compiler
> [bundle]
> [INFO] Apache Avro Maven Plugin
> [maven-plugin]
> [INFO] Apache Avro IPC
>  [bundle]
> [INFO] Trevni Java
> [pom]
> [INFO] Trevni Java Core
>  [jar]
> [INFO] Apache Avro Mapred API
> [bundle]
> [INFO] Trevni Java Avro
>  [jar]
> [INFO] Trevni Specification
>  [pom]
> [INFO] Apache Avro Tools
> [jar]
> [INFO] Apache Avro Protobuf Compatibility
> [bundle]
> [INFO] Apache Avro Thrift Compatibility
> [bundle]
> [INFO] Apache Avro Maven Archetypes
>  [pom]
> [INFO] Apache Avro Maven Service Archetype
> [maven-archetype]
> [INFO] Apache Avro gRPC
> [bundle]
> [INFO]
> [INFO] ---< org.apache.avro:avro-toplevel
> >
> [INFO] Building Apache Avro Toplevel 1.9.0-SNAPSHOT
> [1/18]
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @
> avro-toplevel ---
> [INFO]
> [INFO] < org.apache.avro:avro-parent
> >-
> [INFO] Building Apache Avro Java 1.9.0-SNAPSHOT
> [2/18]
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @
> avro-parent ---
> [INFO]
> [INFO] --< org.apache.avro:avro-guava-dependencies
> >---
> [INFO] Building Apache Avro Guava Dependencies 1.9.0-SNAPSHOT
> [3/18]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @
> avro-guava-dependencies ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
> avro-guava-dependencies ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.6.0:compile (default-compile) @
> avro-guava-dependencies ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> D:\Rumesh\OpenSource\avro\lang\java\guava\target\classes
> [INFO]
> [INFO] < org.apache.avro:avro
> >
> [INFO] Building Apache Avro 1.9.0-SNAPSHOT
>  [4/18]
> [INFO] ---[ bundle
> ]---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @ avro ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ avro
> ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 1 resource
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.6.0:compile (default-compile) @ avro ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 138 source files to
> D:\Rumesh\OpenSource\avro\lang\java\avro\target\classes
> [WARNING]
> /D:/Rumesh/OpenSource/avro/lang/java/avro/src/main/java/org/apache/avro/reflect/FieldAccessUnsafe.java:[27,16]
> sun.misc.Unsafe is internal p
> roprietary API and may be removed in a future release
> [WARNING]
> /D:/Rumesh/OpenSource/avro/lang/java/avro/src/main/java/org/apache/avro/reflect/FieldAccessUnsafe.java:[32,24]
> sun.misc.Unsafe is internal p
> roprietary API and may be removed in a future release
> [WARNING]
> /D:/Rumesh/OpenSource/avro/lang/java/avro/src/main/java/org/apache/avro/reflect/FieldAccessUnsafe.java:[36,25]
> sun.misc.Unsafe is internal p
> roprietary API and may be removed in a future release
> [WARNING]
> 

Re: WELCOME to dev@avro.apache.org

[Suraj Acharya]

Hi,
I have filed : https://issues.apache.org/jira/browse/AVRO-2163
If you believe any fix is needed for the release please link it.
If you want any change in please contribute.

Thanks
Suraj Acharya


On Thu, Mar 22, 2018 at 8:55 AM, Bridger Howell <bhow...@sofi.org> wrote:

> Not a committer, but I'd like to chime in and say that I'd absolutely love
> to see another set of official releases soon.
>
> When looking through the blockers in JIRA, AVRO-1810 and AVRO-1891 stand
> out a bit - does anybody know if those issues should actually be considered
> "blockers"?
> Caveat here: I do have a personal interest in seeing AVRO-1891 fixed, and
> if we do decide that it is actually a blocker, I would definitely be
> willing to volunteer some time to help sort it out quickly.
>
> On Thu, Mar 22, 2018 at 8:55 AM, Edward Anderson <eander...@doximity.com>
> wrote:
>
> > Hi,
> >
> > There have been a lot of great improvements
> > <https://github.com/apache/avro/compare/release-1.8.2...master> since
> May
> > 2017 when Avro 1.8.2 was released—241 commits from 55 different
> > contributors over nearly a year. We would love to see these included in a
> > new versioned release. Right now, people affected by this year's worth of
> > fixes need to work around the issues or do a local build of master, both
> of
> > which are inconvenient. The number of users affected will continue to
> grow
> > until the next release.
> >
> > Do you agree that it's time for a new release? If not now, when do you
> > think will be best? We wanted to check in before starting our own
> > workarounds.
> >
> > Thanks for all your work on this great project!
> >
> > Best,
> >
> > Edward Anderson
> > Software Engineer
> > Doximity, Inc.
> >
> > On Thu, Mar 22, 2018 at 10:54 AM, <dev-h...@avro.apache.org> wrote:
> >
> > > Hi! This is the ezmlm program. I'm managing the
> > > dev@avro.apache.org mailing list.
> > >
> > > I'm working for my owner, who can be reached
> > > at dev-ow...@avro.apache.org.
> > >
> > > Acknowledgment: I have added the address
> > >
> > >eander...@doximity.com
> > >
> > > to the dev mailing list.
> > >
> > > Welcome to dev@avro.apache.org!
> > >
> > > Please save this message so that you know the address you are
> > > subscribed under, in case you later want to unsubscribe or change your
> > > subscription address.
> > >
> > >
> > > --- Administrative commands for the dev list ---
> > >
> > > I can handle administrative requests automatically. Please
> > > do not send them to the list address! Instead, send
> > > your message to the correct command address:
> > >
> > > To subscribe to the list, send a message to:
> > ><dev-subscr...@avro.apache.org>
> > >
> > > To remove your address from the list, send a message to:
> > ><dev-unsubscr...@avro.apache.org>
> > >
> > > Send mail to the following for info and FAQ for this list:
> > ><dev-i...@avro.apache.org>
> > ><dev-...@avro.apache.org>
> > >
> > > Similar addresses exist for the digest list:
> > ><dev-digest-subscr...@avro.apache.org>
> > ><dev-digest-unsubscr...@avro.apache.org>
> > >
> > > To get messages 123 through 145 (a maximum of 100 per request), mail:
> > ><dev-get.123_...@avro.apache.org>
> > >
> > > To get an index with subject and author for messages 123-456 , mail:
> > ><dev-index.123_...@avro.apache.org>
> > >
> > > They are always returned as sets of 100, max 2000 per request,
> > > so you'll actually get 100-499.
> > >
> > > To receive all messages with the same subject as message 12345,
> > > send a short message to:
> > ><dev-thread.12...@avro.apache.org>
> > >
> > > The messages should contain one line or word of text to avoid being
> > > treated as sp@m, but I will ignore their content.
> > > Only the ADDRESS you send to is important.
> > >
> > > You can start a subscription for an alternate address,
> > > for example "john@host.domain", just add a hyphen and your
> > > address (with '=' instead of '@') after the command word:
> > > 

[jira] [Updated] (AVRO-2163) Release 1.8.3

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-2163:

Description: Please link to any issues that should be considered blockers 
for the 1.8.3 release.  (was: Please link to any issues that should be 
considered blockers for the 1.8.2 release.)

> Release 1.8.3
> -
>
> Key: AVRO-2163
> URL: https://issues.apache.org/jira/browse/AVRO-2163
> Project: Avro
>  Issue Type: Task
>  Components: community
>Affects Versions: 1.8.3
>Reporter: Sean Busbey
>    Assignee: Suraj Acharya
>Priority: Major
> Fix For: 1.8.3
>
>
> Please link to any issues that should be considered blockers for the 1.8.3 
> release.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AVRO-2163) Release 1.8.3

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-2163:

Fix Version/s: (was: 1.8.2)
   1.8.3

> Release 1.8.3
> -
>
> Key: AVRO-2163
> URL: https://issues.apache.org/jira/browse/AVRO-2163
> Project: Avro
>  Issue Type: Task
>  Components: community
>Affects Versions: 1.8.3
>Reporter: Sean Busbey
>    Assignee: Suraj Acharya
>Priority: Major
> Fix For: 1.8.3
>
>
> Please link to any issues that should be considered blockers for the 1.8.3 
> release.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AVRO-2163) Release 1.8.3

[Suraj Acharya (JIRA)]

Suraj Acharya created AVRO-2163:
---

 Summary: Release 1.8.3
 Key: AVRO-2163
 URL: https://issues.apache.org/jira/browse/AVRO-2163
 Project: Avro
  Issue Type: Task
  Components: community
Affects Versions: 1.8.2
Reporter: Sean Busbey
Assignee: Suraj Acharya
 Fix For: 1.8.2


Please link to any issues that should be considered blockers for the 1.8.2 
release.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AVRO-2163) Release 1.8.3

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-2163:

Affects Version/s: (was: 1.8.2)
   1.8.3

> Release 1.8.3
> -
>
> Key: AVRO-2163
> URL: https://issues.apache.org/jira/browse/AVRO-2163
> Project: Avro
>  Issue Type: Task
>  Components: community
>Affects Versions: 1.8.3
>Reporter: Sean Busbey
>    Assignee: Suraj Acharya
>Priority: Major
> Fix For: 1.8.3
>
>
> Please link to any issues that should be considered blockers for the 1.8.2 
> release.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Licensing problem (LGPL in codebase!!)

[Suraj Acharya]

As part of the release we do run the rat plugin.
So it is a highly unlikely this would have been run through a release.
However, changing it now is a great addition since the release manager has
to go through the whole license check for all of the files.
Also, as Sean mentioned anyone who has made any changes to the file after
the addition of the license will also need to be informed of the change to
the license.

Thanks

Suraj


On Thu, Dec 14, 2017 at 2:49 AM, Niels Basjes  wrote:

> Hi all,
>
> After we hear back from Thiru I would like Zoltan to fix these 4 files.
>
> lang/java/compiler/src/main/java/org/apache/avro/compiler/
> schema/SchemaVisitorAction.java
> lang/java/compiler/src/main/java/org/apache/avro/compiler/
> schema/SchemaVisitor.java
> lang/java/compiler/src/main/java/org/apache/avro/compiler/
> schema/Schemas.java
> lang/java/compiler/src/main/java/org/apache/avro/compiler/
> schema/CloningVisitor.java
>
> See: https://issues.apache.org/jira/browse/AVRO-2118
>
> After those have been fixed we can commit this change (guys, please review
> this. Thanks.)
> https://issues.apache.org/jira/browse/AVRO-2119
>
> Niels Basjes
>
>
> On Thu, Dec 14, 2017 at 11:11 AM, Niels Basjes  wrote:
>
> > Hi all,
> >
> > I had a closer look at the code base.
> >
> > Most important:
> > 1) I have found these files only in the master branch.
> > 2) I checked both release 1.8.2 and 1.7.7 and in these files are NOT
> > present in any of those releases. (
> > So we're ok on this part.
> >
> > I have found exactly 2 files with this problem:
> > ./lang/java/compiler/src/main/java/org/apache/avro/compiler/
> > schema/SchemaVisitorAction.java
> > ./lang/java/compiler/src/main/java/org/apache/avro/compiler/
> > schema/SchemaVisitor.java
> >
> > I have found 1 additional commit that touches these two files:
> >
> > https://github.com/apache/avro/commit/9132015450a2ad6f56cd582b393e8f
> > 1b8df573c9
> >
> > commit 9132015450a2ad6f56cd582b393e8f1b8df573c9
> >> Author: Thiruvalluvan M G 
> >> AuthorDate: Sun Apr 30 21:02:02 2017 +0530
> >> Commit: Thiruvalluvan M G 
> >> CommitDate: Sun Apr 30 23:31:29 2017 +0530
> >> Added more tests and fixed a couple of bugs. Also formatted the code
> >
> >
> > In both these files the only changes are:
> > - Removing the author tag
> > - Whitespace changes.
> >
> > See:
> > https://github.com/apache/avro/commit/9132015450a2ad6f56cd582b393e8f
> > 1b8df573c9#diff-d0adffb4097a1e43917fd5c3f2aae1ab
> > https://github.com/apache/avro/commit/9132015450a2ad6f56cd582b393e8f
> > 1b8df573c9#diff-ced3f0d25217ef63c2f2ea09a8b60e92
> >
> > @Thiru: To be 100% sure: You agree with changing these two files to the
> > Apache license?
> >
> > Niels Basjes
> >
> >
> > On Wed, Dec 13, 2017 at 6:47 PM, Sean Busbey  wrote:
> >
> >> In addition to Zoltan we'll need to confirm anyone else who has modified
> >> the files.
> >>
> >> On Dec 13, 2017 11:46, "Sean Busbey"  wrote:
> >>
> >> > Have these files made it into a release?
> >> >
> >> > On Dec 13, 2017 10:18, "Niels Basjes"  wrote:
> >> >
> >> >> Zoltan,
> >> >>
> >> >> Because the copyright notice now says you own it I guess the best way
> >> to
> >> >> approach this is is when you put up a pull request with all those
> files
> >> >> files having a new license header.
> >> >> That way it is clear that you made the license switch. I think this
> >> should
> >> >> be a separate jira to document this clearly.
> >> >>
> >> >> What do you guys think about this approach?
> >> >>
> >> >> @Nandor / Gabor: I'll put up a ticket that we should run rat much
> more
> >> >> often (for both 1.8 and master). (i.e. no longer only in separate
> >> profile
> >> >> of maven)
> >> >>
> >> >> Niels Basjes
> >> >>
> >> >>
> >> >> On Wed, Dec 13, 2017 at 4:37 PM, Zoltan Farkas
> >> >>  >> >> > wrote:
> >> >>
> >> >> > Hi Niels, the license is a mistake made by me.
> >> >> > Those files were based from my work on spf4j-avro which is
> currently
> >> >> dual
> >> >> > licensed with LGPL and Apache .
> >> >> >
> >> >> > We should just replace the license headers with the appropriate
> >> Apache
> >> >> > header.
> >> >> > Let me know if you need me to do anything.
> >> >> >
> >> >> > Thank you
> >> >> >
> >> >> > --z
> >> >> >
> >> >> > > On Dec 13, 2017, at 8:14 AM, Niels Basjes 
> wrote:
> >> >> > >
> >> >> > > Hi all,
> >> >> > >
> >> >> > > I was going through the codebase and I found that several files
> are
> >> >> not
> >> >> > > Apache licensed.
> >> >> > >
> >> >> > > https://github.com/apache/avro/tree/master/lang/java/
> >> >> > compiler/src/main/java/org/apache/avro/compiler/schema
> >> >> > >
> >> >> > > Some of these files do not have a copyright block (fixable), yet
> >> some
> >> >> > have
> >> >> > > this:
> >> >> > >
> >> >> > > /*
> >> >> > >
> >> >> > > * Copyright 

Re: [VOTE] Convert to gitbox

[Suraj Acharya]

Ryan had filed an Infra ticket to turn it on.
I am not sure what the status of that ticket is.
I don't have view privileges on that ticket.

Suraj

On Wed, Dec 6, 2017 at 3:09 AM, Niels Basjes <ni...@basjes.nl> wrote:

> Hi,
>
> I see this transition was started but at this point it does not seem to
> work yet.
> What is the current status?
>
> Niels
>
> On Tue, Aug 29, 2017 at 9:14 PM, Suraj Acharya <su...@apache.org> wrote:
>
> > +1
> >
> > On Tue, Aug 29, 2017 at 11:49 AM, Sean Busbey <bus...@apache.org> wrote:
> >
> > > +1
> > >
> > > On 2017-08-29 11:29, "Sean Busbey"<bus...@apache.org> 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 writeable
> > > repository will be on github and some committer set up will be
> > needed[2]. I
> > > don't think this got adequately conveyed originally, so I wanted to
> call
> > it
> > > out here.
> > > >
> > > > Additionally, the infra process for converting to gitbox requires a
> > link
> > > to a community consensus thread. While I think we already had that back
> > in
> > > [1], May was a long time ago and some folks might not be watching for
> > > [DISCUSS] threads.
> > > >
> > > > Please vote:
> > > >
> > > > +1: we should convert to gitbox and enable pull request merging
> > > > -1: we should not convert to gitbox because...
> > > >
> > > > Vote will be open for at least 72 hours and will be subject to
> Majority
> > > Approval (3 or more +1s and more +1s than -1s).
> > > >
> > > > [1]: https://s.apache.org/ieB0
> > > > [2]: Committers will need to flag a github account as theirs via the
> > > account linking utility:
> > > > https://gitbox.apache.org/setup/
> > > >
> > > > The git-wip repository will also cease, so folks who currently use it
> > > will need to update their remote url for existing git clones. We can
> call
> > > this out in our contribution docs.
> > > >
> > >
> >
>
>
>
> --
> Best regards / Met vriendelijke groeten,
>
> Niels Basjes
>

[jira] [Commented] (AVRO-1407) NettyTransceiver can cause a infinite loop when slow to connect

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-1407:
-

Yes.
Feel free to cherry-pick it back to 1.7.8.
I am for the time being removing the release version 1.7.8 from the Jira

> NettyTransceiver can cause a infinite loop when slow to connect
> ---
>
> Key: AVRO-1407
> URL: https://issues.apache.org/jira/browse/AVRO-1407
> Project: Avro
>  Issue Type: Bug
>  Components: java
>Affects Versions: 1.7.5, 1.7.6
>Reporter: Gareth Davis
>Assignee: Gareth Davis
> Fix For: 1.8.0
>
> Attachments: AVRO-1407-1.patch, AVRO-1407-2.patch, 
> AVRO-1407-testcase.patch
>
>
> When a new {{NettyTransceiver}} is created it forces the channel to be 
> allocated and connected to the remote host. it waits for the connectTimeout 
> ms on the [connect channel 
> future|https://github.com/apache/avro/blob/1579ab1ac95731630af58fc303a07c9bf28541d6/lang/java/ipc/src/main/java/org/apache/avro/ipc/NettyTransceiver.java#L271]
>  this is obivously a good thing it's only that on being unsuccessful, ie 
> {{!channelFuture.isSuccess()}} an exception is thrown and the call to the 
> constructor fails with an {{IOException}}, but has the potential to leave a 
> active channel associated with the {{ChannelFactory}}
> The problem is that a Netty {{NioClientSocketChannelFactory}} will not 
> shutdown if there are active channels still around and if you have supplied 
> the {{ChannelFactory}} to the {{NettyTransceiver}} then  you will not be able 
> to cancel it by calling {{ChannelFactory.releaseExternalResources()}} like 
> the [Flume Avro RPC client 
> does|https://github.com/apache/flume/blob/b8cf789b8509b1e5be05dd0b0b16c5d9af9698ae/flume-ng-sdk/src/main/java/org/apache/flume/api/NettyAvroRpcClient.java#L158].
>  In order to recreate this you need a very laggy network, where the connect 
> attempt takes longer than the connect timeout but does actually work, this 
> very hard to organise in a test case, although I do have a test setup using 
> vagrant VM's that recreates this everytime, using the Flume RPC client and 
> server.
> The following stack is from a production system, it won't ever leave recover 
> until the channel is disconnected (by forcing a disconnect at the remote 
> host) or restarting the JVM.
> {noformat:title=Production stack trace}
> "TLOG-0" daemon prio=10 tid=0x7f581c7be800 nid=0x39a1 waiting on 
> condition [0x7f57ef9f2000]
>   java.lang.Thread.State: TIMED_WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   parking to wait for <0x0007218b16e0> (a 
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
>   at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:196)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2025)
>   at 
> java.util.concurrent.ThreadPoolExecutor.awaitTermination(ThreadPoolExecutor.java:1253)
>   at 
> org.jboss.netty.util.internal.ExecutorUtil.terminate(ExecutorUtil.java:103)
>   at 
> org.jboss.netty.channel.socket.nio.AbstractNioWorkerPool.releaseExternalResources(AbstractNioWorkerPool.java:80)
>   at 
> org.jboss.netty.channel.socket.nio.NioClientSocketChannelFactory.releaseExternalResources(NioClientSocketChannelFactory.java:181)
>   at 
> org.apache.flume.api.NettyAvroRpcClient.connect(NettyAvroRpcClient.java:142)
>   at 
> org.apache.flume.api.NettyAvroRpcClient.connect(NettyAvroRpcClient.java:101)
>   at 
> org.apache.flume.api.NettyAvroRpcClient.configure(NettyAvroRpcClient.java:564)
>   locked <0x0006c30ae7b0> (a org.apache.flume.api.NettyAvroRpcClient)
>   at 
> org.apache.flume.api.RpcClientFactory.getInstance(RpcClientFactory.java:88)
>   at 
> org.apache.flume.api.LoadBalancingRpcClient.createClient(LoadBalancingRpcClient.java:214)
>   at 
> org.apache.flume.api.LoadBalancingRpcClient.getClient(LoadBalancingRpcClient.java:205)
>   locked <0x0006a97b18e8> (a org.apache.flume.api.LoadBalancingRpcClient)
>   at 
> org.apache.flume.api.LoadBalancingRpcClient.appendBatch(LoadBalancingRpcClient.java:95)
>   at 
> com.ean.platform.components.tlog.client.service.AvroRpcEventRouter$1.call(AvroRpcEventRouter.java:45)
>   at 
> com.ean.platform.components.tlog.client.service.AvroRpcEventRouter$1.call(AvroRpcEventRouter.java:43)
> {noformat}
> The solution is very simple, and a patch should be along in a moment.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AVRO-1407) NettyTransceiver can cause a infinite loop when slow to connect

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1407:

Fix Version/s: (was: 1.7.8)

> NettyTransceiver can cause a infinite loop when slow to connect
> ---
>
> Key: AVRO-1407
> URL: https://issues.apache.org/jira/browse/AVRO-1407
> Project: Avro
>  Issue Type: Bug
>  Components: java
>Affects Versions: 1.7.5, 1.7.6
>Reporter: Gareth Davis
>Assignee: Gareth Davis
> Fix For: 1.8.0
>
> Attachments: AVRO-1407-1.patch, AVRO-1407-2.patch, 
> AVRO-1407-testcase.patch
>
>
> When a new {{NettyTransceiver}} is created it forces the channel to be 
> allocated and connected to the remote host. it waits for the connectTimeout 
> ms on the [connect channel 
> future|https://github.com/apache/avro/blob/1579ab1ac95731630af58fc303a07c9bf28541d6/lang/java/ipc/src/main/java/org/apache/avro/ipc/NettyTransceiver.java#L271]
>  this is obivously a good thing it's only that on being unsuccessful, ie 
> {{!channelFuture.isSuccess()}} an exception is thrown and the call to the 
> constructor fails with an {{IOException}}, but has the potential to leave a 
> active channel associated with the {{ChannelFactory}}
> The problem is that a Netty {{NioClientSocketChannelFactory}} will not 
> shutdown if there are active channels still around and if you have supplied 
> the {{ChannelFactory}} to the {{NettyTransceiver}} then  you will not be able 
> to cancel it by calling {{ChannelFactory.releaseExternalResources()}} like 
> the [Flume Avro RPC client 
> does|https://github.com/apache/flume/blob/b8cf789b8509b1e5be05dd0b0b16c5d9af9698ae/flume-ng-sdk/src/main/java/org/apache/flume/api/NettyAvroRpcClient.java#L158].
>  In order to recreate this you need a very laggy network, where the connect 
> attempt takes longer than the connect timeout but does actually work, this 
> very hard to organise in a test case, although I do have a test setup using 
> vagrant VM's that recreates this everytime, using the Flume RPC client and 
> server.
> The following stack is from a production system, it won't ever leave recover 
> until the channel is disconnected (by forcing a disconnect at the remote 
> host) or restarting the JVM.
> {noformat:title=Production stack trace}
> "TLOG-0" daemon prio=10 tid=0x7f581c7be800 nid=0x39a1 waiting on 
> condition [0x7f57ef9f2000]
>   java.lang.Thread.State: TIMED_WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   parking to wait for <0x0007218b16e0> (a 
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
>   at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:196)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2025)
>   at 
> java.util.concurrent.ThreadPoolExecutor.awaitTermination(ThreadPoolExecutor.java:1253)
>   at 
> org.jboss.netty.util.internal.ExecutorUtil.terminate(ExecutorUtil.java:103)
>   at 
> org.jboss.netty.channel.socket.nio.AbstractNioWorkerPool.releaseExternalResources(AbstractNioWorkerPool.java:80)
>   at 
> org.jboss.netty.channel.socket.nio.NioClientSocketChannelFactory.releaseExternalResources(NioClientSocketChannelFactory.java:181)
>   at 
> org.apache.flume.api.NettyAvroRpcClient.connect(NettyAvroRpcClient.java:142)
>   at 
> org.apache.flume.api.NettyAvroRpcClient.connect(NettyAvroRpcClient.java:101)
>   at 
> org.apache.flume.api.NettyAvroRpcClient.configure(NettyAvroRpcClient.java:564)
>   locked <0x0006c30ae7b0> (a org.apache.flume.api.NettyAvroRpcClient)
>   at 
> org.apache.flume.api.RpcClientFactory.getInstance(RpcClientFactory.java:88)
>   at 
> org.apache.flume.api.LoadBalancingRpcClient.createClient(LoadBalancingRpcClient.java:214)
>   at 
> org.apache.flume.api.LoadBalancingRpcClient.getClient(LoadBalancingRpcClient.java:205)
>   locked <0x0006a97b18e8> (a org.apache.flume.api.LoadBalancingRpcClient)
>   at 
> org.apache.flume.api.LoadBalancingRpcClient.appendBatch(LoadBalancingRpcClient.java:95)
>   at 
> com.ean.platform.components.tlog.client.service.AvroRpcEventRouter$1.call(AvroRpcEventRouter.java:45)
>   at 
> com.ean.platform.components.tlog.client.service.AvroRpcEventRouter$1.call(AvroRpcEventRouter.java:43)
> {noformat}
> The solution is very simple, and a patch should be along in a moment.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AVRO-1597) Random data tool writes corrupt data to standard output

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-1597:
-

Seems like the issue is that the patch is present in the code, but it has lost 
its history.
You can see the changes made 
https://issues.apache.org/jira/secure/attachment/12677013/AVRO-1597.patch in 
https://github.com/apache/avro/blame/branch-1.7/lang/java/trevni/core/src/test/java/org/apache/trevni/TestUtil.java


> Random data tool writes corrupt data to standard output
> ---
>
> Key: AVRO-1597
> URL: https://issues.apache.org/jira/browse/AVRO-1597
> Project: Avro
>  Issue Type: Bug
>  Components: java
>Reporter: Doug Cutting
>Assignee: Doug Cutting
> Fix For: 1.7.8, 1.8.0
>
> Attachments: AVRO-1597.patch
>
>
> When 'random' command is used to write a data file to standard output that 
> file is corrupt.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

1.7.8 Release of Apache Avro

[Suraj Acharya]

Hi,

I have done the cleanup of all the requirements needed for the release of
Apache Avro-1.7.8[1].
The 1.7 branch is building.
All the required cherry-picks are in the branch-1.7.
Does anyone want to be a release manager? A minimum requirement is you need
to be a committer to the project.

If no one is interested in it, I will work on it this week and try to get a
release going in the next week. Just wanted to see if anyone is interested.
Thanks a lot for the patience with this release.

[1]: https://issues.apache.org/jira/browse/AVRO-1998

If you have any questions feel free to reach out to me.

Thanks
Suraj Acharya

[jira] [Commented] (AVRO-1998) Make a release for 1.7.8

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-1998:
-

The cherry-picking of all the changes is now complete.


> Make a release for 1.7.8
> 
>
> Key: AVRO-1998
> URL: https://issues.apache.org/jira/browse/AVRO-1998
> Project: Avro
>  Issue Type: Task
>  Components: community
>Affects Versions: 1.7.7
>    Reporter: Suraj Acharya
>
> There have been quite a few issues fixed in a 1.7 branch since 1.7.7.
> Here is a list of all the issues present in the 1.7.X branch 
> [Jira Filter | 
> https://issues.apache.org/jira/browse/AVRO-1489?jql=project%20%3D%20AVRO%20AND%20fixVersion%20%3D%201.7.8%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC]
> I would appreciate if people who need the release can help out with the 
> patches currently present so we can merge those and get an updated 1.7.8 
> release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AVRO-2062) Cherry-pick commits missing.

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-2062:
-

Finished all the cherry-pick commits. 
The build has been successful.
Closing this.

> Cherry-pick commits missing.
> 
>
> Key: AVRO-2062
> URL: https://issues.apache.org/jira/browse/AVRO-2062
> Project: Avro
>  Issue Type: Sub-task
>  Components: community
>Affects Versions: 1.7.8
>    Reporter: Suraj Acharya
>    Assignee: Suraj Acharya
>Priority: Blocker
> Fix For: 1.7.8
>
>
> Missing Cherry-picks :
> AVRO-1719
> AVRO-1683
> AVRO-1656



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (AVRO-2062) Cherry-pick commits missing.

[Suraj Acharya (JIRA)]

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

Suraj Acharya resolved AVRO-2062.
-
Resolution: Fixed

> Cherry-pick commits missing.
> 
>
> Key: AVRO-2062
> URL: https://issues.apache.org/jira/browse/AVRO-2062
> Project: Avro
>  Issue Type: Sub-task
>  Components: community
>Affects Versions: 1.7.8
>    Reporter: Suraj Acharya
>    Assignee: Suraj Acharya
>Priority: Blocker
> Fix For: 1.7.8
>
>
> Missing Cherry-picks :
> AVRO-1719
> AVRO-1683
> AVRO-1656



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (AVRO-2062) Cherry-pick commits missing.

[Suraj Acharya (JIRA)]

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

Suraj Acharya closed AVRO-2062.
---

> Cherry-pick commits missing.
> 
>
> Key: AVRO-2062
> URL: https://issues.apache.org/jira/browse/AVRO-2062
> Project: Avro
>  Issue Type: Sub-task
>  Components: community
>Affects Versions: 1.7.8
>    Reporter: Suraj Acharya
>    Assignee: Suraj Acharya
>Priority: Blocker
> Fix For: 1.7.8
>
>
> Missing Cherry-picks :
> AVRO-1719
> AVRO-1683
> AVRO-1656



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [DISCUSS] October board report draft

[Suraj Acharya]

Looks good.
Thanks for the report Ryan.

Suraj

On Thu, Oct 12, 2017 at 10:01 AM, Ryan Blue <rb...@netflix.com.invalid>
wrote:

> Hi everyone,
>
> Here's my current draft for the October board report. Please let me know if
> there's any activity you'd like to have included.
>
> Also, I've added to the report that I plan to move on as PMC chair.
> Nominations are open for a new one!
>
> rb
>
> ## Description:
>
> - Avro is a cross-language data serialization system.
>
> ## Issues:
>
> - There are no issues requiring board attention at this time.
>
> ## Activity:
>
> - 1.8.2 released 13 May 2017.
> - Planning to rotate the PMC chair.
>
> ## Health report:
>
> - No significant changes from the last report.
>
> ## PMC changes:
>
> - Currently 18 PMC members.
> - Last PMC addition was Suraj Acharya on Wed Apr 12 2017
>
> ## Committer base changes:
>
> - Currently 25 committers.
> - New commmitters:
> - Gábor Szádovszky was added as a committer on Sat Feb 04 2017
> - Suraj Acharya was added as a committer on Sat Feb 04 2017
>
> ## Releases:
>
> - Last release was 1.8.2 on 13 May 2017
>
> ## Mailing list activity:
>
> - dev@avro.apache.org:
> - 302 subscribers (up 11 in the last 3 months)
> - 591 emails sent to list (417 in previous quarter)
>
> - u...@avro.apache.org:
> - 669 subscribers (up 9 in the last 3 months):
> - 44 emails sent to list (60 in previous quarter)
>
> ## JIRA activity:
>
> - 49 JIRA tickets created in the last 3 months
> - 24 JIRA tickets closed/resolved in the last 3 months
>
> --
> Ryan Blue
> Software Engineer
> Netflix
>

Fwd: Jira Downtime - Sunday October 8th 00:45 UTC

[Suraj Acharya]

ASF infra has informed us of a scheduled downtime of JIRA.

Suraj
-- Forwarded message --
From: Chris Lambertus 
Date: Fri, Oct 6, 2017 at 10:15 AM
Subject: Re: Jira Downtime - Sunday October 8th 00:45 UTC
To: committ...@apache.org
Cc: ASF Operations , e...@apache.org


Just a reminder of the upcoming downtime for Jira this weekend:



> On Oct 2, 2017, at 5:51 PM, Chris Lambertus  wrote:
>
> Please be advised:
>
>
> Sun, 08 Oct 2017 00:45:00 GMT - Sun, 08 Oct 2017 06:45:00 GMT:
>
> Jira - issues.apache.org will be down for approximately 6 hours while the
database is exported and reloaded to correct a database collation/encoding
issue. This is necessary in preparation for the 7.x upgrade (to be
scheduled soon.)
>
> -Chris
> ASF Infra
>


signature.asc
Description: PGP signature

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

[Suraj Acharya (JIRA)]

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

Suraj Acharya reassigned AVRO-2039:
---

Assignee: Tim Perkins

> Ruby encoding performance improvement
> -
>
> Key: AVRO-2039
> URL: https://issues.apache.org/jira/browse/AVRO-2039
> Project: Avro
>  Issue Type: Improvement
>  Components: ruby
>Reporter: Tim Perkins
>Assignee: Tim Perkins
>Priority: Critical
>
> For a use case with a few levels of nesting and unions in several places 
> within the schema we saw a 5x improvement in encoding performance with these 
> changes to encoding using Ruby.
> 1. Avoid the exhaustive validation of schemas in a union
> 2. Avoid the repeated validation of nested schemas
> https://github.com/apache/avro/pull/230



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (AVRO-2080) Fix Javadoc Warnings in Generated Records

[Suraj Acharya (JIRA)]

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

Suraj Acharya reassigned AVRO-2080:
---

Assignee: Bridger Howell

> Fix Javadoc Warnings in Generated Records
> -
>
> Key: AVRO-2080
> URL: https://issues.apache.org/jira/browse/AVRO-2080
> Project: Avro
>  Issue Type: Bug
>  Components: java
>Affects Versions: 1.8.2
>Reporter: Bridger Howell
>Assignee: Bridger Howell
>Priority: Minor
> Attachments: Test.java
>
>
> I've been seeing a number of javadoc errors for the generated records using 
> the 1.8.2 version of {{SpecificCompiler}}. 
> For example, if I generate code from the following schema:
> {noformat}
> {
> "type":"record",
> "name":"Test",
> "namespace":"foo.bar",
> "fields":[
> {"name":"name","type":"string"}
>  ],
> "version":1
> }
> {noformat}
> And then run the javadoc tool on it, I get the following javadoc warnings:
> {noformat}
> [warn] src_managed/main/Test.java:30: warning: no @return
> [warn]   public static BinaryMessageDecoder getDecoder() {
> [warn]^
> [warn] src_managed/main/Test.java:38: warning: no @return
> [warn]   public static BinaryMessageDecoder createDecoder(SchemaStore 
> resolver) {
> [warn]^
> [warn] src_managed/main/Test.java:43: warning: no @return
> [warn]   public java.nio.ByteBuffer toByteBuffer() throws java.io.IOException 
> {
> [warn]  ^
> [warn] src_managed/main/Test.java:43: warning: no @throws for 
> java.io.IOException
> [warn]   public java.nio.ByteBuffer toByteBuffer() throws java.io.IOException 
> {
> [warn]  ^
> [warn] src_managed/main/Test.java:48: warning: no @param for b
> [warn]   public static Test fromByteBuffer(
> [warn]  ^
> [warn] src_managed/main/Test.java:48: warning: no @return
> [warn]   public static Test fromByteBuffer(
> [warn]  ^
> [warn] src_managed/main/Test.java:48: warning: no @throws for 
> java.io.IOException
> [warn]   public static Test fromByteBuffer(
> [warn]  ^
> {noformat}
> Since this is a simple enough problem, I'll see if I can make a quick patch 
> in a bit.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] Convert to gitbox

[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 bar
> to start is convert our repo to use gitbox. this means the writeable
> repository will be on github and some committer set up will be needed[2]. I
> don't think this got adequately conveyed originally, so I wanted to call it
> out here.
> >
> > Additionally, the infra process for converting to gitbox requires a link
> to a community consensus thread. While I think we already had that back in
> [1], May was a long time ago and some folks might not be watching for
> [DISCUSS] threads.
> >
> > Please vote:
> >
> > +1: we should convert to gitbox and enable pull request merging
> > -1: we should not convert to gitbox because...
> >
> > Vote will be open for at least 72 hours and will be subject to Majority
> Approval (3 or more +1s and more +1s than -1s).
> >
> > [1]: https://s.apache.org/ieB0
> > [2]: Committers will need to flag a github account as theirs via the
> account linking utility:
> > https://gitbox.apache.org/setup/
> >
> > The git-wip repository will also cease, so folks who currently use it
> will need to update their remote url for existing git clones. We can call
> this out in our contribution docs.
> >
>

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

[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
  Components: build
Affects Versions: 1.7.8, 1.9.0, 1.8.3
Reporter: Suraj Acharya
Assignee: Suraj Acharya


{quote}
Hi PMC,

   The Release Distribution Policy[1] changed regarding .sha files.
   See under "Cryptographic Signatures and Checksums Requirements" [2].

  Old policy :

-- use extension .sha for any SHA checksum (SHA-1, SHA-256, SHA-512)

  New policy :

 -- use .sha1 for a SHA-1 checksum
 -- use .sha256 for a SHA-256 checksum
 -- use .sha512 for a SHA-512 checksum
 -- [*] .sha should contain a SHA-1

  Why this change ?

 -- Verifying a checksum under the old policy is/was not handy.
You have to inspect the .sha to find out which algorithm
should be used ; or try them all (SHA-1, SHA256, etc).
The new scheme avoids this ambiguity.
 -- The last point[*] was only added for clarity. Most of the
old, stale .sha's contain a SHA-1. The relatively new .sha's
contain a SHA-512. The expectation is that the last catagory will
disappear, when active projects adapt to the 'new' convention.

  Impact :

 -- Should be none ; many projects already use the 'new' convention.
 -- Please ask your release managers to use .sha1, .sha256, .sha512
instead of the .sha extension.
 -- Please fix your build-tools if you have any.

  Piggyback :

 -- The policy requires a .md5 for every package ;
providing a .sha512 is recommended.
Since MD5 is essentially broken, it is to be expected that
in the future a .sha512 will be required.
Perhaps it is wize to start providing .sha512's
with your releases if you do not already do so.

 -- Visit http://mirror-vm.apache.org/checker/
to check the health of your /dist/-area ;
my stuff ; any feedback is most welcome.

  Thanks ; regards,

  Henk Penning

   [1] http://www.apache.org/dev/release-distribution
   [2] http://www.apache.org/dev/release-distribution#sigs-and-sums


Henk P. Penning ; apache.org infrastructure volunteer.
he...@apache.org ; http://mirror-vm.apache.org/~henkp/
{quote}

We will need to update the build.sh to conform to these activities.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AVRO-2063) C: VERSION, SOVERSION not set correctly for shared library

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-2063:
-

Hey [~edmonds],
Can you make a similar patch on the avro project.
I am pretty sure others will appreciate the fix too.

Thanks

> C: VERSION, SOVERSION not set correctly for shared library
> --
>
> Key: AVRO-2063
> URL: https://issues.apache.org/jira/browse/AVRO-2063
> Project: Avro
>  Issue Type: Bug
>  Components: c
>Affects Versions: 1.8.2
>Reporter: Robert Edmonds
>Priority: Minor
>
> Hi,
> I'm attempting to package avro-c for Debian. While doing so, I noticed that 
> the libavro.so symlink that gets installed points directly to the 
> libavro.so.23.0.0 library file, without an intermediate "libavro.so.23" 
> symlink, and that the SONAME embedded in the library file is set to 
> "libavro.so.23.0.0", rather than "libavro.so.23", which is what I would 
> expect for a library trying to follow the libtool-style current/revision/age 
> scheme on Linux systems.
> It looks like the recommended way to get CMake to produce the typical symlink 
> chain and SONAME is to set the VERSION property to "23.0.0" and the SOVERSION 
> to 23 on the shared library target. See this article for details: 
> http://pusling.com/blog/?p=352.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AVRO-1683) Add microsecond-precision time and timestamp logical type specs

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1683:

Fix Version/s: (was: 1.7.8)

This was a documentation change. The other pieces of information introducing 
the original changes are not present in branch-1.7

> Add microsecond-precision time and timestamp logical type specs
> ---
>
> Key: AVRO-1683
> URL: https://issues.apache.org/jira/browse/AVRO-1683
> Project: Avro
>  Issue Type: Improvement
>  Components: spec
>Reporter: Ryan Blue
>Assignee: Ryan Blue
> Fix For: 1.8.0
>
> Attachments: AVRO-1683-1.patch
>
>
> SQL engines that store data in Avro need to be able to store times and 
> timestamps to meet the SQL spec. For portability, those values should be 
> labelled so other readers can work with the data. I propose adding two new 
> logical types:
> * time-micros: annotates a long, represents the number of microseconds from 
> midnight.
> * timestamp-micros: annotates a long, represents the number of microseconds 
> from the unix epoch.
> Like the other time types, these representations match the ones that were 
> just added to Parquet (PARQUET-200) to make implementations easier.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AVRO-2062) Cherry-pick commits missing.

[Suraj Acharya (JIRA)]

Suraj Acharya created AVRO-2062:
---

 Summary: Cherry-pick commits missing.
 Key: AVRO-2062
 URL: https://issues.apache.org/jira/browse/AVRO-2062
 Project: Avro
  Issue Type: Sub-task
Affects Versions: 1.7.8
Reporter: Suraj Acharya
Assignee: Suraj Acharya
Priority: Blocker
 Fix For: 1.7.8


Missing Cherry-picks :
AVRO-1719
AVRO-1683
AVRO-1656




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (AVRO-2060) Broken links to API documentation on Avro Site

[Suraj Acharya (JIRA)]

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

Suraj Acharya resolved AVRO-2060.
-
Resolution: Fixed

The docs have been refreshed.

> Broken links to API documentation on Avro Site
> --
>
> Key: AVRO-2060
> URL: https://issues.apache.org/jira/browse/AVRO-2060
> Project: Avro
>  Issue Type: Bug
>  Components: build, doc
>Affects Versions: 1.8.2
>    Reporter: Suraj Acharya
>    Assignee: Suraj Acharya
>Priority: Critical
> Fix For: 1.8.2
>
>
> Martin Broadhurst mbroa...@thoughtworks.com via apache.org 
> 12:39 AM (11 hours ago)
>  to dev 
> The links to the current API documentation are broken:
> http://avro.apache.org/docs/current/api/java/index.html
> http://avro.apache.org/docs/current/api/c/index.html
> http://avro.apache.org/docs/current/api/cpp/html/index.html
> http://avro.apache.org/docs/current/api/csharp/index.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (AVRO-2060) Broken links to API documentation on Avro Site

[Suraj Acharya (JIRA)]

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

Suraj Acharya closed AVRO-2060.
---

> Broken links to API documentation on Avro Site
> --
>
> Key: AVRO-2060
> URL: https://issues.apache.org/jira/browse/AVRO-2060
> Project: Avro
>  Issue Type: Bug
>  Components: build, doc
>Affects Versions: 1.8.2
>    Reporter: Suraj Acharya
>    Assignee: Suraj Acharya
>Priority: Critical
> Fix For: 1.8.2
>
>
> Martin Broadhurst mbroa...@thoughtworks.com via apache.org 
> 12:39 AM (11 hours ago)
>  to dev 
> The links to the current API documentation are broken:
> http://avro.apache.org/docs/current/api/java/index.html
> http://avro.apache.org/docs/current/api/c/index.html
> http://avro.apache.org/docs/current/api/cpp/html/index.html
> http://avro.apache.org/docs/current/api/csharp/index.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Broken links to API documentation on Avro Site

[Suraj Acharya]

Thanks a lot for reporting it.
Filed : https://issues.apache.org/jira/browse/AVRO-2060

In the meantime you can use 1.8.1 docs.
http://avro.apache.org/docs/1.8.1/api/java/index.html

Suraj

On Tue, Aug 1, 2017 at 6:06 AM, Gill, John  wrote:

> +1
> Would be great if this was fixed.
>
> - John
>
> On Aug 1, 2017, at 12:40 AM, Martin Broadhurst 
> wrote:
>
> The links to the current API documentation are broken:
> http://avro.apache.org/docs/current/api/java/index.html
> http://avro.apache.org/docs/current/api/c/index.html
> http://avro.apache.org/docs/current/api/cpp/html/index.html
> http://avro.apache.org/docs/current/api/csharp/index.html
>
> Martin Broadhurst
>

[jira] [Created] (AVRO-2060) Broken links to API documentation on Avro Site

[Suraj Acharya (JIRA)]

Suraj Acharya created AVRO-2060:
---

 Summary: Broken links to API documentation on Avro Site
 Key: AVRO-2060
 URL: https://issues.apache.org/jira/browse/AVRO-2060
 Project: Avro
  Issue Type: Bug
  Components: build, doc
Affects Versions: 1.8.2
Reporter: Suraj Acharya
Assignee: Suraj Acharya
Priority: Critical
 Fix For: 1.8.2


Martin Broadhurst mbroa...@thoughtworks.com via apache.org 
12:39 AM (11 hours ago)

 to dev 
The links to the current API documentation are broken:
http://avro.apache.org/docs/current/api/java/index.html
http://avro.apache.org/docs/current/api/c/index.html
http://avro.apache.org/docs/current/api/cpp/html/index.html
http://avro.apache.org/docs/current/api/csharp/index.html





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Discuss regarding upcoming 1.7.8 release for Apache Avro

[suraj acharya]

Just information.
So those scripts didn't work exactly work for me.
I did a manual check and cleaned up a few jiras.
The ones that need a cherry-pick are :

AVRO-1719

AVRO-1683

AVRO-1656


I will do that. And then use that as the base for the release.



Suraj

-Suraj Acharya

On Thu, Jul 20, 2017 at 8:37 AM, Sean Busbey <bus...@cloudera.com> wrote:

> Unfortunately I don't have it as a script.
>
> I have a series of commands I do over in HBase for each release. I wrote
> them down the first time I worked through things over in JIRA:
>
> https://s.apache.org/rJsw
>
> On Thu, Jul 20, 2017 at 12:51 AM, suraj acharya <suraj@gmail.com>
> wrote:
>
> > Hi Sean,
> > Were you able to find the script which will help with this?
> > I think all required changes have been completed and merged on
> branch-1.7.
> >
> > Suraj Acharya
> >
> > -Suraj Acharya
> >
> > On Tue, Jun 13, 2017 at 9:24 AM, Sean Busbey <bus...@cloudera.com>
> wrote:
> >
> > > It would be useful to do a check of what's currently tagged in JIRA as
> > > being in 1.7 but isn't actually in git. I think I have stuff somewhere
> > > for doing this check, let me dig it out.
> > >
> > > On Mon, Jun 12, 2017 at 8:39 PM, Suraj Acharya <su...@apache.org>
> wrote:
> > > > Hi Community,
> > > >
> > > > I am wrapping up the license issue with AVRO 1.7.8 [1]. I will
> shortly
> > > > begin the release for 1.7.8[2].
> > > > If there are any issues you want to see in 1.7.8 and that is not
> > present
> > > in
> > > > the branch-1.7 [3] please comment on the release ticket for 1.7.8[2].
> > > > Backports for a 2-year-old branch are very difficult, cumbersome and
> in
> > > > some cases major changes. I will make an honest effort to backport
> > > changes
> > > > to the branch once comments are made.
> > > > If you know the backport(cherry-pick) won't be clean, please submit a
> > > pull
> > > > request [4] so that it will make the release work a lot easier and
> > > > backports accurate.
> > > >
> > > > If you have any questions feel free to reply to this or open a new
> > > thread.
> > > >
> > > >
> > > > [1] https://issues.apache.org/jira/browse/AVRO-2023
> > > > [2] https://issues.apache.org/jira/browse/AVRO-1998
> > > > [3] https://s.apache.org/avro-branch-1.7
> > > > [4] https://github.com/apache/avro/compare
> > > >
> > > > Suraj Acharya
> > >
> > >
> > >
> > > --
> > > busbey
> > >
> >
>
>
>
> --
> busbey
>

[jira] [Updated] (AVRO-1342) ObjectCreator fails if bad assemblies loaded

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1342:

Fix Version/s: (was: 1.7.8)
   1.7.9

> ObjectCreator fails if bad assemblies loaded
> 
>
> Key: AVRO-1342
> URL: https://issues.apache.org/jira/browse/AVRO-1342
> Project: Avro
>  Issue Type: Bug
>  Components: csharp
>Affects Versions: 1.7.4
> Environment: Windows, Visual Studio
>Reporter: David Taylor
> Fix For: 1.7.9
>
> Attachments: AVRO-1342-csharp-ObjectCreator-fix.patch, 
> continue-on-exception.diff
>
>
> When iterating over the list of assemblies in ObjectCreator.cs the GetTypes() 
> call can fail with an exception if there is a load error on an assembly.  
> Currently this exception is propagated but really does not need to be.  I 
> think a more reasonable approach is to note the error and then try the next 
> assembly. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AVRO-1460) Perl API doesn't raise warning/error when encoding record with spurious fields

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1460:

Fix Version/s: (was: 1.7.8)
   1.7.9

> Perl API doesn't raise warning/error when encoding record with spurious fields
> --
>
> Key: AVRO-1460
> URL: https://issues.apache.org/jira/browse/AVRO-1460
> Project: Avro
>  Issue Type: Improvement
>  Components: perl
>Reporter: John Karp
>Assignee: John Karp
>Priority: Minor
> Fix For: 1.7.9
>
> Attachments: AVRO-1460.patch
>
>
> When serializing a record with a field that isn't specified in the schema, 
> there should be some sort of warning or error. Otherwise, a simple typo in a 
> field name can lead to silent loss of that field's data.
> Test case that should pass but currently fails:
> {noformat}
> {
> my $schema = Avro::Schema->parse(<<EOJ);
>   {
>   "type": "record",
>   "name": "test",
>   "fields" : [
>   {"name": "a", "type": "long"}
>   ]
>   }
> EOJ
> my $enc = '';
> eval {
> Avro::BinaryEncoder->encode(
> schema => $schema,
> data => { a => 27, b => 'foo' },
> emit_cb => sub { $enc .= ${ $_[0] } },
> );
> };
> isa_ok $@, 'Avro::BinaryEncoder::Error';
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AVRO-1463) Undefined values cause warnings when unions with null serialized

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1463:

Fix Version/s: (was: 1.7.8)
   1.7.9

> Undefined values cause warnings when unions with null serialized
> 
>
> Key: AVRO-1463
> URL: https://issues.apache.org/jira/browse/AVRO-1463
> Project: Avro
>  Issue Type: Bug
>  Components: perl
>Reporter: John Karp
>Assignee: John Karp
>Priority: Minor
> Fix For: 1.7.9
>
> Attachments: AVRO-1463.patch
>
>
> This code produces warnings:
> {noformat}
> $enc = '';
> $schema = Avro::Schema->parse(q(["long","null"]));
> Avro::BinaryEncoder->encode(
> schema => $schema,
> data => undef,
> emit_cb => sub { $enc .= ${ $_[0] } },
> );
> {noformat}
> {noformat}
> Use of uninitialized value $data in pack at 
> /home/johnkarp/git/avro/lang/perl/blib/lib/Avro/Schema.pm line 285.
> Use of uninitialized value $data in string eq at 
> /home/johnkarp/git/avro/lang/perl/blib/lib/Avro/Schema.pm line 287.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AVRO-1505) Generic comparator features definable in avro schema

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1505:

Fix Version/s: (was: 1.7.8)

> Generic comparator features definable in avro schema
> 
>
> Key: AVRO-1505
> URL: https://issues.apache.org/jira/browse/AVRO-1505
> Project: Avro
>  Issue Type: New Feature
>  Components: java
>Affects Versions: 1.7.6
> Environment: same as for hadoop 2.3.0
>Reporter: Dr. Martin Menzel
>Priority: Minor
>  Labels: patch
> Attachments: AVRO-1505.patch.gz, CompoundDataExportKeyExtended2.avsc, 
> GenericComparator.java, GenericData.java, TestGenericComparator.java
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> This patch allows to add additional optional comparator informations to the 
> avro schema for record types.
> An example is included in the patch 
> CompoundDataExportKeyExtended2.avsc
> ...snip...
>  {"name": "seqNo", "type": "int",   "comparators" : [
>{ 
> "name":"default",   "compareIdx" : 3, "order":"ascending" }, 
>{ 
> "name":"grouping1", "compareIdx" : 3, "order":"ignore"  } ,
>{ 
> "name":"grouping2", "compareIdx" : 3, "order":"ignore"  } 
>  ]},
> ...snip...
> in the comparators property of a field definition multiple compartor 
> informations can be defined. Often used when defining GroupingCompartors with 
> compound keys is order="ignore" so that the keys are just compared with 
> respect to some special (not ignored fields)
> The necessary changes are made in GenericData class with a fall back to the 
> standard behavior if no comparators are defined.
> An example generic Compartor is delivered with this patch called:
> org.woopi.avro.GenericComparator
> Maybe this class can be included in the avro bundle. In this case the package 
> can be adapted to org.apache.
> The TestCase tests several different situations and is called.
> TestGenericComparator.java



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AVRO-1518) Python client support decimal.Decimal types -> double encoding / decoding

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1518:

Fix Version/s: (was: 1.7.8)
   1.7.9

> Python client support decimal.Decimal types -> double encoding / decoding
> -
>
> Key: AVRO-1518
> URL: https://issues.apache.org/jira/browse/AVRO-1518
> Project: Avro
>  Issue Type: Improvement
>Reporter: Scott Reynolds
>Assignee: Scott Reynolds
> Fix For: 1.7.9
>
>
> Python standard library > 2.4 provides a Decimal type that has much better 
> semantics then standard binary float. Avro library should be able to accept 
> Decimal's and encode them as doubles.
> (https://docs.python.org/2/library/decimal.html)
> I also believe it should, by default, turn Avro double's into Decimal object 
> instead of a float.
> Simple patch allows for encoding a Decimal into an Avro double
> {code}
> --- io.py 2014-05-23 13:41:14.0 -0700
> +++ /Users/sreynolds/Projects/avro-1.7.6 2/src/avro/io.py 2014-05-23 
> 13:44:03.0 -0700
> @@ -46,6 +46,11 @@ try:
>  except ImportError:
>   import simplejson as json
> +try:
> +from decimal import Decimal
> +except ImportError:
> +Decimal = float
> +
>  #
>  # Constants
>  #
> @@ -117,7 +122,7 @@ def validate(expected_schema, datum):
>  and LONG_MIN_VALUE <= datum <= LONG_MAX_VALUE)
>elif schema_type in ['float', 'double']:
>  return (isinstance(datum, int) or isinstance(datum, long)
> -or isinstance(datum, float))
> +or isinstance(datum, float) or instance(datum, Decimal))
>elif schema_type == 'fixed':
>  return isinstance(datum, str) and len(datum) == expected_schema.size
>elif schema_type == 'enum':
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AVRO-1517) Unicode strings are accepted as bytes and fixed type by perl API

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1517:

Fix Version/s: (was: 1.7.8)
   1.7.9

> Unicode strings are accepted as bytes and fixed type by perl API
> 
>
> Key: AVRO-1517
> URL: https://issues.apache.org/jira/browse/AVRO-1517
> Project: Avro
>  Issue Type: Bug
>  Components: perl
>Reporter: John Karp
>Assignee: John Karp
> Fix For: 1.7.9
>
> Attachments: AVRO-1517.patch
>
>
> By default in perl, a string is a sequence of bytes, values 0-255. However, 
> if a Unicode character is included that cannot be represented with a single 
> byte, the string gets 'upgraded' to a non-byte-based Unicode string allowing 
> ordinals outside that range. When string operations are done with byte and 
> non-byte Unicode strings, the result is always non-byte, with the byte string 
> first 'upgraded'. Upgrading consists of utf8 encoding and setting a utf8 flag 
> on the string. ('utf8' is a variant of UTF-8 used by perl)
> The perl Avro API is accepting these Unicode strings as-is for the 'bytes' 
> type. This is a problem because 1) values >255 are not valid as bytes, and 
> any encoding is their job. 2) As Avro assembles the serialized data, perl 
> 'upgrades' all the data, having the effect of utf8 encoding our serialized 
> binary data.
> The correct behavior is for the Avro perl API is to attempt to downgrade the 
> string, and if this fails because of contained values >255 then to raise an 
> error. (The behavior of 'string' won't change, it will still take Unicode 
> strings as expected.)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AVRO-1523) Perl API: int/long type minimum value checks are off by one

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1523:

Fix Version/s: (was: 1.7.8)
   1.7.9

> Perl API: int/long type minimum value checks are off by one
> ---
>
> Key: AVRO-1523
> URL: https://issues.apache.org/jira/browse/AVRO-1523
> Project: Avro
>  Issue Type: Bug
>  Components: perl
>Reporter: John Karp
>Assignee: John Karp
>Priority: Minor
> Fix For: 1.7.9
>
> Attachments: AVRO-1523.patch
>
>
> -2,147,483,648 is rejected as an int, and −9,223,372,036,854,775,808 is 
> rejected as a long when passed to the binary encoder, but they are valid 
> signed 32-bit and 64-bit numbers respectively.
> The problem is that the range check is made against the absolute value of the 
> input, but in two's complement arithmetic types the minimum and maximum 
> values have different absolute values.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AVRO-1527) support bzip2 in python avro tool

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1527:

Fix Version/s: (was: 1.7.8)
   1.7.9

> support bzip2 in python avro tool
> -
>
> Key: AVRO-1527
> URL: https://issues.apache.org/jira/browse/AVRO-1527
> Project: Avro
>  Issue Type: Improvement
>Affects Versions: 1.7.6
>Reporter: Eustache
>Priority: Minor
>  Labels: avro, bzip2, python
> Fix For: 1.7.9
>
> Attachments: AVRO-1527.diff
>
>
> The python tool to decode avro files is missing bzip2 support.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AVRO-1556) csharp PrimitiveSchema loses custom properties in WriteJson/ToString

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1556:

Fix Version/s: (was: 1.7.8)
   1.7.9

> csharp PrimitiveSchema loses custom properties in WriteJson/ToString
> 
>
> Key: AVRO-1556
> URL: https://issues.apache.org/jira/browse/AVRO-1556
> Project: Avro
>  Issue Type: Bug
>  Components: csharp
>Affects Versions: 1.7.7
>Reporter: Dmitry Kovalev
>Assignee: Dmitry Kovalev
> Fix For: 1.7.9
>
> Attachments: AVRO-1556-csharp-primitiveschema-fix.patch
>
>
> PrimitiveSchema class overrides WriteJson method to handle a shotrcut where 
> primitive type is given as a literal, but in doing so it ignores teh case 
> where there are custom properties attached to it. 
> This breaks any functionality which relies on the equality of the schema 
> re-parsed from its ToString/WriteJson output, one example being csharp 
> codegen.
> Example:
> { "type": "string", "logicalType":"DateTimeInstant", 
> "logicalEncoding":"ISO8601-datetime-offset" }
> becomes "type" : "string"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AVRO-1608) Deprecate mutator methods on Schema

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1608:

Fix Version/s: (was: 1.7.8)
   1.7.9

> Deprecate mutator methods on Schema
> ---
>
> Key: AVRO-1608
> URL: https://issues.apache.org/jira/browse/AVRO-1608
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.7.7
>Reporter: Tom White
>Assignee: Tom White
> Fix For: 1.7.9
>
> Attachments: AVRO-1608.patch, AVRO-1608.patch
>
>
> This is a follow on to AVRO-261. It would be good to deprecate 
> JsonProperties#addProp, Schema#addAlias, and Schema.Field#addAlias, and 
> remove them in 1.8.0. Instead users should use SchemaBuilder, or we could 
> also provide overloaded variants of the factory methods on Schema to specify 
> properties and aliases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AVRO-2020) Update BUILD instructions with correct versions for language-specific libraries

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-2020:

Fix Version/s: (was: 1.7.8)
   1.7.9

> Update BUILD instructions with correct versions for language-specific 
> libraries
> ---
>
> Key: AVRO-2020
> URL: https://issues.apache.org/jira/browse/AVRO-2020
> Project: Avro
>  Issue Type: Task
>  Components: community, doc
>Affects Versions: 1.7.7, 1.8.1, 1.9.0
>Reporter: Sean Busbey
>Priority: Critical
> Fix For: 1.9.0, 1.8.3, 1.7.9
>
>
> our BUILD instructions current list a few things I know are wrong (Ruby 1.8 
> support) and some things I'm pretty sure are wrong (Java 1.6 support).
> we should do a pass checking all the languages.
> {code}
> REQUIREMENTS
> The following packages must be installed before Avro can be built:
>  - Java: JDK 1.6, Maven 2 or better, protobuf-compile
>  - PHP: php5, phpunit, php5-gmp
>  - Python: 2.5 or greater, python-setuptools for dist target
>  - C: gcc, cmake, asciidoc, source-highlight
>  - C++: cmake 2.8.4 or greater, g++, flex, bison, libboost-dev
>  - C#: mono-devel mono-gmcs nunit
>  - JavaScript: nodejs, npm
>  - Ruby: ruby 1.86 or greater, ruby-dev, gem, rake, echoe, yajl-ruby
>  - Perl: perl 5.8.1 or greater, gmake, Module::Install,
>Module::Install::ReadmeFromPod, Module::Install::Repository,
>Math::BigInt, JSON::XS, Try::Tiny, Regexp::Common, Encode,
>IO::String, Object::Tiny, Compress::ZLib, Test::More,
>Test::Exception, Test::Pod
>  - Apache Ant 1.7
>  - Apache Forrest 0.8 (for documentation)
>  - md5sum, sha1sum, used by top-level dist target
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Drop hadoop1 support in Avro 1.9

[suraj acharya]

Yeah may be subtasks.
But please make sure all of the dependencies are updated before even one is
merged in.
We dont want to be in a situation where the dependency still exists for one
of the other languages.

Thanks again for taking on this effort

-Suraj Acharya

On Fri, Jul 28, 2017 at 12:33 AM, Gabor Szadovszky <ga...@apache.org> wrote:

> Created the issue AVRO-2059
> <https://issues.apache.org/jira/browse/AVRO-2059> to track it.
> I can do it for java but I guess, we have to do some update in the other
> languages as well. Shall I create subtasks for all the langs?
>
> On Thu, Jul 27, 2017 at 10:01 PM, Sean Busbey <bus...@cloudera.com> wrote:
>
> > +1 sounds great. We can let user@avro know about the plan once we have
> the
> > change in place, so there's still time if someone has a compelling reason
> > staying on Avro 1.7 or 1.8 can't work for hadoop1 folks.
> >
> > On Thu, Jul 27, 2017 at 12:52 AM, Gabor Szadovszky <ga...@apache.org>
> > wrote:
> >
> > > Hi All,
> > >
> > > It has already appeared in some discussions/code reviews that we might
> > not
> > > want to support hadoop1 anymore. As it would be a breaking change I
> would
> > > suggest removing the hadoop1 support in the next major release 1.9.0.
> > > What do you think?
> > >
> > > Cheers,
> > > Gabor
> > >
> >
> >
> >
> > --
> > busbey
> >
>

[jira] [Commented] (AVRO-1741) Python 3 code should check if avro.codec is None before decoding

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-1741:
-

Seems like the patch has been merged.
Any reason this is still in Patch Available state?


> Python 3 code should check if avro.codec is None before decoding
> 
>
> Key: AVRO-1741
> URL: https://issues.apache.org/jira/browse/AVRO-1741
> Project: Avro
>  Issue Type: Bug
>Reporter: Matthew Hayes
>Assignee: Matthew Hayes
> Fix For: 1.7.7
>
> Attachments: AVRO-1741.diff
>
>
> I'm getting the error below when trying to read an Avro file in Python 3.  
> FWIW, I generated this Avro file from Pig.  I don't know if that makes a 
> difference.
> {code}
> avro.datafile.DataFileReader(open("test.avro","rb"),avro.io.DatumReader())
> Traceback (most recent call last):
>   File "", line 1, in 
>   File 
> "/Users/mhayes/.pyenv/versions/3.4.2/lib/python3.4/site-packages/avro/datafile.py",
>  line 352, in __init__
> self.codec = self.GetMeta('avro.codec').decode('utf-8')
> AttributeError: 'NoneType' object has no attribute 'decode'
> {code}
> It appears the problem is in the following code.  It should check if GetMeta 
> returns None before trying to decode it.  The Python 2 code doesn't have this 
> problem because it is already decoded.
> {code}
> # ensure codec is valid
> self.codec = self.GetMeta('avro.codec').decode('utf-8')
> if self.codec is None:
>   self.codec = "null"
> if self.codec not in VALID_CODECS:
>   raise DataFileException('Unknown codec: %s.' % self.codec)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AVRO-2040) Fix Ruby 2.4 deprecation notices

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-2040:

Fix Version/s: 1.9.0

> Fix Ruby 2.4 deprecation notices 
> -
>
> Key: AVRO-2040
> URL: https://issues.apache.org/jira/browse/AVRO-2040
> Project: Avro
>  Issue Type: Improvement
>Reporter: Tim Perkins
>Assignee: Tim Perkins
>Priority: Minor
> Fix For: 1.9.0
>
>
> https://github.com/apache/avro/pull/231



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (AVRO-2040) Fix Ruby 2.4 deprecation notices

[Suraj Acharya (JIRA)]

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

Suraj Acharya reassigned AVRO-2040:
---

Assignee: Tim Perkins

> Fix Ruby 2.4 deprecation notices 
> -
>
> Key: AVRO-2040
> URL: https://issues.apache.org/jira/browse/AVRO-2040
> Project: Avro
>  Issue Type: Improvement
>Reporter: Tim Perkins
>Assignee: Tim Perkins
>Priority: Minor
>
> https://github.com/apache/avro/pull/231



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AVRO-2055) Remove Magic Value From org.apache.avro.hadoop.io.AvroSequenceFile

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-2055:
-

+1.
LGTM

> Remove Magic Value From org.apache.avro.hadoop.io.AvroSequenceFile
> --
>
> Key: AVRO-2055
> URL: https://issues.apache.org/jira/browse/AVRO-2055
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.7.7, 1.8.2
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Trivial
> Attachments: AVRO-2055.1.patch
>
>
> Remove magic string _io.file.buffer.size_ and _DEFAULT_BUFFER_SIZE_BYTES_ and 
> instead rely on the Hadoop libraries to provide this information.  Will help 
> to keep Avro in sync with changes in Hadoop.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AVRO-2048) Avro Binary Decoding - Gracefully Handle Long Strings

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-2048:
-

Seems like the code is not passing checkstyle.
The artifacts are present here: 
https://builds.apache.org/job/PreCommit-AVRO-Build-TEST/32/artifact/component/patchprocess/test--lang_java.txt

The value is {{0l}}. Change it to {{0L}} and it should pass.

{code}

[INFO] 
[INFO] --- maven-checkstyle-plugin:2.17:check (checkstyle-check) @ avro ---
[INFO] Starting audit...
/testptch/avro/lang/java/avro/src/main/java/org/apache/avro/io/BinaryDecoder.java:263:19:
 error: Should use uppercase 'L'.
/testptch/avro/lang/java/avro/src/main/java/org/apache/avro/io/BinaryDecoder.java:268:10:
 error: Should use uppercase 'L'.
Audit done.
[INFO] There are 2 errors reported by Checkstyle 6.11.2 with checkstyle.xml 
ruleset.
[ERROR] src/main/java/org/apache/avro/io/BinaryDecoder.java:[263,19] (misc) 
UpperEll: Should use uppercase 'L'.
[ERROR] src/main/java/org/apache/avro/io/BinaryDecoder.java:[268,10] (misc) 
UpperEll: Should use uppercase 'L'.

{code}



> Avro Binary Decoding - Gracefully Handle Long Strings
> -
>
> Key: AVRO-2048
> URL: https://issues.apache.org/jira/browse/AVRO-2048
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.7.7, 1.8.2
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Minor
> Attachments: AVRO-2048.1.patch
>
>
> According to the 
> [specs|https://avro.apache.org/docs/1.8.2/spec.html#binary_encode_primitive]:
> bq. a string is encoded as a *long* followed by that many bytes of UTF-8 
> encoded character data.
> However, that is currently not being adhered to:
> {code:title=org.apache.avro.io.BinaryDecoder}
>   @Override
>   public Utf8 readString(Utf8 old) throws IOException {
> int length = readInt();
> Utf8 result = (old != null ? old : new Utf8());
> result.setByteLength(length);
> if (0 != length) {
>   doReadBytes(result.getBytes(), 0, length);
> }
> return result;
>   }
> {code}
> The first thing the code does here is to load an *int* value, not a *long*.  
> Because of the variable length nature of the size, this will mostly work.  
> However, there may be edge-cases where the serializer is putting in large 
> length values erroneously or nefariously. Let us gracefully detect such 
> scenarios and more closely adhere to the spec.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AVRO-2054) Use StringBuilder instead of StringBuffer

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-2054:
-

Thanks for the patch [~belugabehr].

Only one comment :
* Can you change the variable from {{buffer}} to {{builder}}. It makes the 
consistency better.

> Use StringBuilder instead of StringBuffer
> -
>
> Key: AVRO-2054
> URL: https://issues.apache.org/jira/browse/AVRO-2054
> Project: Avro
>  Issue Type: Improvement
>Affects Versions: 1.7.7, 1.8.2
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Trivial
> Attachments: AVRO-2054.1.patch
>
>
> Use the un-synchronized StringBuilder instead of StringBuffer.  Use _char_ 
> values instead of Strings.
> {code:title=org.apache.trevni.MetaData}
>   @Override public String toString() {
> StringBuffer buffer = new StringBuffer();
> buffer.append("{ ");
> for (Map.Entry<String,byte[]> e : entrySet()) {
>   buffer.append(e.getKey());
>   buffer.append("=");
>   try {
> buffer.append(new String(e.getValue(), "ISO-8859-1"));
>   } catch (java.io.UnsupportedEncodingException error) {
> throw new TrevniRuntimeException(error);
>   }
>   buffer.append(" ");
> }
> buffer.append("}");
> return buffer.toString();
>   }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AVRO-2041) set up gitbox integration

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-2041:
-

[~busbey] lets start with the simple feature of pull requests.
We can always expand to others.
If everything looks good to you, I would recommend that we file the ticket with 
Infra as Chris mentioned.

> set up gitbox integration
> -
>
> Key: AVRO-2041
> URL: https://issues.apache.org/jira/browse/AVRO-2041
> Project: Avro
>  Issue Type: Task
>  Components: community
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>
> We got consensus back in may about [turning on gitbox 
> integration|https://lists.apache.org/thread.html/cdd8ba14c1bf8aca2d71d09862e9780f2dc46af414ed78b1e3fd9c56@%3Cdev.avro.apache.org%3E]
>  so do it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Discuss regarding upcoming 1.7.8 release for Apache Avro

[suraj acharya]

Hi Sean,
Were you able to find the script which will help with this?
I think all required changes have been completed and merged on branch-1.7.

Suraj Acharya

-Suraj Acharya

On Tue, Jun 13, 2017 at 9:24 AM, Sean Busbey <bus...@cloudera.com> wrote:

> It would be useful to do a check of what's currently tagged in JIRA as
> being in 1.7 but isn't actually in git. I think I have stuff somewhere
> for doing this check, let me dig it out.
>
> On Mon, Jun 12, 2017 at 8:39 PM, Suraj Acharya <su...@apache.org> wrote:
> > Hi Community,
> >
> > I am wrapping up the license issue with AVRO 1.7.8 [1]. I will shortly
> > begin the release for 1.7.8[2].
> > If there are any issues you want to see in 1.7.8 and that is not present
> in
> > the branch-1.7 [3] please comment on the release ticket for 1.7.8[2].
> > Backports for a 2-year-old branch are very difficult, cumbersome and in
> > some cases major changes. I will make an honest effort to backport
> changes
> > to the branch once comments are made.
> > If you know the backport(cherry-pick) won't be clean, please submit a
> pull
> > request [4] so that it will make the release work a lot easier and
> > backports accurate.
> >
> > If you have any questions feel free to reply to this or open a new
> thread.
> >
> >
> > [1] https://issues.apache.org/jira/browse/AVRO-2023
> > [2] https://issues.apache.org/jira/browse/AVRO-1998
> > [3] https://s.apache.org/avro-branch-1.7
> > [4] https://github.com/apache/avro/compare
> >
> > Suraj Acharya
>
>
>
> --
> busbey
>

[jira] [Commented] (AVRO-1998) Make a release for 1.7.8

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-1998:
-

[~radai] sorry for the delayed response. 
I do not want to backport the change to branch 1.7 because it is a backwards 
incompatible change and will break the contract of not pushing backwards 
incompatible change into a maintenance release.
If someone is able to backport it without making it incompatible in behaviour 
then I would be okay with it. 

> Make a release for 1.7.8
> 
>
> Key: AVRO-1998
> URL: https://issues.apache.org/jira/browse/AVRO-1998
> Project: Avro
>  Issue Type: Task
>  Components: community
>Affects Versions: 1.7.7
>    Reporter: Suraj Acharya
>
> There have been quite a few issues fixed in a 1.7 branch since 1.7.7.
> Here is a list of all the issues present in the 1.7.X branch 
> [Jira Filter | 
> https://issues.apache.org/jira/browse/AVRO-1489?jql=project%20%3D%20AVRO%20AND%20fixVersion%20%3D%201.7.8%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC]
> I would appreciate if people who need the release can help out with the 
> patches currently present so we can merge those and get an updated 1.7.8 
> release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AVRO-2023) backport and update license fixes for branch-1.7

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-2023:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Change set has been merged.

> backport and update license fixes for branch-1.7
> 
>
> Key: AVRO-2023
> URL: https://issues.apache.org/jira/browse/AVRO-2023
> Project: Avro
>  Issue Type: Task
>  Components: build, community
>Affects Versions: 1.7.7
>Reporter: Sean Busbey
>    Assignee: Suraj Acharya
>Priority: Blocker
> Fix For: 1.7.8
>
>
> Backport the changes from AVRO-1722 and subtasks, ensure they're applicable 
> for branch-1.7.
> git history as summary:
> {code}
> $ git hist --grep AVRO-1722 --grep AVRO-1727 --grep AVRO-1728 --grep 
> AVRO-1729 --grep AVRO-1730 --grep AVRO-1731 --grep AVRO-1732 --grep AVRO-1733 
> --grep AVRO-1734 --grep AVRO-1735 --grep AVRO-1736 --grep AVRO-1771 
> origin/branch-1.8
> * 059e6df - AVRO-1771. Add LICENSE and NOTICE to avro-doc artifact. 
> Contributed by blue. (1 year, 3 months ago)
> * ee28a20 - AVRO-1728: Java: Add LICENSE and NOTICE files to jars. (1 year, 4 
> months ago)
> * 80ba788 - AVRO-1722 ADDENDUM: Add last license doc changes, rat helper. (1 
> year, 4 months ago)
> * bf751df - AVRO-1722 ADDENDUM: Java: Fix tests broken by adding licenses. (1 
> year, 4 months ago)
> * f49b2d3 - AVRO-1722: Update root LICENSE.txt and NOTICE.txt. (1 year, 4 
> months ago)
> * 2c6c570 - AVRO-1730: Python3: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * e11c588 - AVRO-1730: Python: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * ada69ac - AVRO-1736: PHP: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * 96d2d35 - AVRO-1735: Perl: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * df5c513 - AVRO-1731: C: Add LICENSE and NOTICE to binary distribution. (1 
> year, 4 months ago)
> * 3585c45 - AVRO-1733: C#: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * 5cb83db - AVRO-1732: C++: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * bc19e3a - AVRO-1729: Ruby: Add LICENSE and NOTICE to ruby gems. (1 year, 6 
> months ago)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-1485:
-

* The tests on the master failed. Not sure what the reason for the same is. 
* The other two issues seem to be due to the presence of tabs in the xml file. 
But the rest of the code also has tabs in it. So i guess there is not much to 
worry about this -1 from the bot.

> Specification says Record field type can be record name but implementation 
> allows any named type.
> -
>
> Key: AVRO-1485
> URL: https://issues.apache.org/jira/browse/AVRO-1485
> Project: Avro
>  Issue Type: Bug
>  Components: java, spec
>Affects Versions: 1.7.6
>Reporter: Sean Busbey
>Assignee: Nandor Kollar
> Attachments: AVRO-1485_1.patch
>
>
> The [specification for Record 
> fields|http://avro.apache.org/docs/1.7.6/spec.html#schema_record] says that 
> the type is
> bq. A JSON object defining a schema, or a JSON string naming a record 
> definition (required).
> AFAICT, the Java implementation allows for any [named 
> type|http://avro.apache.org/docs/1.7.6/spec.html#Names].
> The specification should be updated to state any named type is allowed or the 
> Java implementation should restrict what can be used. The former seems less 
> likely to disturb current users.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Suraj Acharya (JIRA)]

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

Suraj Acharya reassigned AVRO-2050:
---

Assignee: BELUGA BEHR

> Clear Array To Allow GC
> ---
>
> Key: AVRO-2050
> URL: https://issues.apache.org/jira/browse/AVRO-2050
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.7.7, 1.8.2
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Minor
> Attachments: AVRO-2050.1.patch, AVRO-2050.2.patch
>
>
> Java's {{ArrayList}} implementation clears all Objects from the internal 
> buffer when the {{clear()}} method is called.  This allows the Objects to be 
> free for GC.  We should do the same in Avro 
> {{org.apache.avro.generic.GenericData}} 
> [ArrayList 
> Source|http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/8u40-b25/java/util/ArrayList.java#ArrayList.clear%28%29]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Suraj Acharya (JIRA)]

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

Suraj Acharya reassigned AVRO-2049:
---

Assignee: BELUGA BEHR

> Remove Superfluous Configuration From AvroSerializer
> 
>
> Key: AVRO-2049
> URL: https://issues.apache.org/jira/browse/AVRO-2049
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.7.7, 1.8.2
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Trivial
> Attachments: AVRO-2049.1.patch, AVRO-2049.2.patch
>
>
> In the class {{org.apache.avro.hadoop.io.AvroSerializer}}, we see that the 
> Avro block size is configured with a hard-coded value and there is a request 
> to benchmark different buffer sizes.
> {code:title=org.apache.avro.hadoop.io.AvroSerializer}
>   /**
>* The block size for the Avro encoder.
>*
>* This number was copied from the AvroSerialization of 
> org.apache.avro.mapred in Avro 1.5.1.
>*
>* TODO(gwu): Do some benchmarking with different numbers here to see if it 
> is important.
>*/
>   private static final int AVRO_ENCODER_BLOCK_SIZE_BYTES = 512;
>   /** An factory for creating Avro datum encoders. */
>   private static EncoderFactory mEncoderFactory
>   = new 
> EncoderFactory().configureBlockSize(AVRO_ENCODER_BLOCK_SIZE_BYTES);
> {code}
> However, there is no need to benchmark, this setting is superfluous and is 
> ignored with the current implementation.
> {code:title=org.apache.avro.hadoop.io.AvroSerializer}
>   @Override
>   public void open(OutputStream outputStream) throws IOException {
> mOutputStream = outputStream;
> mAvroEncoder = mEncoderFactory.binaryEncoder(outputStream, mAvroEncoder);
>   }
> {code}
> {{org.apache.avro.io.EncoderFactory.binaryEncoder}} ignores this setting.  
> This setting is only relevant for calls to 
> {{org.apache.avro.io.EncoderFactory.blockingBinaryEncoder}} 
>  which considers the configured "Block Size" for doing binary encoding of 
> blocked Array types as laid out in the 
> [specs|https://avro.apache.org/docs/1.8.2/spec.html#binary_encode_complex].  
> It can simply be removed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-2021:
-

LGTM Thanks [~nkollar]

> uuid logical type is not documented
> ---
>
> Key: AVRO-2021
> URL: https://issues.apache.org/jira/browse/AVRO-2021
> Project: Avro
>  Issue Type: Improvement
>Reporter: Andrew Rosca
>Assignee: Nandor Kollar
>Priority: Minor
> Attachments: AVRO-2021_1.patch
>
>
> The documentation does not mention anything about the _uuid_ logical type, 
> which is in fact implemented in LogicalTypes.java.
> Add documentation for _uuid_



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [Announce] Release of Avro-1.8.2

[Suraj Acharya]

Thanks.
I will look into it in the next few days and try to submit a patch.
In the meantime if someone else has time feel free to update that value.

Thanks once again

Suraj

On Tue, Jun 20, 2017 at 4:34 PM, Gill, John <john.g...@teradata.com> wrote:

> Suraj,
> It looks like the following file just need to be updated with the 1.8.2
> version:
> https://github.com/Homebrew/homebrew-core/blob/master/Formula/avro-c.rb
>
> - John
>
> -Original Message-
> From: Suraj Acharya <su...@apache.org>
> Reply-To: "dev@avro.apache.org" <dev@avro.apache.org>
> Date: Tuesday, June 20, 2017 at 10:47 AM
> To: "dev@avro.apache.org" <dev@avro.apache.org>
> Subject: Re: [Announce] Release of Avro-1.8.2
>
> I have no idea about the Brew install.
> If anyone has any idea please let me know, I will surely try to release it
> there.
> It's highly likely someone just uploaded it on their own.
>
> Suraj
>
>
> On Jun 19, 2017 12:08 PM, "Gill, John" <john.g...@teradata.com> wrote:
>
> Who does the homebrew maintenance when new releases are made? It seems that
> the avro-c library is still the 1.8.1 code base. Would be nice if this was
> updated.
>
> - John
>
> -Original Message-
> From: suraj acharya <suraj@gmail.com>
> Reply-To: "dev@avro.apache.org" <dev@avro.apache.org>
> Date: Thursday, June 1, 2017 at 11:23 AM
> To: "dev@avro.apache.org" <dev@avro.apache.org>
> Subject: Re: [Announce] Release of Avro-1.8.2
>
> Like Sean mentioned, changing the fixed version will help correcting the
> Release Notes.
> Once, we have some amount of fixes in, we can start making releases on a
> cadence.
>
> S
>
>
> -Suraj Acharya
>
> On Thu, Jun 1, 2017 at 10:47 AM, Sean Busbey <bus...@cloudera.com> wrote:
>
> > Update the jira to not have 1.8.2 in the fix versions. If we want to
> > get the changes in the 1.8 release line, I'd recommend reopening the
> > issues and cherry-picking to branch-1.8 then setting 1.8.3 as a fix
> > version.
> >
> > On Thu, Jun 1, 2017 at 4:20 AM, Niels Basjes <ni...@basjes.nl> wrote:
> > > Hi,
> > >
> > > I know now that while fixing the bugs I should have committed them to
> > both
> > > the master and the 1.8 branch instead of 'just the master'.
> > > Just diffing the change log of master and the 1.8 branch shows that
> this
> > > mistake is made quite a large number of times and in both directions.
> > >
> > > As a consequence the release notes (obviously based on the Jira tags)
> > shows
> > > many bugs/changes that are not present in the release.
> > >
> > > How do we fix this properly?
> > >
> > > Niels Basjes
> > >
> > >
> > > On Thu, Jun 1, 2017 at 3:55 AM, Suraj Acharya <su...@apache.org>
> wrote:
> > >
> > >> It gives me great pleasure to announce the release of Avro 1.8.2!
> > >>
> > >>
> > >> Changes are listed at: https://s.apache.org/avro-release-note-1.8.2
> > >>
> > >>
> > >> This release can be downloaded from:
> > >> https://www.apache.org/dyn/closer.cgi/avro/
> > >>
> > >>
> > >> Java artifacts are available from Maven Central, Ruby artifacts are at
> > >> RubyGems, Python is at PyPI, JS at NPM.
> > >>
> > >>
> > >> Thanks to everyone for contributing and helping out.
> > >>
> > >>
> > >> Suraj Acharya
> > >>
> > >
> > >
> > >
> > > --
> > > Best regards / Met vriendelijke groeten,
> > >
> > > Niels Basjes
> >
> >
> >
> > --
> > busbey
> >
>
>
>

Re: [Announce] Release of Avro-1.8.2

[Suraj Acharya]

I have no idea about the Brew install.
If anyone has any idea please let me know, I will surely try to release it
there.
It's highly likely someone just uploaded it on their own.

Suraj


On Jun 19, 2017 12:08 PM, "Gill, John" <john.g...@teradata.com> wrote:

Who does the homebrew maintenance when new releases are made? It seems that
the avro-c library is still the 1.8.1 code base. Would be nice if this was
updated.

- John

-Original Message-----
From: suraj acharya <suraj@gmail.com>
Reply-To: "dev@avro.apache.org" <dev@avro.apache.org>
Date: Thursday, June 1, 2017 at 11:23 AM
To: "dev@avro.apache.org" <dev@avro.apache.org>
Subject: Re: [Announce] Release of Avro-1.8.2

Like Sean mentioned, changing the fixed version will help correcting the
Release Notes.
Once, we have some amount of fixes in, we can start making releases on a
cadence.

S


-Suraj Acharya

On Thu, Jun 1, 2017 at 10:47 AM, Sean Busbey <bus...@cloudera.com> wrote:

> Update the jira to not have 1.8.2 in the fix versions. If we want to
> get the changes in the 1.8 release line, I'd recommend reopening the
> issues and cherry-picking to branch-1.8 then setting 1.8.3 as a fix
> version.
>
> On Thu, Jun 1, 2017 at 4:20 AM, Niels Basjes <ni...@basjes.nl> wrote:
> > Hi,
> >
> > I know now that while fixing the bugs I should have committed them to
> both
> > the master and the 1.8 branch instead of 'just the master'.
> > Just diffing the change log of master and the 1.8 branch shows that this
> > mistake is made quite a large number of times and in both directions.
> >
> > As a consequence the release notes (obviously based on the Jira tags)
> shows
> > many bugs/changes that are not present in the release.
> >
> > How do we fix this properly?
> >
> > Niels Basjes
> >
> >
> > On Thu, Jun 1, 2017 at 3:55 AM, Suraj Acharya <su...@apache.org> wrote:
> >
> >> It gives me great pleasure to announce the release of Avro 1.8.2!
> >>
> >>
> >> Changes are listed at: https://s.apache.org/avro-release-note-1.8.2
> >>
> >>
> >> This release can be downloaded from:
> >> https://www.apache.org/dyn/closer.cgi/avro/
> >>
> >>
> >> Java artifacts are available from Maven Central, Ruby artifacts are at
> >> RubyGems, Python is at PyPI, JS at NPM.
> >>
> >>
> >> Thanks to everyone for contributing and helping out.
> >>
> >>
> >> Suraj Acharya
> >>
> >
> >
> >
> > --
> > Best regards / Met vriendelijke groeten,
> >
> > Niels Basjes
>
>
>
> --
> busbey
>

[jira] [Assigned] (AVRO-2023) backport and update license fixes for branch-1.7

[Suraj Acharya (JIRA)]

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

Suraj Acharya reassigned AVRO-2023:
---

Assignee: Suraj Acharya

> backport and update license fixes for branch-1.7
> 
>
> Key: AVRO-2023
> URL: https://issues.apache.org/jira/browse/AVRO-2023
> Project: Avro
>  Issue Type: Task
>  Components: build, community
>Affects Versions: 1.7.7
>Reporter: Sean Busbey
>    Assignee: Suraj Acharya
>Priority: Blocker
> Fix For: 1.7.8
>
>
> Backport the changes from AVRO-1722 and subtasks, ensure they're applicable 
> for branch-1.7.
> git history as summary:
> {code}
> $ git hist --grep AVRO-1722 --grep AVRO-1727 --grep AVRO-1728 --grep 
> AVRO-1729 --grep AVRO-1730 --grep AVRO-1731 --grep AVRO-1732 --grep AVRO-1733 
> --grep AVRO-1734 --grep AVRO-1735 --grep AVRO-1736 --grep AVRO-1771 
> origin/branch-1.8
> * 059e6df - AVRO-1771. Add LICENSE and NOTICE to avro-doc artifact. 
> Contributed by blue. (1 year, 3 months ago)
> * ee28a20 - AVRO-1728: Java: Add LICENSE and NOTICE files to jars. (1 year, 4 
> months ago)
> * 80ba788 - AVRO-1722 ADDENDUM: Add last license doc changes, rat helper. (1 
> year, 4 months ago)
> * bf751df - AVRO-1722 ADDENDUM: Java: Fix tests broken by adding licenses. (1 
> year, 4 months ago)
> * f49b2d3 - AVRO-1722: Update root LICENSE.txt and NOTICE.txt. (1 year, 4 
> months ago)
> * 2c6c570 - AVRO-1730: Python3: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * e11c588 - AVRO-1730: Python: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * ada69ac - AVRO-1736: PHP: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * 96d2d35 - AVRO-1735: Perl: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * df5c513 - AVRO-1731: C: Add LICENSE and NOTICE to binary distribution. (1 
> year, 4 months ago)
> * 3585c45 - AVRO-1733: C#: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * 5cb83db - AVRO-1732: C++: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * bc19e3a - AVRO-1729: Ruby: Add LICENSE and NOTICE to ruby gems. (1 year, 6 
> months ago)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AVRO-2023) backport and update license fixes for branch-1.7

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-2023:
-

protovis-r3.2.js : BSD license.
g.bar.js : MIT licesne. Will add those to the exclude list.
Squash the commits and merge it in.

> backport and update license fixes for branch-1.7
> 
>
> Key: AVRO-2023
> URL: https://issues.apache.org/jira/browse/AVRO-2023
> Project: Avro
>  Issue Type: Task
>  Components: build, community
>Affects Versions: 1.7.7
>Reporter: Sean Busbey
>Priority: Blocker
> Fix For: 1.7.8
>
>
> Backport the changes from AVRO-1722 and subtasks, ensure they're applicable 
> for branch-1.7.
> git history as summary:
> {code}
> $ git hist --grep AVRO-1722 --grep AVRO-1727 --grep AVRO-1728 --grep 
> AVRO-1729 --grep AVRO-1730 --grep AVRO-1731 --grep AVRO-1732 --grep AVRO-1733 
> --grep AVRO-1734 --grep AVRO-1735 --grep AVRO-1736 --grep AVRO-1771 
> origin/branch-1.8
> * 059e6df - AVRO-1771. Add LICENSE and NOTICE to avro-doc artifact. 
> Contributed by blue. (1 year, 3 months ago)
> * ee28a20 - AVRO-1728: Java: Add LICENSE and NOTICE files to jars. (1 year, 4 
> months ago)
> * 80ba788 - AVRO-1722 ADDENDUM: Add last license doc changes, rat helper. (1 
> year, 4 months ago)
> * bf751df - AVRO-1722 ADDENDUM: Java: Fix tests broken by adding licenses. (1 
> year, 4 months ago)
> * f49b2d3 - AVRO-1722: Update root LICENSE.txt and NOTICE.txt. (1 year, 4 
> months ago)
> * 2c6c570 - AVRO-1730: Python3: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * e11c588 - AVRO-1730: Python: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * ada69ac - AVRO-1736: PHP: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * 96d2d35 - AVRO-1735: Perl: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * df5c513 - AVRO-1731: C: Add LICENSE and NOTICE to binary distribution. (1 
> year, 4 months ago)
> * 3585c45 - AVRO-1733: C#: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * 5cb83db - AVRO-1732: C++: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * bc19e3a - AVRO-1729: Ruby: Add LICENSE and NOTICE to ruby gems. (1 year, 6 
> months ago)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Discuss regarding upcoming 1.7.8 release for Apache Avro

[Suraj Acharya]

Hi Community,

I am wrapping up the license issue with AVRO 1.7.8 [1]. I will shortly
begin the release for 1.7.8[2].
If there are any issues you want to see in 1.7.8 and that is not present in
the branch-1.7 [3] please comment on the release ticket for 1.7.8[2].
Backports for a 2-year-old branch are very difficult, cumbersome and in
some cases major changes. I will make an honest effort to backport changes
to the branch once comments are made.
If you know the backport(cherry-pick) won't be clean, please submit a pull
request [4] so that it will make the release work a lot easier and
backports accurate.

If you have any questions feel free to reply to this or open a new thread.


[1] https://issues.apache.org/jira/browse/AVRO-2023
[2] https://issues.apache.org/jira/browse/AVRO-1998
[3] https://s.apache.org/avro-branch-1.7
[4] https://github.com/apache/avro/compare

Suraj Acharya

[jira] [Resolved] (AVRO-1885) Release 1.8.2

[Suraj Acharya (JIRA)]

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

Suraj Acharya resolved AVRO-1885.
-
Resolution: Fixed

The release has been completed successfully.

> Release 1.8.2
> -
>
> Key: AVRO-1885
> URL: https://issues.apache.org/jira/browse/AVRO-1885
> Project: Avro
>  Issue Type: Task
>  Components: community
>Affects Versions: 1.8.2
>Reporter: Sean Busbey
>    Assignee: Suraj Acharya
> Fix For: 1.8.2
>
>
> Please link to any issues that should be considered blockers for the 1.8.2 
> release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Closing out issues for the release.

[suraj acharya]

I am not sure.
It was one of those steps on the guide.
It is the only one left for me to finish.

-Suraj Acharya

On Mon, Jun 5, 2017 at 4:50 PM, Sean Busbey <bus...@cloudera.com> wrote:

> what do we gain by marking them closed instead of leaving them resolved?
>
> On Sun, Jun 4, 2017 at 8:30 PM, Suraj Acharya <su...@apache.org> wrote:
> > As part of the release. I am to close all issues marked resolved in
> 1.8.2.
> > However, a few have been back ported to 1.7.8 and a few are on
> > master(1.9.0).
> > So i want to know if there is a better to close jira's marked as fixed in
> > 1.8.2 only, other than going through each one of them and closing them
> > manually?
> >
> > Thanks
> >
> > S
>
>
>
> --
> busbey
>

Closing out issues for the release.

[Suraj Acharya]

As part of the release. I am to close all issues marked resolved in 1.8.2.
However, a few have been back ported to 1.7.8 and a few are on
master(1.9.0).
So i want to know if there is a better to close jira's marked as fixed in
1.8.2 only, other than going through each one of them and closing them
manually?

Thanks

S

[jira] [Updated] (AVRO-2027) Merge fix for data file corruption, when using Python3, avro-python3 and the snappy codec.

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-2027:

Status: Patch Available  (was: Open)

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

> Merge fix for data file corruption, when using Python3, avro-python3 and the 
> snappy codec.
> --
>
> Key: AVRO-2027
> URL: https://issues.apache.org/jira/browse/AVRO-2027
> Project: Avro
>  Issue Type: Bug
>  Components: python
>Affects Versions: 1.8.1
>Reporter: Zahary Karadjov
>Assignee: Zahary Karadjov
>
> A complete description of the issue is provided in the Github pull request 
> here:
> https://github.com/apache/avro/pull/220



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (AVRO-2027) Merge fix for data file corruption, when using Python3, avro-python3 and the snappy codec.

[Suraj Acharya (JIRA)]

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

Suraj Acharya reassigned AVRO-2027:
---

Assignee: Zahary Karadjov

> Merge fix for data file corruption, when using Python3, avro-python3 and the 
> snappy codec.
> --
>
> Key: AVRO-2027
> URL: https://issues.apache.org/jira/browse/AVRO-2027
> Project: Avro
>  Issue Type: Bug
>  Components: python
>Affects Versions: 1.8.1
>Reporter: Zahary Karadjov
>Assignee: Zahary Karadjov
>
> A complete description of the issue is provided in the Github pull request 
> here:
> https://github.com/apache/avro/pull/220



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [Announce] Release of Avro-1.8.2

[suraj acharya]

Like Sean mentioned, changing the fixed version will help correcting the
Release Notes.
Once, we have some amount of fixes in, we can start making releases on a
cadence.

S


-Suraj Acharya

On Thu, Jun 1, 2017 at 10:47 AM, Sean Busbey <bus...@cloudera.com> wrote:

> Update the jira to not have 1.8.2 in the fix versions. If we want to
> get the changes in the 1.8 release line, I'd recommend reopening the
> issues and cherry-picking to branch-1.8 then setting 1.8.3 as a fix
> version.
>
> On Thu, Jun 1, 2017 at 4:20 AM, Niels Basjes <ni...@basjes.nl> wrote:
> > Hi,
> >
> > I know now that while fixing the bugs I should have committed them to
> both
> > the master and the 1.8 branch instead of 'just the master'.
> > Just diffing the change log of master and the 1.8 branch shows that this
> > mistake is made quite a large number of times and in both directions.
> >
> > As a consequence the release notes (obviously based on the Jira tags)
> shows
> > many bugs/changes that are not present in the release.
> >
> > How do we fix this properly?
> >
> > Niels Basjes
> >
> >
> > On Thu, Jun 1, 2017 at 3:55 AM, Suraj Acharya <su...@apache.org> wrote:
> >
> >> It gives me great pleasure to announce the release of Avro 1.8.2!
> >>
> >>
> >> Changes are listed at: https://s.apache.org/avro-release-note-1.8.2
> >>
> >>
> >> This release can be downloaded from:
> >> https://www.apache.org/dyn/closer.cgi/avro/
> >>
> >>
> >> Java artifacts are available from Maven Central, Ruby artifacts are at
> >> RubyGems, Python is at PyPI, JS at NPM.
> >>
> >>
> >> Thanks to everyone for contributing and helping out.
> >>
> >>
> >> Suraj Acharya
> >>
> >
> >
> >
> > --
> > Best regards / Met vriendelijke groeten,
> >
> > Niels Basjes
>
>
>
> --
> busbey
>

[jira] [Updated] (AVRO-2038) Update the build.xml in doc to strip of any whitespace / new line

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-2038:

   Resolution: Fixed
Fix Version/s: 1.8.3
   1.9.0
   Status: Resolved  (was: Patch Available)

Thanks [~rawduh] for the patch.

> Update the build.xml in doc to strip of any whitespace / new line
> -
>
> Key: AVRO-2038
> URL: https://issues.apache.org/jira/browse/AVRO-2038
> Project: Avro
>  Issue Type: Improvement
>  Components: build, doc
>    Reporter: Suraj Acharya
>Assignee: Rodrigo Coelho
> Fix For: 1.9.0, 1.8.3
>
>
> Currently the build.xml present in the doc folder does not strip the 
> whitespace/newline.
> That needs to be removed so the build scripts build correctly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[Announce] Release of Avro-1.8.2

[Suraj Acharya]

It gives me great pleasure to announce the release of Avro 1.8.2!


Changes are listed at: https://s.apache.org/avro-release-note-1.8.2


This release can be downloaded from:
https://www.apache.org/dyn/closer.cgi/avro/


Java artifacts are available from Maven Central, Ruby artifacts are at
RubyGems, Python is at PyPI, JS at NPM.


Thanks to everyone for contributing and helping out.


Suraj Acharya

[jira] [Assigned] (AVRO-2038) Update the build.xml in doc to strip of any whitespace / new line

[Suraj Acharya (JIRA)]

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

Suraj Acharya reassigned AVRO-2038:
---

Assignee: Rodrigo Coelho  (was: Suraj Acharya)

> Update the build.xml in doc to strip of any whitespace / new line
> -
>
> Key: AVRO-2038
> URL: https://issues.apache.org/jira/browse/AVRO-2038
> Project: Avro
>  Issue Type: Improvement
>  Components: build, doc
>    Reporter: Suraj Acharya
>Assignee: Rodrigo Coelho
>
> Currently the build.xml present in the doc folder does not strip the 
> whitespace/newline.
> That needs to be removed so the build scripts build correctly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AVRO-2038) Update the build.xml in doc to strip of any whitespace / new line

[Suraj Acharya (JIRA)]

Suraj Acharya created AVRO-2038:
---

 Summary: Update the build.xml in doc to strip of any whitespace / 
new line
 Key: AVRO-2038
 URL: https://issues.apache.org/jira/browse/AVRO-2038
 Project: Avro
  Issue Type: Improvement
  Components: build, doc
Reporter: Suraj Acharya
Assignee: Suraj Acharya


Currently the build.xml present in the doc folder does not strip the 
whitespace/newline.
That needs to be removed so the build scripts build correctly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Help with the website release.

[Suraj Acharya]

Hey guys,
I am trying to work on the release.
However, the docs for 1.8.2 are not getting pushed. Does anyone have
experience with it, or does anyone have some ideas on what are the next
steps are to push the 1.8.2 docs?

Currently, the link on the website is broken and I am trying to look into
it.

Step 13 of this guide is where I am stuck :
https://cwiki.apache.org/confluence/display/AVRO/How+To+Release

S

[jira] [Updated] (AVRO-1885) Release 1.8.2

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1885:

Fix Version/s: (was: 1.8.3)
   1.8.2

> Release 1.8.2
> -
>
> Key: AVRO-1885
> URL: https://issues.apache.org/jira/browse/AVRO-1885
> Project: Avro
>  Issue Type: Task
>  Components: community
>Affects Versions: 1.8.2
>Reporter: Sean Busbey
>    Assignee: Suraj Acharya
> Fix For: 1.8.2
>
>
> Please link to any issues that should be considered blockers for the 1.8.2 
> release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Work started] (AVRO-1885) Release 1.8.2

[Suraj Acharya (JIRA)]

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

Work on AVRO-1885 started by Suraj Acharya.
---
> Release 1.8.2
> -
>
> Key: AVRO-1885
> URL: https://issues.apache.org/jira/browse/AVRO-1885
> Project: Avro
>  Issue Type: Task
>  Components: community
>Affects Versions: 1.8.2
>Reporter: Sean Busbey
>    Assignee: Suraj Acharya
> Fix For: 1.8.2
>
>
> Please link to any issues that should be considered blockers for the 1.8.2 
> release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AVRO-1862) AvroOutputFormat saves compressed avrò files without respecting codec's default extension

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1862:

Fix Version/s: (was: 1.8.2)
   1.8.3

> AvroOutputFormat saves compressed avrò files without respecting codec's 
> default extension
> -
>
> Key: AVRO-1862
> URL: https://issues.apache.org/jira/browse/AVRO-1862
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.8.1
>Reporter: Piotr Wikieł
>Priority: Minor
>  Labels: patch
> Fix For: 1.8.3
>
> Attachments: AVRO-1862-1.patch, AVRO-1862.patch
>
>
> Common pattern in naming compressed files is giving them extension derived 
> from compression codec, for example: {{.gz}}, {{.zip}}, {{.bz2}}. 
> {{AvroOutputFormat}} currently does not respect this convention. 
> I've adapted some code from Hadoop's {{TextOutputFormat}} in 
> backward-compatible manner adding following {{JobConf}} property:
> {{avro.mapred.output.extension.from-codec}} ({{boolean}}, default: {{false}}) 
> - when set to {{true}}, extension will be changed according to above rule.
> EDIT: Please take a look at first comment for an update. {{.gz.avro}}, 
> {{.snappy.avro}} will be an extension of the file when above property will be 
> set to true.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1965:

Fix Version/s: (was: 1.8.2)
   1.8.3

> Reparsing an existing schema mutates the schema
> ---
>
> Key: AVRO-1965
> URL: https://issues.apache.org/jira/browse/AVRO-1965
> Project: Avro
>  Issue Type: Bug
>  Components: java
>Affects Versions: 1.8.1
>Reporter: David Maughan
>Assignee: Doug Cutting
> Fix For: 1.8.3
>
> Attachments: AVRO-1965.patch
>
>
> h2. Overview
> In certain scenarios re-parsing a schema constructed via {{SchemaBuilder}} or 
> {{Schema.createRecord}} produces a schema that is no longer equal to the 
> original. In the below example, after parsing the existing schema, the 
> namespace of the top level record is cascaded down to the bottom level 
> record. Note that the way the top level record is being created with the 
> namespace as part of the name {{default.a}} is the same way Hive's 
> {{AvroSerDe}} constructs a schema from a Hive table's metadata.
> h2. Failing test case
> {code}
> Schema d = SchemaBuilder.builder().intType();
> Schema c = 
> SchemaBuilder.record("c").fields().name("d").type(d).noDefault().endRecord();
> Schema b = 
> SchemaBuilder.record("b").fields().name("c").type(c).noDefault().endRecord();
> Schema a1 = 
> SchemaBuilder.record("default.a").fields().name("b").type(b).noDefault().endRecord();
> Schema a2 = new Schema.Parser().parse(a1.toString());
> // a1 = 
> {"type":"record","name":"a","namespace":"default","fields":[{"name":"b","type":{"type":"record","name":"b","namespace":"","fields":[{"name":"c","type":{"type":"record","name":"c","fields":[{"name":"d","type":"int"}]}}]}}]}
> // a2 = 
> {"type":"record","name":"a","namespace":"default","fields":[{"name":"b","type":{"type":"record","name":"b","namespace":"","fields":[{"name":"c","type":{"type":"record","name":"c","namespace":"default","fields":[{"name":"d","type":"int"}]}}]}}]}
> assertThat(a2, is(a1));
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1957:

Fix Version/s: (was: 1.8.2)
   1.8.3

> TimeConversions do not implement getRecommendedSchema()
> ---
>
> Key: AVRO-1957
> URL: https://issues.apache.org/jira/browse/AVRO-1957
> Project: Avro
>  Issue Type: Bug
>Affects Versions: 1.8.1
>Reporter: Sean Timm
>Assignee: Sean Timm
> Fix For: 1.8.3
>
>
> org.apache.avro.data.TimeConversions.TimestampConversion and other date and 
> time conversions do not implement getRecommendedSchema(). When trying to 
> dynamically generate an Avro schema from a pojo that contains a DateTime 
> object using ReflectData, I get an unsupported operation exception.
> I think the implementation should be as simple as
> {code}
> @Override
> public Schema getRecommendedSchema() {
>   return 
> LogicalTypes.timestampMillis().addToSchema(Schema.create(Schema.Type.LONG));
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AVRO-2008) change the error module to be thread-safe on Windows as well as on UNIX

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-2008:

Fix Version/s: (was: 1.8.2)
   1.8.3

> change the error module to be thread-safe on Windows as well as on UNIX
> ---
>
> Key: AVRO-2008
> URL: https://issues.apache.org/jira/browse/AVRO-2008
> Project: Avro
>  Issue Type: Improvement
>  Components: c
>Affects Versions: 1.8.1
>Reporter: Eliyahu Machluf
>Assignee: Eliyahu Machluf
> Fix For: 1.8.3
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AVRO-1885) Release 1.8.2

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-1885:

Fix Version/s: (was: 1.8.2)
   1.8.3

> Release 1.8.2
> -
>
> Key: AVRO-1885
> URL: https://issues.apache.org/jira/browse/AVRO-1885
> Project: Avro
>  Issue Type: Task
>  Components: community
>Affects Versions: 1.8.2
>Reporter: Sean Busbey
>    Assignee: Suraj Acharya
> Fix For: 1.8.3
>
>
> Please link to any issues that should be considered blockers for the 1.8.2 
> release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AVRO-2026) Incorporate valgrind memory testing for C

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-2026:

Fix Version/s: (was: 1.8.2)
   1.8.3

> Incorporate valgrind memory testing for C
> -
>
> Key: AVRO-2026
> URL: https://issues.apache.org/jira/browse/AVRO-2026
> Project: Avro
>  Issue Type: Improvement
>  Components: c
>Reporter: John Gill
> Fix For: 1.8.3
>
> Attachments: AVRO-2026.patch
>
>
> With the work done for AVRO-1167 & AVRO-766 in identifying memory leaks 
> decided to make it a standard part of the testing framework. This issue  
> requires https://github.com/apache/avro/pull/218 otherwise test_avro_schema 
> and test_avro_values fail due to to avro_schema_copy calls.
> Adding valgrind tool to the docker container
> Adding valgrind to CMakeLists.txt to optionally do valgrind testing if the 
> tool is found
> Cleaning up existing tests that were failing due to not properly cleaning up 
> memory
> Lastly, as part of ./build.sh test for lang/c do not remove the build/c 
> directory. The memcheck output is kept so that memory leak issues can be 
> reviewed and addressed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (AVRO-1885) Release 1.8.2

[Suraj Acharya (JIRA)]

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

Suraj Acharya reassigned AVRO-1885:
---

Assignee: Suraj Acharya  (was: Ryan Blue)

> Release 1.8.2
> -
>
> Key: AVRO-1885
> URL: https://issues.apache.org/jira/browse/AVRO-1885
> Project: Avro
>  Issue Type: Task
>  Components: community
>Affects Versions: 1.8.2
>Reporter: Sean Busbey
>    Assignee: Suraj Acharya
> Fix For: 1.8.2
>
>
> Please link to any issues that should be considered blockers for the 1.8.2 
> release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] Release Apache Avro 1.8.2 RC4

[Suraj Acharya]

Thanks a lot for the verification. The voting on this is now closed.
The RC has now passed, with the minimum required votes.
Vote Count :
6 Votes +1.
4 Binding Votes.

I will now begin with process of releasing the artifacts.

I will send out another email with the official download links.

Suraj Acharya


On Wed, May 10, 2017 at 11:52 PM, Harsha Chintalapani <a...@harsha.io>
wrote:

> +1
> Verified artifacts.
> Unit tests passed
> tested the Java Avro.
>
> Thanks,
> Harsha
>
> On Wed, May 10, 2017 at 11:38 AM Ryan Blue <rb...@netflix.com.invalid>
> wrote:
>
> > That's the one I was looking at, I think it should be fine for just that
> > one to be published.
> >
> > On Wed, May 10, 2017 at 11:36 AM, Suraj Acharya <su...@apache.org>
> wrote:
> >
> > > So I have looked at the reason why there have been two repositories
> > > present. Looks like it was a maven issue.
> > > I will be using
> > > https://repository.apache.org/content/repositories/orgapacheavro-1014
> to
> > > publish.
> > >
> > > S
> > >
> > > On Wed, May 10, 2017 at 11:38 AM, Ryan Blue <rb...@netflix.com.invalid
> >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Everything looks good, other than the extra maven repo. Would just
> the
> > > one
> > > > with all the artifacts get published?
> > > >
> > > > On Wed, May 10, 2017 at 4:58 AM, Niels Basjes <ni...@basjes.nl>
> wrote:
> > > >
> > > > > Downloaded source, ran build test and rat checks.
> > > > > Everything passed
> > > > >
> > > > > +1
> > > > >
> > > > > On Wed, May 10, 2017 at 12:18 AM, Doug Cutting <cutt...@gmail.com>
> > > > wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > Downloaded source, verified checksum.  All tests passed on Ubuntu
> > > > 16.04.
> > > > > >
> > > > > > Doug
> > > > > >
> > > > > > On Mon, May 8, 2017 at 7:23 PM, Suraj Acharya <su...@apache.org>
> > > > wrote:
> > > > > > > Hi everyone,
> > > > > > >
> > > > > > > I propose the following RC to be released as official Apache
> Avro
> > > > 1.8.2
> > > > > > > release.
> > > > > > >
> > > > > > > The commit id is 7f2b8dda4be515a3d1f0b60d5175ee500dbe16e2
> > > > > > >
> > > > > > > * This corresponds to the tag: release-1.8.2-rc4
> > > > > > > * https://s.apache.org/avro-1.8.2-rc4
> > > > > > >
> > > > > > > The release tarball, signature, and checksums are here:
> > > > > > > * https://dist.apache.org/repos/dist/dev/avro/avro-1.8.2-rc4/
> > > > > > >
> > > > > > > You can find the KEYS file here:
> > > > > > > * https://dist.apache.org/repos/dist/release/avro/KEYS
> > > > > > >
> > > > > > > Binary artifacts for Java are staged in Nexus here:
> > > > > > > * https://repository.apache.org/content/repositories/
> > > > > orgapacheavro-1013
> > > > > > > * https://repository.apache.org/content/repositories/
> > > > > orgapacheavro-1014
> > > > > > >
> > > > > > > This release includes:
> > > > > > > * A spec for single-message Avro encoding and a Java
> > implementation
> > > > > > > * Java: Bug fixes for Java logical types
> > > > > > > * Java: Support for Decimal with specific classes
> > > > > > > * Ruby: A fix for compatibility when using snappy
> > > > > > > * Python 3: Updated to use the standard module-level logging
> > > pattern
> > > > > > > * C++: Support for Boost >= 1.59
> > > > > > > * And more bug fixes...
> > > > > > >
> > > > > > > Please download, verify, and test. This vote will remain open
> for
> > > at
> > > > > > least
> > > > > > > 72 hours. Given sufficient votes, I would like to close it on
> or
> > > > about
> > > > > > 9AM
> > > > > > > CDT on Sunday, 14 May 2017.
> > > > > > >
> > > > > > > [ ] +1 Release this as Apache Avro 1.8.2
> > > > > > > [ ] +0
> > > > > > > [ ] -1 Do not release this because...
> > > > > > >
> > > > > > > --
> > > > > > > Suraj Acharya
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best regards / Met vriendelijke groeten,
> > > > >
> > > > > Niels Basjes
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Ryan Blue
> > > > Software Engineer
> > > > Netflix
> > > >
> > >
> >
> >
> >
> > --
> > Ryan Blue
> > Software Engineer
> > Netflix
> >
>

Re: [VOTE] Release Apache Avro 1.8.2 RC4

[Suraj Acharya]

So I have looked at the reason why there have been two repositories
present. Looks like it was a maven issue.
I will be using
https://repository.apache.org/content/repositories/orgapacheavro-1014 to
publish.

S

On Wed, May 10, 2017 at 11:38 AM, Ryan Blue <rb...@netflix.com.invalid>
wrote:

> +1
>
> Everything looks good, other than the extra maven repo. Would just the one
> with all the artifacts get published?
>
> On Wed, May 10, 2017 at 4:58 AM, Niels Basjes <ni...@basjes.nl> wrote:
>
> > Downloaded source, ran build test and rat checks.
> > Everything passed
> >
> > +1
> >
> > On Wed, May 10, 2017 at 12:18 AM, Doug Cutting <cutt...@gmail.com>
> wrote:
> >
> > > +1
> > >
> > > Downloaded source, verified checksum.  All tests passed on Ubuntu
> 16.04.
> > >
> > > Doug
> > >
> > > On Mon, May 8, 2017 at 7:23 PM, Suraj Acharya <su...@apache.org>
> wrote:
> > > > Hi everyone,
> > > >
> > > > I propose the following RC to be released as official Apache Avro
> 1.8.2
> > > > release.
> > > >
> > > > The commit id is 7f2b8dda4be515a3d1f0b60d5175ee500dbe16e2
> > > >
> > > > * This corresponds to the tag: release-1.8.2-rc4
> > > > * https://s.apache.org/avro-1.8.2-rc4
> > > >
> > > > The release tarball, signature, and checksums are here:
> > > > * https://dist.apache.org/repos/dist/dev/avro/avro-1.8.2-rc4/
> > > >
> > > > You can find the KEYS file here:
> > > > * https://dist.apache.org/repos/dist/release/avro/KEYS
> > > >
> > > > Binary artifacts for Java are staged in Nexus here:
> > > > * https://repository.apache.org/content/repositories/
> > orgapacheavro-1013
> > > > * https://repository.apache.org/content/repositories/
> > orgapacheavro-1014
> > > >
> > > > This release includes:
> > > > * A spec for single-message Avro encoding and a Java implementation
> > > > * Java: Bug fixes for Java logical types
> > > > * Java: Support for Decimal with specific classes
> > > > * Ruby: A fix for compatibility when using snappy
> > > > * Python 3: Updated to use the standard module-level logging pattern
> > > > * C++: Support for Boost >= 1.59
> > > > * And more bug fixes...
> > > >
> > > > Please download, verify, and test. This vote will remain open for at
> > > least
> > > > 72 hours. Given sufficient votes, I would like to close it on or
> about
> > > 9AM
> > > > CDT on Sunday, 14 May 2017.
> > > >
> > > > [ ] +1 Release this as Apache Avro 1.8.2
> > > > [ ] +0
> > > > [ ] -1 Do not release this because...
> > > >
> > > > --
> > > > Suraj Acharya
> > >
> >
> >
> >
> > --
> > Best regards / Met vriendelijke groeten,
> >
> > Niels Basjes
> >
>
>
>
> --
> Ryan Blue
> Software Engineer
> Netflix
>

Re: [VOTE] Release Apache Avro 1.8.2 RC4

[Suraj Acharya]

+1 on the release candidate. (Binding)
Downloaded the tar, ran tests and checked the md5sum.

When I tried to untar on my MacOSX, there was an error of a missing file.
The problem seemed to be local to MacOSX and was not seen on my Linux box.
It was the same issue seen in the released 1.8.1 tarball. I dont believe
that is an issue.


Suraj Acharya

On Mon, May 8, 2017 at 9:23 PM, Suraj Acharya <su...@apache.org> wrote:

> Hi everyone,
>
> I propose the following RC to be released as official Apache Avro 1.8.2
> release.
>
> The commit id is 7f2b8dda4be515a3d1f0b60d5175ee500dbe16e2
>
> * This corresponds to the tag: release-1.8.2-rc4
> * https://s.apache.org/avro-1.8.2-rc4
>
> The release tarball, signature, and checksums are here:
> * https://dist.apache.org/repos/dist/dev/avro/avro-1.8.2-rc4/
>
> You can find the KEYS file here:
> * https://dist.apache.org/repos/dist/release/avro/KEYS
>
> Binary artifacts for Java are staged in Nexus here:
> * https://repository.apache.org/content/repositories/orgapacheavro-1013
> * https://repository.apache.org/content/repositories/orgapacheavro-1014
>
> This release includes:
> * A spec for single-message Avro encoding and a Java implementation
> * Java: Bug fixes for Java logical types
> * Java: Support for Decimal with specific classes
> * Ruby: A fix for compatibility when using snappy
> * Python 3: Updated to use the standard module-level logging pattern
> * C++: Support for Boost >= 1.59
> * And more bug fixes...
>
> Please download, verify, and test. This vote will remain open for at least
> 72 hours. Given sufficient votes, I would like to close it on or about 9AM
> CDT on Sunday, 14 May 2017.
>
> [ ] +1 Release this as Apache Avro 1.8.2
> [ ] +0
> [ ] -1 Do not release this because...
>
> --
> Suraj Acharya
>

[VOTE] Release Apache Avro 1.8.2 RC4

[Suraj Acharya]

Hi everyone,

I propose the following RC to be released as official Apache Avro 1.8.2
release.

The commit id is 7f2b8dda4be515a3d1f0b60d5175ee500dbe16e2

* This corresponds to the tag: release-1.8.2-rc4
* https://s.apache.org/avro-1.8.2-rc4

The release tarball, signature, and checksums are here:
* https://dist.apache.org/repos/dist/dev/avro/avro-1.8.2-rc4/

You can find the KEYS file here:
* https://dist.apache.org/repos/dist/release/avro/KEYS

Binary artifacts for Java are staged in Nexus here:
* https://repository.apache.org/content/repositories/orgapacheavro-1013
* https://repository.apache.org/content/repositories/orgapacheavro-1014

This release includes:
* A spec for single-message Avro encoding and a Java implementation
* Java: Bug fixes for Java logical types
* Java: Support for Decimal with specific classes
* Ruby: A fix for compatibility when using snappy
* Python 3: Updated to use the standard module-level logging pattern
* C++: Support for Boost >= 1.59
* And more bug fixes...

Please download, verify, and test. This vote will remain open for at least
72 hours. Given sufficient votes, I would like to close it on or about 9AM
CDT on Sunday, 14 May 2017.

[ ] +1 Release this as Apache Avro 1.8.2
[ ] +0
[ ] -1 Do not release this because...

--
Suraj Acharya

Re: [DISCUSS] turn on gitbox and prioritize github contributions?

[suraj acharya]

1) Yes I agree on using the GitHub for code review.
2) And if we wish to actively encourage it, we would need to update our
contribution wiki.
3) Also, I dont want to stop people from submitting patches, so for the
time being I would say lets keep both running.
4) I would say, lets continue to use JIRA. We have significant history
present here. Moving to issues might need to fine-tune the workflow out
there.

S

-Suraj Acharya

On Fri, May 5, 2017 at 11:35 AM, Sean Busbey <bus...@cloudera.com> wrote:

> Hi folks!
>
> Infra now offers read/write access to github via a service called
> 'gitbox'[1]. PMCs have the option to join the service and then make
> use of whichever github features they want.
>
> Personally, I find PR management via the github interface way faster
> than other options. In particular, since it has a usable mobile
> interface I'm able to use commute time to do reviews via it.
>
> What do folks think about
>
> 1) opting in generally
>
> 2) using github PRs directly
>
> 3) actively encouraging our community to switch to github PRs
>
> 4) using github issues
>
>
> [1]: https://gitbox.apache.org/
>
> --
> busbey
>

[jira] [Commented] (AVRO-2023) backport and update license fixes for branch-1.7

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-2023:
-

I have tried to fix the licensing issues.
I have created a pull request here : https://github.com/apache/avro/pull/222.

Can you guys make sure it looks good?
Also, I am not sure about those .js files in the java project.

> backport and update license fixes for branch-1.7
> 
>
> Key: AVRO-2023
> URL: https://issues.apache.org/jira/browse/AVRO-2023
> Project: Avro
>  Issue Type: Task
>  Components: build, community
>Affects Versions: 1.7.7
>Reporter: Sean Busbey
>Priority: Blocker
> Fix For: 1.7.8
>
>
> Backport the changes from AVRO-1722 and subtasks, ensure they're applicable 
> for branch-1.7.
> git history as summary:
> {code}
> $ git hist --grep AVRO-1722 --grep AVRO-1727 --grep AVRO-1728 --grep 
> AVRO-1729 --grep AVRO-1730 --grep AVRO-1731 --grep AVRO-1732 --grep AVRO-1733 
> --grep AVRO-1734 --grep AVRO-1735 --grep AVRO-1736 --grep AVRO-1771 
> origin/branch-1.8
> * 059e6df - AVRO-1771. Add LICENSE and NOTICE to avro-doc artifact. 
> Contributed by blue. (1 year, 3 months ago)
> * ee28a20 - AVRO-1728: Java: Add LICENSE and NOTICE files to jars. (1 year, 4 
> months ago)
> * 80ba788 - AVRO-1722 ADDENDUM: Add last license doc changes, rat helper. (1 
> year, 4 months ago)
> * bf751df - AVRO-1722 ADDENDUM: Java: Fix tests broken by adding licenses. (1 
> year, 4 months ago)
> * f49b2d3 - AVRO-1722: Update root LICENSE.txt and NOTICE.txt. (1 year, 4 
> months ago)
> * 2c6c570 - AVRO-1730: Python3: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * e11c588 - AVRO-1730: Python: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * ada69ac - AVRO-1736: PHP: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * 96d2d35 - AVRO-1735: Perl: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * df5c513 - AVRO-1731: C: Add LICENSE and NOTICE to binary distribution. (1 
> year, 4 months ago)
> * 3585c45 - AVRO-1733: C#: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * 5cb83db - AVRO-1732: C++: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * bc19e3a - AVRO-1729: Ruby: Add LICENSE and NOTICE to ruby gems. (1 year, 6 
> months ago)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AVRO-2023) backport and update license fixes for branch-1.7

[Suraj Acharya (JIRA)]

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

Suraj Acharya updated AVRO-2023:

Status: Patch Available  (was: Open)

> backport and update license fixes for branch-1.7
> 
>
> Key: AVRO-2023
> URL: https://issues.apache.org/jira/browse/AVRO-2023
> Project: Avro
>  Issue Type: Task
>  Components: build, community
>Affects Versions: 1.7.7
>Reporter: Sean Busbey
>Priority: Blocker
> Fix For: 1.7.8
>
>
> Backport the changes from AVRO-1722 and subtasks, ensure they're applicable 
> for branch-1.7.
> git history as summary:
> {code}
> $ git hist --grep AVRO-1722 --grep AVRO-1727 --grep AVRO-1728 --grep 
> AVRO-1729 --grep AVRO-1730 --grep AVRO-1731 --grep AVRO-1732 --grep AVRO-1733 
> --grep AVRO-1734 --grep AVRO-1735 --grep AVRO-1736 --grep AVRO-1771 
> origin/branch-1.8
> * 059e6df - AVRO-1771. Add LICENSE and NOTICE to avro-doc artifact. 
> Contributed by blue. (1 year, 3 months ago)
> * ee28a20 - AVRO-1728: Java: Add LICENSE and NOTICE files to jars. (1 year, 4 
> months ago)
> * 80ba788 - AVRO-1722 ADDENDUM: Add last license doc changes, rat helper. (1 
> year, 4 months ago)
> * bf751df - AVRO-1722 ADDENDUM: Java: Fix tests broken by adding licenses. (1 
> year, 4 months ago)
> * f49b2d3 - AVRO-1722: Update root LICENSE.txt and NOTICE.txt. (1 year, 4 
> months ago)
> * 2c6c570 - AVRO-1730: Python3: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * e11c588 - AVRO-1730: Python: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * ada69ac - AVRO-1736: PHP: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * 96d2d35 - AVRO-1735: Perl: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * df5c513 - AVRO-1731: C: Add LICENSE and NOTICE to binary distribution. (1 
> year, 4 months ago)
> * 3585c45 - AVRO-1733: C#: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * 5cb83db - AVRO-1732: C++: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * bc19e3a - AVRO-1729: Ruby: Add LICENSE and NOTICE to ruby gems. (1 year, 6 
> months ago)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AVRO-2023) backport and update license fixes for branch-1.7

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-2023:
-

There is no NOTICE or LICENSE file in js.
If nothing is present, is there a need to add that, or since it is empty 
nothing is needed there?

> backport and update license fixes for branch-1.7
> 
>
> Key: AVRO-2023
> URL: https://issues.apache.org/jira/browse/AVRO-2023
> Project: Avro
>  Issue Type: Task
>  Components: build, community
>Affects Versions: 1.7.7
>Reporter: Sean Busbey
>Priority: Blocker
> Fix For: 1.7.8
>
>
> Backport the changes from AVRO-1722 and subtasks, ensure they're applicable 
> for branch-1.7.
> git history as summary:
> {code}
> $ git hist --grep AVRO-1722 --grep AVRO-1727 --grep AVRO-1728 --grep 
> AVRO-1729 --grep AVRO-1730 --grep AVRO-1731 --grep AVRO-1732 --grep AVRO-1733 
> --grep AVRO-1734 --grep AVRO-1735 --grep AVRO-1736 --grep AVRO-1771 
> origin/branch-1.8
> * 059e6df - AVRO-1771. Add LICENSE and NOTICE to avro-doc artifact. 
> Contributed by blue. (1 year, 3 months ago)
> * ee28a20 - AVRO-1728: Java: Add LICENSE and NOTICE files to jars. (1 year, 4 
> months ago)
> * 80ba788 - AVRO-1722 ADDENDUM: Add last license doc changes, rat helper. (1 
> year, 4 months ago)
> * bf751df - AVRO-1722 ADDENDUM: Java: Fix tests broken by adding licenses. (1 
> year, 4 months ago)
> * f49b2d3 - AVRO-1722: Update root LICENSE.txt and NOTICE.txt. (1 year, 4 
> months ago)
> * 2c6c570 - AVRO-1730: Python3: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * e11c588 - AVRO-1730: Python: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * ada69ac - AVRO-1736: PHP: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * 96d2d35 - AVRO-1735: Perl: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * df5c513 - AVRO-1731: C: Add LICENSE and NOTICE to binary distribution. (1 
> year, 4 months ago)
> * 3585c45 - AVRO-1733: C#: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * 5cb83db - AVRO-1732: C++: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * bc19e3a - AVRO-1729: Ruby: Add LICENSE and NOTICE to ruby gems. (1 year, 6 
> months ago)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] Release Apache Avro 1.8.2 RC3

[Suraj Acharya]

No,
This has been closed.
The vote has failed!

S

On Mon, May 1, 2017 at 6:08 PM, Harsha Chintalapani <a...@harsha.io> wrote:

> Hi,
>  is this VOTE thread still active.
> Thanks,
> Harsha
>
> On Thu, Apr 13, 2017 at 11:13 AM Sean Busbey <bus...@cloudera.com> wrote:
>
> > Thanks for continuing to push on this Suraj!
> >
> > On Thu, Apr 13, 2017 at 9:03 AM, suraj acharya <suraj@gmail.com>
> > wrote:
> > > Hi Gabor,
> > >
> > > Thanks for looking at the RC.
> > >
> > > * The issue of the missing file seems like a bad push or some other
> > issue.
> > > * Regarding the JS issue, no it was not an intentional numbering. The
> > > release guide didnt have a mention of it and I missed it.
> > > For everyone, this is the value that needs to be bumped.
> > > https://github.com/apache/avro/blob/branch-1.8/lang/js/package.json#L3
> > >
> > > I dont believe this RC can pass and I *close* the vote.
> > >
> > > I will try again to build a new RC may be next month since all pushes
> on
> > > 1.8 were stopped while I was working on this.
> > >
> > > Once again thanks for taking the time
> > >
> > > Suraj Acharya
> > >
> > > -Suraj Acharya
> > >
> > > On Thu, Apr 13, 2017 at 6:59 AM, Gabor Szadovszky <
> > > gabor.szadovs...@cloudera.com> wrote:
> > >
> > >> Hi Suraj,
> > >>
> > >> Thanks a lot for taking care of this new release.
> > >>
> > >> Verified the checksums and ASC under https://dist.apache.org/repos/
> > >> dist/dev/avro/avro-1.8.2-rc3/ <https://dist.apache.org/
> > >> repos/dist/dev/avro/avro-1.8.2-rc3/>
> > >> Is it intentional that the JS has the version 1.8.0 while all the
> others
> > >> have 1.8.2?
> > >> All the checksums and ASC are correct.
> > >>
> > >> By unpacking the src tar I’ve got an unclear error message:
> > >> tar: copyfile unpack (avro-src-1.8.2/lang/java/
> > >> mapred/src/test/resources/org/apache/avro/mapreduce/
> > >> mapreduce-test-input.avro/SUCCESS.crc) failed: No such file or
> directory
> > >> In addition this file does not exist in the github repo under the
> label
> > >> release-1.8.2-rc3. I guess because of this anomaly I was not able to
> do
> > a
> > >> mvn clean install in the unpacked src archive (unit test failure).
> > >> Apart from that the src archive contains the same files as in the
> repo.
> > >>
> > >> mvn clean install works properly with the related tag in the github
> > repo.
> > >>
> > >> Regards,
> > >> Gabor
> > >>
> > >>
> > >> > On 12 Apr 2017, at 20:35, Suraj Acharya <su...@apache.org> wrote:
> > >> >
> > >> > Hi everyone,
> > >> >
> > >> > I propose the following RC to be released as official Apache Avro
> > 1.8.2
> > >> > release.
> > >> >
> > >> > The commit id is e38f7074d7c8f9156b39c8310302486ced93767a
> > >> >
> > >> > * This corresponds to the tag: release-1.8.2-rc3
> > >> > * https://s.apache.org/avro-1.8.2-rc3
> > >> >
> > >> > The release tarball, signature, and checksums are here:
> > >> > * https://dist.apache.org/repos/dist/dev/avro/avro-1.8.2-rc3/
> > >> >
> > >> > You can find the KEYS file here:
> > >> > * https://dist.apache.org/repos/dist/release/avro/KEYS
> > >> >
> > >> > Binary artifacts for Java are staged in Nexus here:
> > >> > *
> > https://repository.apache.org/content/repositories/orgapacheavro-1012/
> > >> >
> > >> > This release includes:
> > >> > * A spec for single-message Avro encoding and a Java implementation
> > >> > * Java: Bug fixes for Java logical types
> > >> > * Java: Support for Decimal with specific classes
> > >> > * Ruby: A fix for compatibility when using snappy
> > >> > * Python 3: Updated to use the standard module-level logging pattern
> > >> > * C++: Support for Boost >= 1.59
> > >> > * And more bug fixes...
> > >> >
> > >> > Please download, verify, and test. This vote will remain open for at
> > >> least
> > >> > 72 hours. Given sufficient votes, I would like to close it on or
> about
> > >> 9AM
> > >> > CDT on Wednesday, 19 April 2017.
> > >> >
> > >> > [ ] +1 Release this as Apache Avro 1.8.2
> > >> > [ ] +0
> > >> > [ ] -1 Do not release this because...
> > >> >
> > >> > --
> > >> > Suraj Acharya
> > >>
> > >>
> >
> >
> >
> > --
> > busbey
> >
>

[jira] [Commented] (AVRO-2023) backport and update license fixes for branch-1.7

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-2023:
-

Apart from the above mentioned files AVRO-2023 branch now fails on only 5 files
{code}
5 Unknown Licenses

***

Unapproved licenses:

  lang/java/ipc/src/main/java/org/apache/avro/ipc/trace/static/g.bar.js
  lang/java/ipc/src/main/java/org/apache/avro/ipc/trace/static/protovis-r3.2.js
  lang/java/tools/src/main/resources/META-INF/cddl-1.0.text
  lang/java/tools/src/main/resources/META-INF/cddl-1.1.text
  lang/java/tools/src/main/resources/META-INF/mpl-2.0.text

***
{code}

If the above questions are answered, I will merge 
https://github.com/spacharya/avro/commits/AVRO-2023 to branch-1.7 and continue 
on the release process.

> backport and update license fixes for branch-1.7
> 
>
> Key: AVRO-2023
> URL: https://issues.apache.org/jira/browse/AVRO-2023
> Project: Avro
>  Issue Type: Task
>  Components: build, community
>Affects Versions: 1.7.7
>Reporter: Sean Busbey
>Priority: Blocker
> Fix For: 1.7.8
>
>
> Backport the changes from AVRO-1722 and subtasks, ensure they're applicable 
> for branch-1.7.
> git history as summary:
> {code}
> $ git hist --grep AVRO-1722 --grep AVRO-1727 --grep AVRO-1728 --grep 
> AVRO-1729 --grep AVRO-1730 --grep AVRO-1731 --grep AVRO-1732 --grep AVRO-1733 
> --grep AVRO-1734 --grep AVRO-1735 --grep AVRO-1736 --grep AVRO-1771 
> origin/branch-1.8
> * 059e6df - AVRO-1771. Add LICENSE and NOTICE to avro-doc artifact. 
> Contributed by blue. (1 year, 3 months ago)
> * ee28a20 - AVRO-1728: Java: Add LICENSE and NOTICE files to jars. (1 year, 4 
> months ago)
> * 80ba788 - AVRO-1722 ADDENDUM: Add last license doc changes, rat helper. (1 
> year, 4 months ago)
> * bf751df - AVRO-1722 ADDENDUM: Java: Fix tests broken by adding licenses. (1 
> year, 4 months ago)
> * f49b2d3 - AVRO-1722: Update root LICENSE.txt and NOTICE.txt. (1 year, 4 
> months ago)
> * 2c6c570 - AVRO-1730: Python3: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * e11c588 - AVRO-1730: Python: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * ada69ac - AVRO-1736: PHP: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * 96d2d35 - AVRO-1735: Perl: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * df5c513 - AVRO-1731: C: Add LICENSE and NOTICE to binary distribution. (1 
> year, 4 months ago)
> * 3585c45 - AVRO-1733: C#: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * 5cb83db - AVRO-1732: C++: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * bc19e3a - AVRO-1729: Ruby: Add LICENSE and NOTICE to ruby gems. (1 year, 6 
> months ago)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (AVRO-2023) backport and update license fixes for branch-1.7

[Suraj Acharya (JIRA)]

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

Suraj Acharya edited comment on AVRO-2023 at 5/1/17 12:01 AM:
--

Some of the files has a different licensing : 
* 
https://github.com/apache/avro/blob/branch-1.7/lang/java/ipc/src/main/java/org/apache/avro/ipc/trace/static/protovis-r3.2.js
 Stanford Visualization Group has the license.
* 
https://github.com/apache/avro/blob/branch-1.7/lang/java/ipc/src/main/java/org/apache/avro/ipc/trace/static/g.bar.js
 is licensed under the MIT license.
* In the changeset of AVRO-1728 
https://github.com/spacharya/avro/blob/AVRO-2023/lang/java/tools/src/main/resources/META-INF/cddl-1.0.text
 CDDL licensing was added. Do i just exclude the text files which have just the 
licensing in them?





[~busbey]/ [~rdblue] is this okay?


was (Author: sacharya):

Some of the files has a different licensing : 
* 
https://github.com/apache/avro/blob/branch-1.7/lang/java/ipc/src/main/java/org/apache/avro/ipc/trace/static/protovis-r3.2.js
 Stanford Visualization Group has the license.
* In the changeset of AVRO-1728 
https://github.com/spacharya/avro/blob/AVRO-2023/lang/java/tools/src/main/resources/META-INF/cddl-1.0.text
 CDDL licensing was added. Do i just exclude the text files which have just the 
licensing in them?





[~busbey]/ [~rdblue] is this okay?

> backport and update license fixes for branch-1.7
> 
>
> Key: AVRO-2023
> URL: https://issues.apache.org/jira/browse/AVRO-2023
> Project: Avro
>  Issue Type: Task
>  Components: build, community
>Affects Versions: 1.7.7
>Reporter: Sean Busbey
>Priority: Blocker
> Fix For: 1.7.8
>
>
> Backport the changes from AVRO-1722 and subtasks, ensure they're applicable 
> for branch-1.7.
> git history as summary:
> {code}
> $ git hist --grep AVRO-1722 --grep AVRO-1727 --grep AVRO-1728 --grep 
> AVRO-1729 --grep AVRO-1730 --grep AVRO-1731 --grep AVRO-1732 --grep AVRO-1733 
> --grep AVRO-1734 --grep AVRO-1735 --grep AVRO-1736 --grep AVRO-1771 
> origin/branch-1.8
> * 059e6df - AVRO-1771. Add LICENSE and NOTICE to avro-doc artifact. 
> Contributed by blue. (1 year, 3 months ago)
> * ee28a20 - AVRO-1728: Java: Add LICENSE and NOTICE files to jars. (1 year, 4 
> months ago)
> * 80ba788 - AVRO-1722 ADDENDUM: Add last license doc changes, rat helper. (1 
> year, 4 months ago)
> * bf751df - AVRO-1722 ADDENDUM: Java: Fix tests broken by adding licenses. (1 
> year, 4 months ago)
> * f49b2d3 - AVRO-1722: Update root LICENSE.txt and NOTICE.txt. (1 year, 4 
> months ago)
> * 2c6c570 - AVRO-1730: Python3: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * e11c588 - AVRO-1730: Python: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * ada69ac - AVRO-1736: PHP: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * 96d2d35 - AVRO-1735: Perl: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * df5c513 - AVRO-1731: C: Add LICENSE and NOTICE to binary distribution. (1 
> year, 4 months ago)
> * 3585c45 - AVRO-1733: C#: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * 5cb83db - AVRO-1732: C++: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * bc19e3a - AVRO-1729: Ruby: Add LICENSE and NOTICE to ruby gems. (1 year, 6 
> months ago)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AVRO-2023) backport and update license fixes for branch-1.7

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-2023:
-


Some of the files has a different licensing : 
* 
https://github.com/apache/avro/blob/branch-1.7/lang/java/ipc/src/main/java/org/apache/avro/ipc/trace/static/protovis-r3.2.js
 Stanford Visualization Group has the license.
* In the changeset of AVRO-1728 
https://github.com/spacharya/avro/blob/AVRO-2023/lang/java/tools/src/main/resources/META-INF/cddl-1.0.text
 CDDL licensing was added. Do i just exclude the text files which have just the 
licensing in them?





[~busbey]/ [~rdblue] is this okay?

> backport and update license fixes for branch-1.7
> 
>
> Key: AVRO-2023
> URL: https://issues.apache.org/jira/browse/AVRO-2023
> Project: Avro
>  Issue Type: Task
>  Components: build, community
>Affects Versions: 1.7.7
>Reporter: Sean Busbey
>Priority: Blocker
> Fix For: 1.7.8
>
>
> Backport the changes from AVRO-1722 and subtasks, ensure they're applicable 
> for branch-1.7.
> git history as summary:
> {code}
> $ git hist --grep AVRO-1722 --grep AVRO-1727 --grep AVRO-1728 --grep 
> AVRO-1729 --grep AVRO-1730 --grep AVRO-1731 --grep AVRO-1732 --grep AVRO-1733 
> --grep AVRO-1734 --grep AVRO-1735 --grep AVRO-1736 --grep AVRO-1771 
> origin/branch-1.8
> * 059e6df - AVRO-1771. Add LICENSE and NOTICE to avro-doc artifact. 
> Contributed by blue. (1 year, 3 months ago)
> * ee28a20 - AVRO-1728: Java: Add LICENSE and NOTICE files to jars. (1 year, 4 
> months ago)
> * 80ba788 - AVRO-1722 ADDENDUM: Add last license doc changes, rat helper. (1 
> year, 4 months ago)
> * bf751df - AVRO-1722 ADDENDUM: Java: Fix tests broken by adding licenses. (1 
> year, 4 months ago)
> * f49b2d3 - AVRO-1722: Update root LICENSE.txt and NOTICE.txt. (1 year, 4 
> months ago)
> * 2c6c570 - AVRO-1730: Python3: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * e11c588 - AVRO-1730: Python: Add LICENSE and NOTICE to distribution. (1 
> year, 4 months ago)
> * ada69ac - AVRO-1736: PHP: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * 96d2d35 - AVRO-1735: Perl: Add LICENSE and NOTICE to distribution. (1 year, 
> 4 months ago)
> * df5c513 - AVRO-1731: C: Add LICENSE and NOTICE to binary distribution. (1 
> year, 4 months ago)
> * 3585c45 - AVRO-1733: C#: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * 5cb83db - AVRO-1732: C++: Add LICENSE and NOTICE to binary distribution. (1 
> year, 6 months ago)
> * bc19e3a - AVRO-1729: Ruby: Add LICENSE and NOTICE to ruby gems. (1 year, 6 
> months ago)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: https://github.com/apache/avro Empty?

[Suraj Acharya]

Hi,
We have been notified by the Infra team of the Apache foundation that
certain mirrors are being deleted and that they are currently working on
it. This is not intentional.
They have opened an issue with Github to resolve the same.

In the meantime you can use the git repository hosted by the ASF to work on
 : https://git1-us-west.apache.org/repos/asf/avro.git

If there are any developments I will surely let you know of the same.


Suraj Acharya


On Fri, Apr 28, 2017 at 3:13 PM, Zoltan Farkas <zolyfar...@yahoo.com.invalid
> wrote:

> Anybody aware of issues with GitHub repo?
>
> I am getting:
>
> This repository is empty.
>
>
> —Z

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

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-2003:
-

Ignore build 14.
Build 15 artifact : 
https://builds.apache.org/job/PreCommit-AVRO-Build-TEST/ws/component/patchprocess/whitespace-eol.txt

> Report specific location of schema incompatibilities
> 
>
> Key: AVRO-2003
> URL: https://issues.apache.org/jira/browse/AVRO-2003
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.8.1
> Environment: Any java env
>Reporter: Elliot West
>Assignee: Elliot West
>Priority: Minor
> Fix For: 1.9.0
>
> Attachments: AVRO-2003.patch
>
>
> h2. Overview
> Building on the work to improve schema incompatibility reporting in 
> AVRO-1933, it would be useful if the {{SchemaCompatibility}} classes could 
> also report the location in the schema where any incompatibility was 
> encountered.
> It is recommended that the location reported is both easily readable by 
> humans and machines. In the first case this would assist schema developers to 
> pin-point issues in there schema documents, and in the latter case it 
> provides a useful mechanism to schema tooling, such as IDEs and editors, to 
> easily select the pertinent nodes in the Schema document tree.
> h2. Implementation specifics
> To meet this requirements it is suggested that the location is encoded using 
> the [JSON Pointer specification|https://tools.ietf.org/html/rfc6901]. This is 
> both easily parsed by users, but is also supported by a number of libraries 
> for a range of common programming languages and platforms.
> h2. Examples
> Given the following example schema, consider some incompatibility scenarios. 
> For each case an expected JSON Pointer description of the incompatibility 
> location is described:
> {code}
> {
>   "type": "record",
>   "name": "myRecord",
>   "fields" : [
> {"name": "pField", "type": "long"},
> {"name": "uField", "type":
>   ["null", "int", "string"]
> },
> {"name": "eField", "type": 
>   { "type": "enum", "name": "Suit", "symbols" : ["SPADES", "HEARTS", 
> "DIAMONDS", "CLUBS"] }
> },
> {"name": "aField", "type":
>   {"type": "array", "items": "string"}
> },
> {"name": "mField", "type": 
>   {"type": "map", "values": "long"}
> },
> {"name": "fField", "type": 
>   {"type": "fixed", "size": 16, "name": "md5"}
> }
>   ]
> }
> {code}
> Possible incompatibility scenarions and the location that would be reported 
> back to the user/tool: 
> * Root type incompatibility; report location: {{/}}
> * Record name mismatch; report location: {{/name}}
> * {{pField}} type incompatibility; report location: {{/fields/0/type}}
> * {{uField}} field type incompatibility; report location: {{/fields/1/type}}
> * {{uField}} missing union branch {{string}}; report location: 
> {{/fields/1/type/2}}
> * {{eField}} field type incompatibility; report location: {{/fields/2/type}}
> * {{eField}} missing enum symbol; report location: {{/fields/2/type/symbols}}
> * {{eField}} enum name mismatch; report location: {{/fields/2/type/name}}
> * {{aField}} field type incompatibility; report location: {{/fields/3/type}}
> * {{aField}} array element type incompatibility; report location: 
> {{/fields/3/type/items}}
> * {{mField}} field type incompatibility; report location: {{/fields/4/type}}
> * {{mField}} map value type incompatibility; report location: 
> {{/fields/4/type/values}}
> * {{fField}} field type incompatibility; report location: {{/fields/5/type}}
> * {{fField}} fixed name mismatch; report location: {{/fields/5/type/name}}
> * {{fField}} fixed size type incompatibility; report location: 
> {{/fields/5/type/size}}
> * {{fField}} missing default value; report location: {{/fields/5}}
> h2. Notes
> * This ticket depends on AVRO-1933 and associated patches.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Suraj Acharya (JIRA)]

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

Suraj Acharya commented on AVRO-1957:
-

Sorry that was due to a configuration error. I have fixed it now.

{code}
JIRA Plugin: no credentials provided to write a comment.


+1 overall

| Vote |  Subsystem |  Runtime   | Comment

|   0  |reexec  |   0m 17s   | Docker mode activated. 
|  +1  |   @author  |   0m  0s   | The patch does not contain any @author 
|  ||| tags.
|  +1  | buildtest  |   0m  0s   | master passed 
|  +1  |whitespace  |   0m  0s   | The patch has no whitespace issues. 
|  +1  | buildtest  |   6m 34s   | the patch passed 
|  ||   6m 55s   | 


|| Subsystem || Report/Notes ||

| Docker | Client=1.13.1 Server=1.13.1 Image:yetus/avro:793178a |
| JIRA Issue | AVRO-1957 |
| GITHUB PR | https://github.com/apache/avro/pull/154 |
| Optional Tests |  buildtest  javac  |
| uname | Linux 58ded22ec82c 3.13.0-106-generic #153-Ubuntu SMP Tue Dec 6 
15:44:32 UTC 2016 x86_64 GNU/Linux |
| Build tool | build |
| git revision | master / 793178a |
| Default Java | 1.7.0_111 |
| modules | C: lang/java U: lang/java |
| Console output | 
https://builds.apache.org/job/PreCommit-AVRO-Build-TEST/9/console |
| Powered by | Apache Yetus 0.4.0   http://yetus.apache.org |
{code}

> TimeConversions do not implement getRecommendedSchema()
> ---
>
> Key: AVRO-1957
> URL: https://issues.apache.org/jira/browse/AVRO-1957
> Project: Avro
>  Issue Type: Bug
>Affects Versions: 1.8.1
>Reporter: Sean Timm
>Assignee: Sean Timm
> Fix For: 1.8.2
>
>
> org.apache.avro.data.TimeConversions.TimestampConversion and other date and 
> time conversions do not implement getRecommendedSchema(). When trying to 
> dynamically generate an Avro schema from a pojo that contains a DateTime 
> object using ReflectData, I get an unsupported operation exception.
> I think the implementation should be as simple as
> {code}
> @Override
> public Schema getRecommendedSchema() {
>   return 
> LogicalTypes.timestampMillis().addToSchema(Schema.create(Schema.Type.LONG));
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Pre-Commit Build Jobs on Apache AVRO

[Suraj Acharya]

Sorry,
I used a few terminology straight out of YETUS.
* Modules are usually sub projects. In our case every language has been
setup to be a module. Was a bit easier that way.
* One of the main tests it runs is ./build.sh on the module(language) which
had the change present. The determination of the change in language is done
by the YETUS system. Apart from build.sh it also checks whitespace and
asflicense issues.
* Once merged, when a ticket is converted to "Patch Available" the jenkins
job is triggered. It looks for either the GitHub bot comment mentioning the
location of the patch file or the patch file in the attachments. If any
changes are made and a new patch is submitted, then the job is retriggered.

Hope that helps

S


On Tue, Apr 25, 2017 at 1:45 AM, Gill, John <john.g...@teradata.com> wrote:

> Suraj,
> Few questions for clarifications:
> - What do you mean by module - Java, C, Python or like an individual
> code file?
> - When you say, " ./build.sh test on the module you have made the
> change to" how does it determine this?
> - Once merged what will trigger the PreCommit Build? Opening a PR?
> Submitting a Patch?
>
> Thanks,
> John
>
> 
> From: Suraj Acharya [su...@apache.org]
> Sent: Monday, April 24, 2017 7:15 PM
> To: dev@avro.apache.org
> Subject: Pre-Commit Build Jobs on Apache AVRO
>
> Hi,
>
>
> I have made an attempt and have setup a pre-commit job using the build
> system in apache.
> https://builds.apache.org/view/PreCommit%20Builds/job/
> PreCommit-AVRO-Build-TEST/
>
> I have tried to test most of the use cases when I was setting it up.
>
> The biggest usecase I have verified is java. I did run it against a few
> other language patches.
>
> The bot basically runs ./build.sh test on the module you have made the
> change to.  Hence, it is not recommended to make changes to multiple
> modules. It uses docker to run the tests in.
>
>
> Going forward I would like to hold every patch to a minimum of this level.
> A -1 from the bot should disqualify the patch from being submitted.
>
> If you believe there is a mistake in the bots response, either a positive
> or a negative please let me know.
>
>
> I hope no one has an issues with the setup.
>
>
> PS :
>
>- Due to a known issue in YETUS (the underlying build test system) if
>the GitHub bot doesn’t comment on the ticket, the test infrastructure
> will
>fail to pick up that issue. There is work currently in progress on the
> said
>issue. (YETUS-499)
>- Currently the code (AVRO-1887) has not been merged to avro:master.
>Hence, the code is being run on spacharya:master.
>- This is my first attempt at setting up a pre-commit job, if you can
>think of improvements or mistakes please let me know.
>
>
>
> Thanks
>
>
> Suraj Acharya
>

Pre-Commit Build Jobs on Apache AVRO

[Suraj Acharya]

Hi,


I have made an attempt and have setup a pre-commit job using the build
system in apache.
https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-AVRO-Build-TEST/

I have tried to test most of the use cases when I was setting it up.

The biggest usecase I have verified is java. I did run it against a few
other language patches.

The bot basically runs ./build.sh test on the module you have made the
change to.  Hence, it is not recommended to make changes to multiple
modules. It uses docker to run the tests in.


Going forward I would like to hold every patch to a minimum of this level.
A -1 from the bot should disqualify the patch from being submitted.

If you believe there is a mistake in the bots response, either a positive
or a negative please let me know.


I hope no one has an issues with the setup.


PS :

   - Due to a known issue in YETUS (the underlying build test system) if
   the GitHub bot doesn’t comment on the ticket, the test infrastructure will
   fail to pick up that issue. There is work currently in progress on the said
   issue. (YETUS-499)
   - Currently the code (AVRO-1887) has not been merged to avro:master.
   Hence, the code is being run on spacharya:master.
   - This is my first attempt at setting up a pre-commit job, if you can
   think of improvements or mistakes please let me know.



Thanks


Suraj Acharya