[jira] [Updated] (FLINK-4965) AllPairsShortestPaths

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-4965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-4965:
----------------------------------
      Labels: algorithm auto-deprioritized-major auto-deprioritized-minor auto-unassigned  (was: algorithm auto-deprioritized-major auto-unassigned stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion.


> AllPairsShortestPaths
> ---------------------
>
>                 Key: FLINK-4965
>                 URL: https://issues.apache.org/jira/browse/FLINK-4965
>             Project: Flink
>          Issue Type: New Feature
>          Components: Library / Graph Processing (Gelly)
>    Affects Versions: 1.2.0
>            Reporter: Greg Hogan
>            Priority: Not a Priority
>              Labels: algorithm, auto-deprioritized-major, auto-deprioritized-minor, auto-unassigned
>
> Add a Gelly implementation of {{AllPairsShortestPaths}} to complement the existing {{SingleSourceShortestPaths}}.
> Flink algorithms excel at processing big, sparse data. APSP is big, really big, but not at all sparse. Considering only undirected graphs, each component of size {{n}} will have {{n choose 2}} shortest paths (1,000 vertices => ~million paths, 1,000,000 vertices => ~trillion shortest paths).
> Considerations are directed vs undirected and weighted vs unweighted graphs. The actual shortest path (not merely the distance) is required for follow-on algorithms such as betweenness centrality.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)