Chesnay Schepler created FLINK-2562:
---
Summary: [py] Implement KeySelectors
Key: FLINK-2562
URL: https://issues.apache.org/jira/browse/FLINK-2562
Project: Flink
Issue Type: Sub-task
Hi,
I updated the Gelly Blog Post.
https://docs.google.com/document/d/1FMtpwKSE3kY7RfH082LzQpWrY6o-fdZVxqambIiC_rU/edit?usp=sharing
Let me know if there are comments or further suggestions. Otherwise, we'll
kick this one out of the nest, to see if it flies :)
On Wed, Jun 3, 2015 at 11:37 AM,
Vasia Kalavri created FLINK-2561:
Summary: Sync Gelly Java and Scala APIs
Key: FLINK-2561
URL: https://issues.apache.org/jira/browse/FLINK-2561
Project: Flink
Issue Type: Task
Hi Sachin,
I was actually under the impression that
ExecutionEnvironment.getExecutionEnvironment() returns the current
environment, if one has already been created.
I don't think that creating a second one is intentional there and if that's
the case, we should change it.
Cheers,
Vasia.
On 21
I just came across 2 more :/
I'm also in favor of tracking these with JIRA. How about test-stability
for a label?
-V.
On 21 August 2015 at 12:47, Matthias J. Sax mj...@informatik.hu-berlin.de
wrote:
I like the idea with the special label. Otherwise, it will be difficult
to find the correct
Congrats and welcome Chesnay!
On 21 August 2015 at 12:19, Stephan Ewen se...@apache.org wrote:
Welcome!
On Fri, Aug 21, 2015 at 10:42 AM, Fabian Hueske fhue...@gmail.com wrote:
Welcome on board Chesnay!
2015-08-20 21:25 GMT+02:00 Andra Lungu lungu.an...@gmail.com:
Congrats
+1 for Vasia's suggestion
On Aug 22, 2015 8:07 PM, Vasiliki Kalavri vasilikikala...@gmail.com
wrote:
I just came across 2 more :/
I'm also in favor of tracking these with JIRA. How about test-stability
for a label?
-V.
On 21 August 2015 at 12:47, Matthias J. Sax
Hi Vasia
In that case, we might as well change it.
getExecutionEnvironment actually goes through the contextFactory, and it
then depends on this contextFactory how it generates new environments. For
example, all the Test Environments currently are shared, i.e., the factory
returns the same object
Your arguments are perfectly valid. So, what I suggest is to have the
functions as they are now, e.g. groupReduceOnNeighbors
and to add a groupReduceOnNeighbors(blablaSameArguments, boolean
useJoinHints). That way, the user can decide whether they'd like to trade
speed for a program that actually
This is an interesting issue, because, quite frankly, the join hint you
passed simply reversed the sides of the join. The algorithm is still the
same and has the same minimum memory requirements.
The fact that it made a difference is quite curious. The only thing I can
imagine is that this hint
10 matches
Mail list logo
