There are significant changes between Avro 1.8 and Avro 1.9. I'm not sure
it's possible for beam-sdks-java-core to support both at the same time. The
fact that AvroIO is a part of the beam-sdks-java-core doesn't make it
simpler. However, I can see how we can build two binary artifacts with the
Good question. IMO it is a very good thing to have fun as with the variety
of uses of the Go language mascot.
Note that copyright and trademark should be clearly separated in this
discussion. These both govern "everyone can draw and adapt".
Copyright: contributed images owned by ASF, licensed
done
On Thu, Jan 16, 2020 at 8:08 AM Rehman Murad Ali <
rehman.murad...@venturedive.com> wrote:
> Hi,
>
> I appreciate if someone can run the mentioned job for this PR.
> https://github.com/apache/beam/pull/10316
>
> Run Java Flink PortableValidatesRunner Streaming
>
>
> *Thanks & Regards*
>
>
>
Hi Dev and Users,
Also we hope to kickoff a meetup in India this year.
https://www.meetup.com/Bangalore-Apache-Beam/
Please let us know if you'd like to get involved, speaking, hosting,
etc. Reply to me, private or on thread, and/or use this survey link:
https://forms.gle/cud39eh3FA1em7EU7
I forgot to explain why the most obvious path (just upgrade Avro to version
1.9.x) is not a valid long term solution. Other systems Beam runs on top of
(e.g. Spark!) also leak Avro into their core so in the moment Spark moves
up
to Avro 1.9.x Spark runner users will be in a really fragile
Nice! This is quite clever.
Kenn
On Mon, Jan 13, 2020 at 5:08 PM Chamikara Jayalath
wrote:
> Thanks Brian. Added some comments.
>
> On Mon, Jan 13, 2020 at 2:25 PM Brian Hulette wrote:
>
>> Hi everyone,
>> I have a proposal that I think can unify two problem sets:
>> 1) adding more IOs for
Shading should be a last resort:
https://jlbp.dev/JLBP-18.html
It tends to cause more problems than it solves. At best it's a stopgap
measure when you don't have the resources to fix the real problem. In
this case it sounds like the real issue is that AVRO is not stable.
There are at least three
*correction: ASF does not require transfer of copyright, only appropriate
license
On Thu, Jan 16, 2020 at 8:45 AM Kenneth Knowles wrote:
> Good question. IMO it is a very good thing to have fun as with the variety
> of uses of the Go language mascot.
>
> Note that copyright and trademark should
done.
On Thu, Jan 16, 2020 at 1:07 PM Tomo Suzuki wrote:
> Hi Beam committers,
>
> I appreciate if somebody can trigger precommit checks for
> https://github.com/apache/beam/pull/10614 with the following additional
> checks:
>
> Run Java PostCommit
> Run Java HadoopFormatIO Performance Test
>
+1 very nice explanation
On Wed, Jan 15, 2020 at 1:57 PM Ahmet Altay wrote:
> +1 - Thank you for driving this!
>
> On Wed, Jan 15, 2020 at 1:55 PM Thomas Weise wrote:
>
>> +1 for the namespace proposal.
>>
>> It is similar to github repos. Top-level is the org, then single level
>> for repo
On Thu, Jan 16, 2020 at 11:00 AM Kenneth Knowles wrote:
>
> IIRC in Java it is forbidden to output an element with a timestamp outside
> its current window.
I don't think this is checked anywhere. (Not sure how you would check
it, as there's not generic window containment function--I suppose
Here is the Jira ticket I created:
https://issues.apache.org/jira/browse/INFRA-19732
Kenn, I tried to add you as a watcher, but was not able to do so because of
lack of permission. Thanks for your willingness to help :)
On Thu, Jan 16, 2020 at 10:47 AM Kenneth Knowles wrote:
> They may require
Avro does not follow semver. They update the major version when the
serialization format changes and the minor version when the API
changes in a backwards incompatible way. See
https://issues.apache.org/jira/browse/AVRO-2687
On Thu, Jan 16, 2020 at 12:50 PM Luke Cwik wrote:
>
> Does avro not
IIRC in Java it is forbidden to output an element with a timestamp outside
its current window. An exception is outputs from @FinishBundle, where the
output timestamp is required and the window is applied. TBH it seems more
of an artifact of a mismatch between the pre-windowing and post-windowing
Thank Ismaël. Java Precommit failed due to timed out. Can you rerun it
please?
https://github.com/apache/beam/pull/10316
*Thanks & Regards*
*Rehman Murad Ali*
Software Engineer
Mobile: +92 3452076766
Skype: rehman.muradali
On Thu, Jan 16, 2020 at 7:17 PM Ismaël Mejía wrote:
> done
>
>
They may require a PMC member, so feel free to add me or another. But a
link to your thread should probably be enough.
On Wed, Jan 15, 2020 at 1:39 PM Hannah Jiang wrote:
> Thanks Andrew, I will try with Jira.
>
> On Wed, Jan 15, 2020 at 1:13 PM Andrew Pilloud
> wrote:
>
>> I'm not sure you
Hi Beam committers,
I appreciate if somebody can trigger precommit checks for
https://github.com/apache/beam/pull/10614 with the following additional
checks:
Run Java PostCommit
Run Java HadoopFormatIO Performance Test
Run BigQueryIO Streaming Performance Test Java
Run Dataflow ValidatesRunner
Looks like there's some strategy to get to the right solution here and that
it may likely involve breaking compatibility.
One option for myself would be to strip the Beam JAR of AvroCoder and
combine with the old AvroCoder from Beam 2.16 -- this would allow me to
upgrade Beam but of course is
I was going to let Julian answer as he is following this thread, but yes,
the design will have appropriate licences so we can use and reuse and
modify it in the future. Julian also expressed willingness to stay active
in the community to contribute more varieties of the mascot as we need :)
On
Hi Beam Committers,
(Andrew, thanks! but I needed to fix tests)
I appreciate if somebody can re-trigger precommit checks for
https://github.com/apache/beam/pull/10614 with the following
additional checks:
Run Java PostCommit
Run Java HadoopFormatIO Performance Test
Run BigQueryIO Streaming
Done
On Thu, Jan 16, 2020 at 5:59 PM Boyuan Zhang wrote:
> Hey,
>
> I'm Boyuan, currently working on beam 2.19.0 release. Can anyone add me as
> a owner of apache-beam package in PyPi for later pushing artifacts? My id
> is boyuanzz.
>
> Thanks for your help!
>
On Thu, Jan 16, 2020 at 11:38 AM Robert Bradshaw
wrote:
> On Thu, Jan 16, 2020 at 11:00 AM Kenneth Knowles wrote:
> >
> > IIRC in Java it is forbidden to output an element with a timestamp
> outside its current window.
>
> I don't think this is checked anywhere. (Not sure how you would check
>
Regarding Google's advice about shading: don't go to a "one version rule"
monorepo for advice about solving diamond dependencies in the wild.
It is a useful description of the pitfalls. We (and Flink before us, and
likely many more) are already doing something that avoids many of them or
makes
Hey Beam Team,
Thanks for your support around this! I will be be submitting an individual
contributors license agreement.
http://www.apache.org/licenses/contributor-agreements.html
Cheers!
Julian
On 2020/01/16 19:17:24 Aizhamal Nurmamat kyzy wrote: > I was going to let
Julian answer as he
Hey,
I'm Boyuan, currently working on beam 2.19.0 release. Can anyone add me as
a owner of apache-beam package in PyPi for later pushing artifacts? My id
is boyuanzz.
Thanks for your help!
Hi all,
Thanks for starting this thread. I have another questions about this policy
change.
I don't know If you also noticed that behaviour of Phrase Triggering became
really unpredictable since Policy changed. What usually happens is that
after "retest this please" command no tests running are
Adding to Ismaël, I find moving Avro out of the core, and keeping
compatibility as a non-exclusive options. Of course, it would require more
effort from our side.
On Thu, Jan 16, 2020 at 12:29 PM Ismaël Mejía wrote:
> For the interested there was also some extra context in the discussion at:
>
For the interested there was also some extra context in the discussion at:
https://github.com/apache/beam/pull/9779
Gleb mentioned the key two points:
1. The fact that Avro is exposed in the User API in beam-sdks-java-core was
a
mistake and makes fixing this issue backwards incompatible.
2.
28 matches
Mail list logo
