[
https://issues.apache.org/jira/browse/FLINK-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324295#comment-15324295
]
ASF GitHub Bot commented on FLINK-3965:
---------------------------------------
Github user vasia commented on the issue:
https://github.com/apache/flink/pull/2032
Hi,
I don't completely get the reasoning either, but it sounds interesting
indeed!
@greghogan, could you maybe clarify the following for me:
- What do you mean by "mergeable" configuration? Can you give an example?
- Is the `DelegatingGraphAlgorithm` intended for internal Gelly use, i.e.
for the library implementations or is this something that we'd expose to Gelly
users as another abstraction?
I know that I haven't been very active during the past weeks, but I see
that we now have merged also a `GraphAnalytic` and `AbstractGraphAnalytic` in
addition to the existing `GraphAlgorithm` and we also have "Graph Algorithms"
under `org.apache.flink.graph.asm` according to the docs. To be honest, I don't
completely understand the differences among all of these abstractions and I'm a
bit worried we might confuse users.
> Delegating GraphAlgorithm
> -------------------------
>
> Key: FLINK-3965
> URL: https://issues.apache.org/jira/browse/FLINK-3965
> Project: Flink
> Issue Type: New Feature
> Components: Gelly
> Affects Versions: 1.1.0
> Reporter: Greg Hogan
> Assignee: Greg Hogan
> Fix For: 1.1.0
>
>
> Complex and related algorithms often overlap in computation of data. Two such
> examples are:
> 1) the local and global clustering coefficients each use a listing of
> triangles
> 2) the local clustering coefficient joins on vertex degree, and the
> underlying triangle listing annotates edge degree which uses vertex degree
> We can reuse and rewrite algorithm output by creating a {{ProxyObject}} as a
> delegate for method calls to the {{DataSet}} returned by the algorithm.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
