Matthias Pohl created FLINK-33258:
-
Summary: Remove Kafka/Gelly module
Key: FLINK-33258
URL: https://issues.apache.org/jira/browse/FLINK-33258
Project: Flink
Issue Type: Sub-task
he change of dropping Gelly in order to
> let more developers and users be aware of it.
>
> Best regards,
> Jing
>
> On Wed, Oct 19, 2022 at 10:32 AM David Anderson
> wrote:
>
> > +1
> >
> > On Wed, Oct 12, 2022 at 10:59 PM Martijn Visser <
> m
+1 and I second Yu Li and Yun Gao. It should be also pointed out that Flink
will continue to support graph processing with a new plan in the upcoming
1.17 release notes which includes the change of dropping Gelly in order to
let more developers and users be aware of it.
Best regards,
Jing
On Wed
+1
On Wed, Oct 12, 2022 at 10:59 PM Martijn Visser
wrote:
> Hi everyone,
>
> I would like to open a vote for dropping Gelly, which was discussed a long
> time ago but never put to a vote [1].
>
> Voting will be open for at least 72 hours.
>
> Best regards,
>
>
+1
On Tue, Oct 18, 2022 at 10:49 AM Dong Lin wrote:
> +1
>
> On Thu, Oct 13, 2022 at 4:59 AM Martijn Visser
> wrote:
>
> > Hi everyone,
> >
> > I would like to open a vote for dropping Gelly, which was discussed a
> long
> > time ago but never put
+1
On Thu, Oct 13, 2022 at 4:59 AM Martijn Visser
wrote:
> Hi everyone,
>
> I would like to open a vote for dropping Gelly, which was discussed a long
> time ago but never put to a vote [1].
>
> Voting will be open for at least 72 hours.
>
> Best regards,
>
>
Martijn Visser created FLINK-29668:
--
Summary: Remove Gelly
Key: FLINK-29668
URL: https://issues.apache.org/jira/browse/FLINK-29668
Project: Flink
Issue Type: Technical Debt
Hi everyone,
Happy to announce that the vote to drop Gelly has passed [1].
+1 Votes:
- Yun Gao (binding)
- Gyula Fóra (binding)
- Niels Basjes (binding)
- Konstantin Knauf (binding)
- Maximilian Michels (binding)
- Yu Li (binding)
- Sergey Nuyanzin (non-binding)
- Yun Tang (binding)
Best
+1 for dropping Gelly as a prerequisite for dropping deprecated DataSet API.
Apart from asking contributors to join the flink-ML development, I'm not sure
whether some old repo [1], which is already based on Flink's DataStream API,
also wants to join the migration guide.
cc @Vasia
[1] https
+1 (non-binding)
On Mon, Oct 17, 2022 at 5:50 AM Yun Gao
wrote:
> Hi Yu,
> Very thanks for the suggestions and I also strongly
> agree with that. Perhaps we could update the Gelly
> documentation pages to also express the information.
>
Hi Yu,
Very thanks for the suggestions and I also strongly
agree with that. Perhaps we could update the Gelly
documentation pages to also express the information.
Best,
Yun Gao
--
From:Yu Li
Send Time:2022 Oct. 16 (Sun.) 18:30
+1
Thanks for the clarification Martijn and Yun. Hopefully we can document
somewhere that there is a plan (maybe long term) to introduce a replacement
based on the new iteration framework introduced in flink-ml (based on
DataStream API) after dropping the old Gelly library, and let our users
know
t; > Hi everyone,
> > >
> > > I would like to open a vote for dropping Gelly, which was discussed a
> > long
> > > time ago but never put to a vote [1].
> > >
> > > Voting will be open for at least 72 hours.
> > >
> > > Best re
+1
Am Do., 13. Okt. 2022 um 10:56 Uhr schrieb Niels Basjes :
> +1
>
> On Wed, Oct 12, 2022 at 11:00 PM Martijn Visser
> wrote:
>
> > Hi everyone,
> >
> > I would like to open a vote for dropping Gelly, which was discussed a
> long
> > time ago b
+1
On Wed, Oct 12, 2022 at 11:00 PM Martijn Visser
wrote:
> Hi everyone,
>
> I would like to open a vote for dropping Gelly, which was discussed a long
> time ago but never put to a vote [1].
>
> Voting will be open for at least 72 hours.
>
> Best regards,
>
>
Hi all,
For the successor of the Gelly library, currently in flink-ml we have already
implemented a new iteration framework based on the DataStream API,
which is necessary for a graph processing framework. It could also provide
abilities like allowing for arbitrary states across rounds
Hi Yu,
The vote is for option 1, remove all code and documentation of Gelly. For
the current users, they can stay on a previous version of Flink which still
contains Gelly. Since Gelly (and the DataSet API) haven't been touched in
multiple releases, there's most likely no need for them to upgrade
Hi Martijn,
>From the last replies of the previous discussion, I could see there are
still users using Gelly that expressed their wish to somehow keep this
module [1] [2] [3]. Therefore, Before giving my vote, I'd like to
confirm what "Drop Gelly" exactly means. Does it mean that
+1
On Thu, 13 Oct 2022 at 04:56, Yun Gao wrote:
> +1
> Best,
> Yun Gao
> --
> From:Martijn Visser
> Send Time:2022 Oct. 13 (Thu.) 04:59
> To:dev
> Subject:[VOTE] Drop Gelly
> Hi everyone,
&g
+1
Best,
Yun Gao
--
From:Martijn Visser
Send Time:2022 Oct. 13 (Thu.) 04:59
To:dev
Subject:[VOTE] Drop Gelly
Hi everyone,
I would like to open a vote for dropping Gelly, which was discussed a long
time ago but never put to a vote [1
Hi everyone,
I would like to open a vote for dropping Gelly, which was discussed a long
time ago but never put to a vote [1].
Voting will be open for at least 72 hours.
Best regards,
Martijn
https://twitter.com/MartijnVisser82
https://github.com/MartijnVisser
[1] https://lists.apache.org
Hi everyone,
I'm reviving this really old discussion thread, but I just stumbled across
Gelly again and realized that this discussion never was finished.
I'll open up a vote thread for dropping the current DataSet based Gelly
library.
Best regards,
Martijn
On 2022/01/05 03:37:18 Yun Gao
Shunyang Li created FLINK-29578:
---
Summary: Multiple executions of `runVertexCentricIteration` cause
memory errors (flink gelly)
Key: FLINK-29578
URL: https://issues.apache.org/jira/browse/FLINK-29578
Hi,
Very thanks for initiating the discussion!
Also +1 to drop the current DataSet based Gelly library so that we could
finally drop the
legacy DataSet API.
For whether to keep the graph computing ability, from my side graph query /
graph computing and
chaining them with the preprocessing
becomes who can contribute and maintain this library.
Another (intermediate) solution might also be to find someone who can
migrate/move the current Gelly codebase to use Flink's DataStream API in
batch mode, so it wouldn't be using the DataSet API anymore. This has
recently also happened
Hi,
thanks Martijn for bringing it up for discussion. I think we could make the
discussion a little bit clearer by splitting it into two questions:
1. should Flink drop Gelly?
2. should Flink drop the graph computing?
The answer of the first question could be yes, since there have been
Hi Martijin,
Thanks for the feedback. I am not proposing to bundle the new graph
library with Alink. I am +1 for dropping the DataSet-based Gelly library,
but we probably need a new graph library in Flink for the possible
migration.
We haven't decided what to do yet and probably need more
Hi everyone,
We (team in seznam.cz) are actually using the Gelly library for batch
anomaly detection in our graphs. It will be very nice to somehow keep this
functionality, maybe in a separate repository. Is there any replacement?
Best,
Lukas
On Mon, Jan 3, 2022 at 2:20 PM Martijn Visser
Hi Zhipeng,
Good that you've reached out, I wasn't aware that Gelly is being used in
Alink. Are you proposing to write a new graph library as a successor of
Gelly and bundle that with Alink?
Best regards,
Martijn
On Tue, 4 Jan 2022 at 02:57, Zhipeng Zhang wrote:
> Hi everyone,
>
&g
Hi everyone,
Thanks for starting the discussion :)
We (Alink team [1]) are actually using part of the Gelly library to support
graph algorithms (connected component, single source shortest path, etc.)
for users in Alibaba Inc.
As DataSet API is going to be dropped, shall we also provide a new
Most of the inquiries I've had about Gelly in recent memory have been from
folks looking for a streaming solution, and it's only been a handful.
+1 for dropping Gelly
David
On Mon, Jan 3, 2022 at 2:41 PM Till Rohrmann wrote:
> I haven't seen any changes or requests to/for Gelly in ages. He
I haven't seen any changes or requests to/for Gelly in ages. Hence, I would
assume that it is not really used and can be removed.
+1 for dropping Gelly.
Cheers,
Till
On Mon, Jan 3, 2022 at 2:20 PM Martijn Visser wrote:
> Hi everyone,
>
> Flink is bundled with Gelly, a Graph API l
Hi everyone,
Flink is bundled with Gelly, a Graph API library [1]. This has been marked
as approaching end-of-life for quite some time [2].
Gelly is built on top of Flink's DataSet API, which is deprecated and
slowly being phased out [3]. It only works on batch jobs. Based on the
activity
wuguihu created FLINK-23260:
---
Summary: [DOCS]The link on page docs/libs/gelly/overview is failed
and 404 is returned
Key: FLINK-23260
URL: https://issues.apache.org/jira/browse/FLINK-23260
Project: Flink
Yu Li created FLINK-20052:
-
Summary: kafka/gelly pre-commit test failed due to process hang
Key: FLINK-20052
URL: https://issues.apache.org/jira/browse/FLINK-20052
Project: Flink
Issue Type: Bug
Chesnay Schepler created FLINK-19964:
Summary: Gelly ITCase stuck on Azure
Key: FLINK-19964
URL: https://issues.apache.org/jira/browse/FLINK-19964
Project: Flink
Issue Type: Bug
ly. I'm pulling in Aljoscha, Klou and Tison who worked on this
> > feature. I believe they can propose a fix for the problem.
> >
> > [1] https://issues.apache.org/jira/browse/FLINK-15116
> >
> > On Sun, Aug 2, 2020 at 11:28 AM Xia Rui wrote:
> >
> >&
, everyone.
I am using Flink-Gelly. I got an error when running the example code of
Gelly-example. I have reported the problem in Stackoverflow, and this is
the
link
(
https://stackoverflow.com/questions/63211746/error-with-flink-gelly-lastjob
executionresult-is-null-for-executionenvironment
<ht
correctly. I'm pulling in Aljoscha, Klou and Tison who worked on this
feature. I believe they can propose a fix for the problem.
[1] https://issues.apache.org/jira/browse/FLINK-15116
On Sun, Aug 2, 2020 at 11:28 AM Xia Rui wrote:
> Hello, everyone.
>
> I am using Flink-Gelly. I got an e
Hello, everyone.
I am using Flink-Gelly. I got an error when running the example code of
Gelly-example. I have reported the problem in Stackoverflow, and this is the
link
(https://stackoverflow.com/questions/63211746/error-with-flink-gelly-lastjob
executionresult-is-null-for-executionenvironment
Chesnay Schepler created FLINK-12851:
Summary: Add travis profile for gelly/kafka
Key: FLINK-12851
URL: https://issues.apache.org/jira/browse/FLINK-12851
Project: Flink
Issue Type
Calvin Han created FLINK-11595:
--
Summary: Gelly addEdge in certain circumstances still include
duplicate vertices.
Key: FLINK-11595
URL: https://issues.apache.org/jira/browse/FLINK-11595
Project: Flink
vinoyang created FLINK-10048:
Summary: Migrate module flink-gelly-examples to flink-examples and
rename it
Key: FLINK-10048
URL: https://issues.apache.org/jira/browse/FLINK-10048
Project: Flink
flora karniav created FLINK-8414:
Summary: Gelly performance seriously decreases when using the
suggested parallelism configuration
Key: FLINK-8414
URL: https://issues.apache.org/jira/browse/FLINK-8414
flora karniav created FLINK-8403:
Summary: Flink Gelly examples hanging without returning result
Key: FLINK-8403
URL: https://issues.apache.org/jira/browse/FLINK-8403
Project: Flink
Issue
Greg Hogan created FLINK-7276:
-
Summary: Gelly algorithm parameters
Key: FLINK-7276
URL: https://issues.apache.org/jira/browse/FLINK-7276
Project: Flink
Issue Type: Improvement
Greg Hogan created FLINK-7275:
-
Summary: Differentiate between normal and power-user cli options
in Gelly examples
Key: FLINK-7275
URL: https://issues.apache.org/jira/browse/FLINK-7275
Project: Flink
Greg Hogan created FLINK-7273:
-
Summary: Gelly tests with empty graphs
Key: FLINK-7273
URL: https://issues.apache.org/jira/browse/FLINK-7273
Project: Flink
Issue Type: Bug
Components
Greg Hogan created FLINK-7211:
-
Summary: Exclude Gelly javadoc jar from release
Key: FLINK-7211
URL: https://issues.apache.org/jira/browse/FLINK-7211
Project: Flink
Issue Type: Improvement
Greg Hogan created FLINK-7031:
-
Summary: Document Gelly examples
Key: FLINK-7031
URL: https://issues.apache.org/jira/browse/FLINK-7031
Project: Flink
Issue Type: New Feature
Components
Greg Hogan created FLINK-7023:
-
Summary: Remaining types for Gelly ValueArrays
Key: FLINK-7023
URL: https://issues.apache.org/jira/browse/FLINK-7023
Project: Flink
Issue Type: Sub-task
Greg Hogan created FLINK-7019:
-
Summary: Rework parallelism in Gelly algorithms and examples
Key: FLINK-7019
URL: https://issues.apache.org/jira/browse/FLINK-7019
Project: Flink
Issue Type: Sub
Greg Hogan created FLINK-7006:
-
Summary: Base class using POJOs for Gelly algorithms
Key: FLINK-7006
URL: https://issues.apache.org/jira/browse/FLINK-7006
Project: Flink
Issue Type: Sub-task
mingleizhang created FLINK-6991:
---
Summary: Inaccessible link under Gelly document
Key: FLINK-6991
URL: https://issues.apache.org/jira/browse/FLINK-6991
Project: Flink
Issue Type: Bug
Greg Hogan created FLINK-6648:
-
Summary: Transforms for Gelly examples
Key: FLINK-6648
URL: https://issues.apache.org/jira/browse/FLINK-6648
Project: Flink
Issue Type: Improvement
FlorianFan created FLINK-6393:
-
Summary: Add Evenly Graph Generator to Flink Gelly
Key: FLINK-6393
URL: https://issues.apache.org/jira/browse/FLINK-6393
Project: Flink
Issue Type: New Feature
Eron Wright created FLINK-6391:
---
Summary: fix build for scala 2.11 (gelly-examples)
Key: FLINK-6391
URL: https://issues.apache.org/jira/browse/FLINK-6391
Project: Flink
Issue Type: Bug
Greg Hogan created FLINK-6382:
-
Summary: Support all numeric types for generated graphs in Gelly
examples
Key: FLINK-6382
URL: https://issues.apache.org/jira/browse/FLINK-6382
Project: Flink
vishnu viswanath created FLINK-6372:
---
Summary: change-scala-version.sh does not change version for
flink-gelly-examples
Key: FLINK-6372
URL: https://issues.apache.org/jira/browse/FLINK-6372
Project
Greg Hogan created FLINK-6358:
-
Summary: Write job details for Gelly examples
Key: FLINK-6358
URL: https://issues.apache.org/jira/browse/FLINK-6358
Project: Flink
Issue Type: Improvement
Greg Hogan created FLINK-6195:
-
Summary: Move gelly-examples jar from opt to examples
Key: FLINK-6195
URL: https://issues.apache.org/jira/browse/FLINK-6195
Project: Flink
Issue Type: Sub-task
Gelly "commonly
applicable". (The MST algorithm need to mark edges during the iteration and
I think there surely be other algorithms more complicated than that)
As for the intermediate caching problem, I think it should be users
themselves to decide when to cache the results and when to re
Flink’s stable API provides the frameworks (DataStream and DataSet). On top of
these frameworks Gelly provides additional models for iterative algorithms, but
there are algorithms such as Minimum Spanning Tree which do not easily map to
these models (in this instance requiring nested iterations
ussion.
>
> I was expecting more changes from the recent discussion on restructuring
> the project, in particular regarding the libraries. Gelly has always
> collected algorithms and I have personally taken an algorithms-first
> approach for contributions. Is that manageable and maintain
lly.
> It's just like a textbook that can not cover all the existing algorithms
> (even if we can). Just representative and commonly used ones will be
> enough. After all, Gelly is mainly designed for providing a framework
> rather than an algorithm library. Besides, it seems that Gelly's API is
Greg Hogan created FLINK-5910:
-
Summary: Framework for Gelly examples
Key: FLINK-5910
URL: https://issues.apache.org/jira/browse/FLINK-5910
Project: Flink
Issue Type: Sub-task
Hi Greg,
On 24 February 2017 at 18:09, Greg Hogan <c...@greghogan.com> wrote:
> Thanks, Vasia, for starting the discussion.
>
> I was expecting more changes from the recent discussion on restructuring
> the project, in particular regarding the libraries. Gelly has always
>
Thanks, Vasia, for starting the discussion.
I was expecting more changes from the recent discussion on restructuring
the project, in particular regarding the libraries. Gelly has always
collected algorithms and I have personally taken an algorithms-first
approach for contributions
Hello squirrels,
this is a discussion thread to organize the Gelly component development for
release 1.3 and discuss longer-term plans for the library.
I am hoping that with time-based releases, we can distribute the load for
PR reviewing and make better use of our time, and also point
r at Onzichtbaar Developers
>
>
> On Tue, Feb 7, 2017 at 3:41 PM, Wouter Ligtenberg <wou...@onzichtbaar.net>
> wrote:
>
> > Hello,
> >
> > For my master thesis i have created Tink, abrevated for temporal Flink,
> > It's a library that's supposed to work o
Hello,
For my master thesis i have created Tink, abrevated for temporal Flink,
It's a library that's supposed to work on top of Flink in relation with
Gelly to do temporal graph analytics.
I've worked on this project for the past 6 months as part of my master
thesis at the university of Eindhoven
y master thesis i have created Tink, abrevated for temporal Flink,
> It's a library that's supposed to work on top of Flink in relation with
> Gelly to do temporal graph analytics.
> I've worked on this project for the past 6 months as part of my master
> thesis at the university o
wouter ligtenberg created FLINK-5161:
Summary: accepting NullValue for VV in Gelly examples and GSA
Key: FLINK-5161
URL: https://issues.apache.org/jira/browse/FLINK-5161
Project: Flink
wouter ligtenberg created FLINK-5152:
Summary: accepting NullValue for EV in Gelly examples
Key: FLINK-5152
URL: https://issues.apache.org/jira/browse/FLINK-5152
Project: Flink
Issue
Greg Hogan created FLINK-4936:
-
Summary: Operator names for Gelly inputs
Key: FLINK-4936
URL: https://issues.apache.org/jira/browse/FLINK-4936
Project: Flink
Issue Type: Improvement
;dev@flink.apache.org" <dev@flink.apache.org>
Betreff: Re: Re: Re: Flink Gelly
Hi,
the exception
> java.lang.RuntimeException: Memory ran out. Compaction failed.
says that the hash table ran out of memory. Gelly is implemented on top of
Flink's DataSet API.
So this would rather be a
Hi,
the exception
> java.lang.RuntimeException: Memory ran out. Compaction failed.
says that the hash table ran out of memory. Gelly is implemented on top of
Flink's DataSet API.
So this would rather be a problem with DataSet than Gelly.
I think Vasia is right about the memory configurat
an
internal
problem with Gelly.
Best,
Dennis
Gesendet: Freitag, 07. Oktober 2016 um 12:29 Uhr
Von: "Vasiliki Kalavri" <vasilikikala...@gmail.com>
An: dev@flink.apache.org
Betreff: Re: Re: Flink Gelly
Hi Dennis,
On 7 October 2016 at 11:29, <d...@web.de> wrote:
> Hi V
ss it has something
> to do with Gelly
> or with the properties.
>
> The configured memory is default. I did not change it because I thought
> that flink is not the problem
> but I might be wrong.
>
The default configured memory is only 512MB. If you have 16GB but you
don't let Flink
Hi Vasia,
thanks for your reply.
Currently I am testing it on my normal workstation (16GB Ram) but I also tried
it on out cluster.
Both are failing at the same amount of nodes, so I guess it has something to do
with Gelly
or with the properties.
The configured memory is default. I did
at 13:29, <d...@web.de> wrote:
>
> Dear ladies and gentlemen,
>
> I got a problem using Gelly in Flink. Currently I am loading a Virtuoso
> Graph into
> Flink's Gelly and I want to analyze it for the different paths one can
> take to link
> the differe
Dear ladies and gentlemen,
I got a problem using Gelly in Flink. Currently I am loading a Virtuoso Graph
into
Flink's Gelly and I want to analyze it for the different paths one can take to
link
the different nodes. Therefore I am using the ScatterGatherIteration.
However, my code just
t;>>> vertices.print();
>>>>> System.out.println("Edges:\n");
>>>>> edges.print();
>>>>>
>>>>> Graph<Long, Summarization.VertexValue,
>>>>>
>>>> Sum
___
Best regards,
Olga Golovneva
On Thu, Sep 15, 2016 at 9:16 AM, Till Rohrmann <trohrm...@apache.org>
wrote:
Hi Olga,
can you provide us with a little bit more details about the problem.
The
full stack trace of the exception and the program you're trying to run
would be helpful
[]{3L, 5L, 5.0},
> > > new Object[]{3L, 6L, 2.0},
> > > new Object[]{4L, 5L, 1.0},
> > > new Object[]{5L, 6L, 4.0}
> > > };
> > > List<Edge<Long, Double>> edgeList = new Linke
bject[]{1L, 1L},
> new Object[]{2L, 1L},
> new Object[]{3L, 5L},
> new Object[]{4L, 5L},
> new Object[]{5L, 5L}
> };
> List<Vertex<Long, Long>> vertexList = new LinkedList<Vertex<Long,
>
Rohrmann <trohrm...@apache.org> wrote:
> Hi Olga,
>
> can you provide us with a little bit more details about the problem. The
> full stack trace of the exception and the program you're trying to run
> would be helpful.
>
> Cheers,
> Till
>
> On Wed, Sep 1
gt; Do you know if there is an example (besides ITCase) of usage of
> Summarization Library in Gelly? I'm having some problems trying to use it
> in my code. Particularly, I cannot print output edges ( it throws the
> following exception: Exception in thread "main"
> org.apache.flink
Hi devs,
Do you know if there is an example (besides ITCase) of usage of
Summarization Library in Gelly? I'm having some problems trying to use it
in my code. Particularly, I cannot print output edges ( it throws the
following exception: Exception in thread "
Greg Hogan created FLINK-4571:
-
Summary: Configurable little parallelism in Gelly drivers
Key: FLINK-4571
URL: https://issues.apache.org/jira/browse/FLINK-4571
Project: Flink
Issue Type
Vasia Kalavri created FLINK-4522:
Summary: Gelly link broken in homepage
Key: FLINK-4522
URL: https://issues.apache.org/jira/browse/FLINK-4522
Project: Flink
Issue Type: Bug
Greg Hogan created FLINK-4217:
-
Summary: Gelly drivers should read CSV values as strings
Key: FLINK-4217
URL: https://issues.apache.org/jira/browse/FLINK-4217
Project: Flink
Issue Type
Vasia Kalavri created FLINK-4204:
Summary: Clean up gelly-examples
Key: FLINK-4204
URL: https://issues.apache.org/jira/browse/FLINK-4204
Project: Flink
Issue Type: Improvement
Greg Hogan created FLINK-4106:
-
Summary: Restructure Gelly docs
Key: FLINK-4106
URL: https://issues.apache.org/jira/browse/FLINK-4106
Project: Flink
Issue Type: Improvement
Components
Greg Hogan created FLINK-4107:
-
Summary: Restructure Gelly docs
Key: FLINK-4107
URL: https://issues.apache.org/jira/browse/FLINK-4107
Project: Flink
Issue Type: Improvement
Components
Greg Hogan created FLINK-4105:
-
Summary: Restructure Gelly docs
Key: FLINK-4105
URL: https://issues.apache.org/jira/browse/FLINK-4105
Project: Flink
Issue Type: Improvement
Components
Greg Hogan created FLINK-4104:
-
Summary: Restructure Gelly docs
Key: FLINK-4104
URL: https://issues.apache.org/jira/browse/FLINK-4104
Project: Flink
Issue Type: Improvement
Components
Greg Hogan created FLINK-3853:
-
Summary: Reduce object creation in Gelly utility mappers
Key: FLINK-3853
URL: https://issues.apache.org/jira/browse/FLINK-3853
Project: Flink
Issue Type
Greg Hogan created FLINK-3845:
-
Summary: Gelly allows duplicate vertices in Graph.addVertices
Key: FLINK-3845
URL: https://issues.apache.org/jira/browse/FLINK-3845
Project: Flink
Issue Type: Bug
Hi all,
as promised, I have updated the Gelly roadmap [1].
Below, I am describing and reasoning about the changes I made. Please, let
me know whether you agree and if you have any other ideas for further
improvements and feature additions.
*1. Operators for highly skewed graphs*:
I have removed
1 - 100 of 243 matches
Mail list logo
