I've added you as an owner of both. You should also now be able to add
others in the future as needed.
Thanks for all your work, making this release happen!
Doug
On Thu, May 16, 2019 at 1:00 PM Driesprong, Fokko
wrote:
> Thanks Doug,
>
> My username for both PyPi and Rubygems is Fokko. Also,
Thanks Doug,
My username for both PyPi and Rubygems is Fokko. Also, feel free to push
yourself :-)
Cheers, Fokko
Op do 16 mei 2019 om 19:50 schreef Doug Cutting :
> I'm happy to push these myself, or better yet, permit others.
>
> Please send me PyPi and rubygems.org usernames to add.
>
> Thank
I'm happy to push these myself, or better yet, permit others.
Please send me PyPi and rubygems.org usernames to add.
Thanks,
Doug
On Thu, May 16, 2019 at 10:13 AM Daniel Kulp wrote:
>
>
> >
> > Also I'm blocked on verifying the python/ruby code due to the pip/gem
> > packages not yet having b
>
> Also I'm blocked on verifying the python/ruby code due to the pip/gem
> packages not yet having been pushed. Is there an ETA for those?
The issue here is that none of the “currently active” Avro committers have
access to the repositories for those. We’ve asked to have our accounts added
Is there a migration guide? I tried upgrading my project
https://github.com/phunt/avro-rpc-quickstart
last night and ran into some issues wrt avro refactoring (ipc in my case)
that might be good to highlight in a migration guide.
Also I'm blocked on verifying the python/ruby code due to the pip/ge
This is a fork of the discussion started in the release vote thread [1].
Just to keep the discussion going and follow up on issues and projects
that deserve attention.
So far open issues are:
BEAM-7328 Update Avro to version 1.9.0 in Java SDK
HIVE-21737 Upgrade Avro to version 1.9.0
FLINK-12532 U
Yes, sorry for polluting this thread, will fork it.
On Thu, May 16, 2019 at 1:45 PM Sean Busbey wrote:
>
> The matter of upgrading downstream projects should get its own thread
> on dev@avro rather than occurring on this VOTE.
>
> On Thu, May 16, 2019 at 5:14 AM Ismaël Mejía wrote:
> >
> > Argh
The matter of upgrading downstream projects should get its own thread
on dev@avro rather than occurring on this VOTE.
On Thu, May 16, 2019 at 5:14 AM Ismaël Mejía wrote:
>
> Argh this looks like problematic if Spark somehow wants to align the
> deps, hope it won't be mandatory.
>
> I filled some
Argh this looks like problematic if Spark somehow wants to align the
deps, hope it won't be mandatory.
I filled some more tickets, so the list of tickets so far:
BEAM-7328 Update Avro to version 1.9.0 in Java SDK
HIVE-21737 Upgrade Avro to version 1.9.0
FLINK-12532 Upgrade Avro to version 1.9.0
P
Thanks Nandor,
Upgrading Hive 2.x (Hadoop 2) is going to be painful since this is still on
Java 1.7. It is still relying on Avro 1.7.7. This is an issue because this
is also blocking upgrading Parquet, this implies that Hive 2.x does not
support reading lz4 and zstd compression.
>From Hive 3.x th
10 matches
Mail list logo
