[
https://issues.apache.org/jira/browse/MADLIB-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050948#comment-16050948
]
Nandish Jayaram commented on MADLIB-1071:
-----------------------------------------
Suggesting some minor changes to the interface, considering the JIRA for
grouping support for
this algorithm (https://issues.apache.org/jira/browse/MADLIB-1083).
{code:sql}
SELECT madlib.weakly_connected_components(
vertex_table, – Vertex table
vertex_id, – Vertix id column (NULL means use default naming)
edge_table, – Edge table
edge_args, – Edge arguments (NULL means use default naming)
out_table, – Output table of connected components
grouping_col); -- Comma separated column names to group on
-- (DEFAULT = NULL, no grouping)
{code}
> Graph - weakly connect components
> ---------------------------------
>
> Key: MADLIB-1071
> URL: https://issues.apache.org/jira/browse/MADLIB-1071
> Project: Apache MADlib
> Issue Type: New Feature
> Components: Module: Graph
> Reporter: Frank McQuillan
> Assignee: Rashmi Raghu
> Fix For: v1.12
>
>
> Story
> As a MADlib developer, I want to implement weakly connected components (ref
> [0]) in an efficient and scaleable way.
> Acceptance
> 1) Interface defined
> 2) Design document updated
> 3) Documentation and on-line help
> 4) IC and functional tests
> 5) Scale tests
> References
> [0] https://en.wikipedia.org/wiki/Connectivity_(graph_theory)
> "A directed graph is called weakly connected if replacing all of its directed
> edges with undirected edges produces a connected (undirected) graph."
> [1] Grails paper
> http://pages.cs.wisc.edu/~jignesh/publ/Grail.pdf
> [2] Grails deck
> http://pages.cs.wisc.edu/~jignesh/publ/Grail-slides.pdf
> [3] Grails repo with page rank example
> https://github.com/UWQuickstep/Grail
> https://github.com/UWQuickstep/Grail/blob/master/analytics/wcc.sql
> (weakly connected components implementation)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
