Hey Dixit,
Sorry for the delay, I had to discuss this in more detail with some of our
other core developers.
The consensus seems to be that we would like push this project in a
direction where the changes can be quickly included in the next releases.
For this it is essential that we implement
Hi,
It'd really help if I got a reply soon. It'll be helpful in writing the
proposal since the deadline is on 27th. Thanks
Regards,
Akshay Dixit
On Sun, Mar 22, 2015 at 1:17 AM, Akshay Dixit akshayd...@gmail.com wrote:
Thanks for the explanation Marton. I've decided to try out for FLINK-1534.
Hello everyone,
I am working on affinity propagation implementation for Gelly (FLINK
1707 https://issues.apache.org/jira/browse/FLINK-1707).The
algorithm passes messages between every pair of vertices (NOT every pair
of connected vertices) in each iteration with computation complexity
Hey,
Give me an hour or so as I am in a meeting currently, but I will get back
to you afterwards.
Regards,
Gyula
On Tue, Mar 24, 2015 at 11:03 AM, Akshay Dixit akshayd...@gmail.com wrote:
Hi,
It'd really help if I got a reply soon. It'll be helpful in writing the
proposal since the deadline
If we could not get more capacity we could set up ASF Jenkins instead.
It is already used to power CI for many ASF projects like Hadoop so should
not be too shabby.
I have created ticket for Flink to setup ASF Jenkins but have not found
time to work on it.
- Henry
On Tuesday, March 24, 2015,
Timo Walther created FLINK-1777:
---
Summary: Update Java 8 Lambdas with Eclipse documentation
Key: FLINK-1777
URL: https://issues.apache.org/jira/browse/FLINK-1777
Project: Flink
Issue Type: Bug
Hi guys,
the build queue on travis is getting very very long. It seems that it takes
4 days now until commits to master are build. The nightly builds from the
website and the maven snapshots are also delayed by that.
Right now, there are 33 pull request builds scheduled (
Let's see what Travis replies to Robert, but in general I agree with Max.
Travis helped a lot to discover certain race conditions in the last weeks... I
would like to not ditch it completely as Max suggested.
On 24 Mar 2015, at 16:03, Maximilian Michels m...@apache.org wrote:
I would also
Dear Apache Flink enthusiast,
In just a few weeks, we'll be holding ApacheCon in Austin, Texas, and
we'd love to have you in attendance. You can save $300 on admission by
registering NOW, since the early bird price ends on the 21st.
Register at http://s.apache.org/acna2015-reg
ApacheCon this
Hi Gyula,
thank a lot. I still don't understand why setup() and open() can not be
unified? I also don't know, what the difference between RuntimeContext
and StreamTaskContext is (or to be more precise, why not using a single
context class that unifies both)?
About the renaming of Timestamp
Fabian Hueske created FLINK-1780:
Summary: Rename FlatCombineFunction to GroupCombineFunction
Key: FLINK-1780
URL: https://issues.apache.org/jira/browse/FLINK-1780
Project: Flink
Issue Type:
Hey Matthias,
Let's see if I get these things for you :)
1) The difference between setup and open is that, setup to set things like
collectors, runtimecontext and everything that will be used by the
implemented invokable, and also by the rich functions. Open is called after
setup, to actually
The setup and open methods could be called together, but they do different
tasks, and therefore I dont see any reason why they should be in a same
method. This is a critical part of the code so better keep things clean and
separate.
The RuntimeContext refers to the operator while the TaskContext
Thanks Gyula.
I agree too that simple and working implementations are preferrable over
hacky complex solutions. I'll start sketching out an initial straighforward
API with only basic pattern matching features
and base it on the existing windowing API. I'll post a draft of the
proposal, keeping
14 matches
Mail list logo
