Thanks Max! :-)
Von: Maximilian Michels
Gesendet: Freitag, 13. November 2015 00:02
An: dev@flink.apache.org
Betreff: [VOTE] [RESULT] Release Apache Flink 0.10.0 (release-0.10.0-rc8)
Thanks for voting! The vote passes.
The following votes have been cast:
+1 votes: 7
Stephan
Aljoscha
Robert
Ma
Hi,
I agree with Robert on this.
We tried to keep the examples concise and moved boilerplate code like the
parameter parsing to the end of the file for that reason. I’m +1 for removing
as much boilerplate code as possible but would prefer to keep the example
selfcontained and in one file.
Be
+1
We did the same when porting the Table API to Calcite and it worked very well.
Von: Till Rohrmann
My ruby skills are a bit rust(y) but I’d love to contribute.
Can you point me to a repository that I can fork?
From: Till Rohrmann
Sent: Wednesday, 1. April, 2015 09:29
To: dev@flink.apache.org
Where can I start contributing. I've got the feeling that it will be
inherently fa
If Put is not Serializable it cannot be serialized and shipped.
Is it possible to make that field transient and initialize Put in configure()?
From: Flavio Pompermaier
Sent: Friday, 3. April, 2015 01:42
To: dev@flink.apache.org
Now I made my fork (https://github.com/fpompermai
Yes, reusing output objects is a good practice but optional. It can help to
bring down GC overhead.
You could make your function a RichFunction and initialize the output object in
open().
Switching function serialization to Kryo is on our TODO list (FLINK-1256).
Would be good to fix that so
The tests that Ufuk is referring to are not deterministically failing. This is
about hard to debug and hard to fix tests where it is not clear who broke them.
Fixing such a test can take a several days or even more… So locking the master
branch is not an option IMO.
Deactivating the tests wi
+1
From: Henry Saputra
Sent: Friday, October 2, 2015 19:34
To: dev@flink.apache.org
Subject: Re: Pulling Streaming out of staging and project restructure
+1
On Friday, October 2, 2015, Matthias J. Sax wrote:
> It think, rename "flink-storm-compatibility-core" to just "flink-storm"
> would be
+1 to that, Stephan.
I can help with FLINK-2763 or FLINK-2800.
From: Stephan Ewen
Sent: Thursday, October 22, 2015 0:02
To: dev@flink.apache.org
Subject: Re: [VOTE] Release Apache Flink 0.10.0 (release-0.10.0-rc0)
>From my side 2888 is a valid blocker. Aljoscha also found another blocker
bug,
Resending to dev@f.a.o
Hi Xingcan,
This is expected behavior. In general, is not possible to guarantee results for
processing time.
Your query is translated as follows:
CollectionSrc(1) -round-robin-> MapFunc(n) -hash-part-> ProcessFunc(n) -fwd->
MapFunc(n) -fwd-> Sink(n)
The order of record
10 matches
Mail list logo
