[
https://issues.apache.org/jira/browse/FLINK-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274340#comment-16274340
]
Vasia Kalavri commented on FLINK-5506:
--
I only had a quick look at the code; I
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/4179#discussion_r124514726
--- Diff:
flink-libraries/flink-gelly-examples/src/main/java/org/apache/flink/graph/drivers/parameter/Parameter.java
---
@@ -40,6 +40,15 @@
String
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/3433#discussion_r108067501
--- Diff:
flink-libraries/flink-gelly-examples/src/main/java/org/apache/flink/graph/drivers/parameter/Parameter.java
---
@@ -0,0 +1,55
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/3431
Thanks! Then, it's good to go from my side.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this fe
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/3434
Thanks @greghogan. Looks good!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/3434
Does `AnalyticResult` also need a method like `toVerboseString()`? Could we
replace both with a e.g. `Result` type?
---
If your project is set up for it, you can reply to this email and have your
[
https://issues.apache.org/jira/browse/FLINK-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15896927#comment-15896927
]
Vasia Kalavri commented on FLINK-2910:
--
I think that's a good idea [~
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/3434
Thanks for the clarification @greghogan. +1 from me.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/3434
Hi @greghogan, thank you for the PR.
I didn't spot anything that needs fixing, but I'm wondering what's the
motivation to add these interfaces. I see how `toVerboseString()`
[
https://issues.apache.org/jira/browse/FLINK-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892696#comment-15892696
]
Vasia Kalavri edited comment on FLINK-4949 at 3/2/17 6:0
[
https://issues.apache.org/jira/browse/FLINK-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892696#comment-15892696
]
Vasia Kalavri commented on FLINK-4949:
--
Thanks you [~greghogan]. I can review du
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2733
Thanks for the results @greghogan! Updating the docs would be nice,
otherwise +1.
Do you think we should move existing implementations in the examples (there
are still relevant to demonstrate
[
https://issues.apache.org/jira/browse/FLINK-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri updated FLINK-2910:
-
Summary: Reorganize / Combine Gelly tests (was: Combine tests for binary
graph operators
[
https://issues.apache.org/jira/browse/FLINK-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri updated FLINK-2910:
-
Description:
- Some tests are spread out in different classes could be combined as well,
e.g. we
[
https://issues.apache.org/jira/browse/FLINK-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri updated FLINK-2910:
-
Fix Version/s: 1.3.0
> Combine tests for binary graph operat
[
https://issues.apache.org/jira/browse/FLINK-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889618#comment-15889618
]
Vasia Kalavri commented on FLINK-2910:
--
Thanks for the heads-up [~uce]. Yes, thi
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2885
Hi @joseprupi,
could you please rebase this PR? Right now it's not clear which are your
changes in order to review.
Thanks!
---
If your project is set up for it, you can reply to this
[
https://issues.apache.org/jira/browse/FLINK-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri updated FLINK-5127:
-
Affects Version/s: 1.1.0
1.2.0
> Reduce the amount of intermediate data
[
https://issues.apache.org/jira/browse/FLINK-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri updated FLINK-5127:
-
Fix Version/s: 1.3.0
> Reduce the amount of intermediate data in vertex-centric iterati
Title: Message Title
Vasia Kalavri commented on FLINK-1526
Title: Message Title
Vasia Kalavri commented on FLINK-1526
Vasia Kalavri created FLINK-5597:
Summary: Improve the LocalClusteringCoefficient documentation
Key: FLINK-5597
URL: https://issues.apache.org/jira/browse/FLINK-5597
Project: Flink
Issue
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2885
Hi @joseprupi, thank you for the PR! This should replace #2053, right? If
yes, could you please close #2053? Thanks!
---
If your project is set up for it, you can reply to this email and have your
Vasia Kalavri created FLINK-5434:
Summary: Remove unsupported project() transformation from Scala
DataStream docs
Key: FLINK-5434
URL: https://issues.apache.org/jira/browse/FLINK-5434
Project: Flink
Vasia Kalavri created FLINK-5351:
Summary: Make the TypeExtractor support functions with more than 2
inputs
Key: FLINK-5351
URL: https://issues.apache.org/jira/browse/FLINK-5351
Project: Flink
[
https://issues.apache.org/jira/browse/FLINK-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri resolved FLINK-5097.
--
Resolution: Fixed
Fix Version/s: 1.2.0
> The TypeExtractor is missing input t
[
https://issues.apache.org/jira/browse/FLINK-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri updated FLINK-5311:
-
Issue Type: Improvement (was: Bug)
> Write user documentation for BipartiteGr
[
https://issues.apache.org/jira/browse/FLINK-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri resolved FLINK-5311.
--
Resolution: Fixed
Fix Version/s: 1.2.0
> Write user documentation for BipartiteGr
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2984
Thank you @mushketyk. That's OK. I'm merging this PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2842
Done. I'll wait for travis, then merge.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this fe
[
https://issues.apache.org/jira/browse/FLINK-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15751890#comment-15751890
]
Vasia Kalavri commented on FLINK-5127:
--
It'd be nice to have for 1.2, bu
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2842
Sure, I can revert using `getMapReturnTypes` , rebase, and merge.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2984
Hi @mushketyk, thank you for the update!
Just a couple of small things and we can merge:
- Can you add a note in the beginning of the docs that bipartite graphs are
only currently supported in
[
https://issues.apache.org/jira/browse/FLINK-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15744495#comment-15744495
]
Vasia Kalavri commented on FLINK-5245:
--
My point is not that these features
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2984
Thank you for the update @mushketyk! I still don't see any link from the
Gelly guide page to the bipartite docs though. Can you please add that too?
Otherwise people won't be able to fin
[
https://issues.apache.org/jira/browse/FLINK-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742744#comment-15742744
]
Vasia Kalavri commented on FLINK-5245:
--
I don't think so. We used to
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91908218
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91907989
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91908101
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91908174
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91908875
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91907816
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91907924
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91908032
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91909237
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91908589
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91908073
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91908249
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91908641
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91908511
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91908677
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91908769
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
+nav-parent_id: graphs
+nav-pos: 6
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2984#discussion_r91907660
--- Diff: docs/dev/libs/gelly/bipartite_graph.md ---
@@ -0,0 +1,148 @@
+---
+title: Graph Generators
--- End diff --
This shouldn'
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2564
Thank you both for your work @mushketyk and @greghogan!
Please, keep in mind that we should always add documentation for every new
feature; especially a big one such as supporting a new graph type
[
https://issues.apache.org/jira/browse/FLINK-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733284#comment-15733284
]
Vasia Kalavri commented on FLINK-1536:
--
The idea is what [~greghogan] describes
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2564
I would go for `org.apache.flink.graph.bipartite`. I think that
`bidirectional` simply suggests that each edge exists in both directions.
---
If your project is set up for it, you can reply to this
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2842
Hi @twalthr, thank you so much for looking into this. I'll create an issue
for functions with > 2 inputs.
I have replaced `createTypeInfo` with `getMapReturnTypes` where possible,
but I&#
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2832
Yes, will do in the following days, thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2764
Sorry, no input from me regarding Eclipse. I've given up on it about a year
ago ;)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
[
https://issues.apache.org/jira/browse/FLINK-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri closed FLINK-5161.
Resolution: Not A Problem
> accepting NullValue for VV in Gelly examples and
[
https://issues.apache.org/jira/browse/FLINK-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15695728#comment-15695728
]
Vasia Kalavri commented on FLINK-5161:
--
Hi Wouter,
the vertex value caries
[
https://issues.apache.org/jira/browse/FLINK-5152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri closed FLINK-5152.
Resolution: Not A Problem
> accepting NullValue for EV in Gelly examp
[
https://issues.apache.org/jira/browse/FLINK-5152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692732#comment-15692732
]
Vasia Kalavri commented on FLINK-5152:
--
Hi [~otherwise777],
this is an exampl
Vasia Kalavri created FLINK-5127:
Summary: Reduce the amount of intermediate data in vertex-centric
iterations
Key: FLINK-5127
URL: https://issues.apache.org/jira/browse/FLINK-5127
Project: Flink
[
https://issues.apache.org/jira/browse/FLINK-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686870#comment-15686870
]
Vasia Kalavri commented on FLINK-1536:
--
This issue does not refer to bipar
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2842
Hi @greghogan,
I was able to fix the problem in `fromDataSet()` and `groupReduceOnEdges()`
with `EdgesFunction`. In the rest of the uses, I don't seem to find a way to
pass all the input
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2842
Thanks! Let me look into these and I'll get back to you.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2842
@greghogan if the input types are known, we should pass them, yes. What
other cases did you find?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2842#discussion_r88926689
--- Diff:
flink-libraries/flink-gelly/src/test/java/org/apache/flink/graph/test/operations/TypeExtractorTest.java
---
@@ -0,0 +1,106
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2842#discussion_r88926534
--- Diff:
flink-libraries/flink-gelly/src/test/java/org/apache/flink/graph/test/operations/TypeExtractorTest.java
---
@@ -0,0 +1,106
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2842#discussion_r88925478
--- Diff:
flink-libraries/flink-gelly/src/test/java/org/apache/flink/graph/test/operations/TypeExtractorTest.java
---
@@ -0,0 +1,106
GitHub user vasia opened a pull request:
https://github.com/apache/flink/pull/2842
[FLINK-5097][gelly] Add is missing input type information to TypeExtrâ¦
I've managed to reproduce @otherwise777's error as reported in the mailing
list and added a test case that failed
[
https://issues.apache.org/jira/browse/FLINK-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683366#comment-15683366
]
Vasia Kalavri commented on FLINK-1536:
--
Hi [~ivan.mushketyk]
afaik, nobod
[
https://issues.apache.org/jira/browse/FLINK-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683354#comment-15683354
]
Vasia Kalavri commented on FLINK-2254:
--
Hey [~ivan.mushketyk],
I would start
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2564
Thank @mushketyk. @greghogan are you shepherding this PR or shall I?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
[
https://issues.apache.org/jira/browse/FLINK-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri updated FLINK-5097:
-
Description: The TypeExtractor is called without information about the
input type in
Vasia Kalavri created FLINK-5097:
Summary: The TypeExtractor is missing input type information in
some Graph methods
Key: FLINK-5097
URL: https://issues.apache.org/jira/browse/FLINK-5097
Project
[
https://issues.apache.org/jira/browse/FLINK-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri updated FLINK-3551:
-
Assignee: Lim Chee Hau
> Sync Scala and Java Streaming Examp
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2725
Hey @greghogan, I didn't have time to review this one, you're a fast merger
:)
It looks like none of `VertexMertics`, `EdgeMetrics`,
`AverageClusteringCoefficient` are mentioned in the
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2730
Thanks! I agree on `Comparable` for vertex types. Good catch!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2731
Hi @greghogan,
do we really need a 12k-line csv and a 32k-line csv to test this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2733
Hi @greghogan,
thanks for this PR. Do you have any idea how this implementation compares
with the existing ones? I'm curious since it uses a bulk iteration and the
existing ones are using
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2730
Thanks for the PR @greghogan. Changes look good. Just make sure to also
update the docs before merging.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2670
+1 and thanks for the benchmarking link!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2670
Hi @greghogan,
I really like the cleanup and new organization!
Two thoughts:
- is the plan to add drivers for all library methods?
- shall we remove the `GraphMetrics` example since
[
https://issues.apache.org/jira/browse/FLINK-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri resolved FLINK-3888.
--
Resolution: Fixed
> Custom Aggregator with Convergence can't be registered direc
[
https://issues.apache.org/jira/browse/FLINK-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri updated FLINK-3888:
-
Fix Version/s: 1.2.0
> Custom Aggregator with Convergence can't be registered direc
[
https://issues.apache.org/jira/browse/FLINK-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri updated FLINK-4129:
-
Issue Type: Improvement (was: Bug)
> Remove the example HITSAlgori
[
https://issues.apache.org/jira/browse/FLINK-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri resolved FLINK-4129.
--
Resolution: Fixed
> Remove the example HITSAlgori
[
https://issues.apache.org/jira/browse/FLINK-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri updated FLINK-4129:
-
Summary: Remove the example HITSAlgorithm (was: HITSAlgorithm should test
for element-wise
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2663
Thanks, will merge.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2606
Thank you for the review @greghogan! I have addressed your comments.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/2606#discussion_r83632808
--- Diff:
flink-optimizer/src/main/java/org/apache/flink/optimizer/plantranslate/JobGraphGenerator.java
---
@@ -1513,14 +1513,21 @@ private void
[
https://issues.apache.org/jira/browse/FLINK-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15579933#comment-15579933
]
Vasia Kalavri commented on FLINK-4129:
--
I think having two HITS examples coul
[
https://issues.apache.org/jira/browse/FLINK-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15579877#comment-15579877
]
Vasia Kalavri commented on FLINK-1091:
--
Hi [~neelesh77],
I'm not workin
[
https://issues.apache.org/jira/browse/FLINK-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri updated FLINK-1091:
-
Assignee: (was: Vasia Kalavri)
> Allow joins with the solution set using key select
GitHub user vasia opened a pull request:
https://github.com/apache/flink/pull/2606
Allow custom convergence criterion in delta iterations
As discussed in the Jira issue, this PR contains the following changes:
1. use `TaskConfig.setConvergenceCriterion()` to set the custom
[
https://issues.apache.org/jira/browse/FLINK-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasia Kalavri reassigned FLINK-3888:
Assignee: Vasia Kalavri
> Custom Aggregator with Convergence can't be registered
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2564
Thanks for the update @mushketyk and for the review @greghogan. I agree
with your suggestions. For the type parameters I would go for ``. Let me know if there's any other issue you'd like my
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2587
Great cleanup! Thanks @greghogan. +1 to merge.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
1 - 100 of 1270 matches
Mail list logo
