Overview

The Connected Component algorithm identifies the connected components in a graph, which is the essential indicator to examine the connectivity and topology characteristics of the graph.

The number of connected components in a graph can serve as a coarse-grained metering method. If the number of connected components remains unchanged after certain operations or modifications to the graph, it suggests that the macroscopic connectivity and topology characteristics of the graph have not been altered significantly.

This information is valuable in various graph analysis scenarios. For example, in social networks, if the number of connected components remains the same over time, it implies that the overall connectivity patterns and community structures within the network have not experienced substantial changes.

Concepts

Connected Component

A connected component is a maximal subset of nodes in a graph where all nodes in that subset are reachable from one another by following edges in the graph. A maximal subset means that no additional nodes can be added to the subset without breaking the connectivity requirement.

The number of connected components in a graph indicates the level of disconnectedness or the presence of distinct subgraphs within the overall graph. A graph that has exactly one component, consisting of the whole graph, is called a connected graph.

Weakly and Strongly Connected Component

There are two important concepts related to connected component: weakly connected component (WCC) and strongly connected component (SCC):

• A WCC refers to a subset of nodes in a directed or undirected graph where there exists a path between any pair of nodes, regardless of the direction of the edges.
• A SCC is a subset of nodes in a directed graph where there is a directed path between every pair of nodes. In other words, for any two nodes u and v in a SCC, there is a directed path from u to v and also from v to u. In directed path, all edges have the same direction.

This example shows the 3 strongly connected components and 2 weakly connected components of a graph. The number of SCCs in a graph is always equal to or greater than the number of WCCs, as determining a SCC requires stricter conditions compared to a WCC.

Considerations

• Each isolated node in the graph is a connected component, and it is both a strongly connected component and a weakly connected component.

Example Graph

To create this graph:

// Runs each row separately in order in an empty graphset
create().node_schema("member").edge_schema("helps")
insert().into(@member).nodes([{_id:"Mike"}, {_id:"Cathy"}, {_id:"Anna"}, {_id:"Joe"}, {_id:"Sam"}, {_id:"Bob"}, {_id:"Bill"}, {_id:"Alice"}])
insert().into(@helps).edges([{_from:"Cathy", _to:"Mike"}, {_from:"Anna", _to:"Sam"}, {_from:"Anna", _to:"Joe"}, {_from:"Joe", _to:"Bob"}, {_from:"Bob", _to:"Joe"},{_from:"Bob", _to:"Bill"}, {_from:"Bill", _to:"Alice"}, {_from:"Bill", _to:"Anna"}, {_from:"Alice", _to:"Anna"}])

Running on HDC Graphs

Creating HDC Graph

To load the entire graph to the HDC server hdc-server-1 as hdc_cc:

CALL hdc.graph.create("hdc-server-1", "hdc_cc", {
  nodes: {"*": ["*"]},
  edges: {"*": ["*"]},
  direction: "undirected",
  load_id: true,
  update: "static",
  query: "query",
  default: false
})

hdc.graph.create("hdc_cc", {
  nodes: {"*": ["*"]},
  edges: {"*": ["*"]},
  direction: "undirected",
  load_id: true,
  update: "static",
  query: "query",
  default: false
}).to("hdc-server-1")

Parameters

Algorithm name: connected_component

In the results of this algorithm, each connected component is represented by the same community_id， which corresponds to the _uuid value of one of its nodes.

File Writeback

This algorithm can generate three files:

CALL algo.connected_component.write("hdc_cc", {
  params: {
    return_id_uuid: "id",
    cc_type: 1
  },
  return_params: {
    file: {
      filename_community_id: "f1.txt",
      filename_ids: "f2.txt",
      filename_num: "f3.txt"
    }
  }
})

algo(connected_component).params({
  project: "hdc_cc",
  return_id_uuid: "id",
  cc_type: 1  
}).write({
  file: {
      filename_community_id: "f1.txt",
      filename_ids: "f2.txt",
      filename_num: "f3.txt"
  }
})

Result:

_id,community_id
Alice,0
Cathy,1
Anna,0
Bob,0
Joe,0
Bill,0
Mike,1
Sam,0

community_id,_ids
0,Alice;Anna;Bob;Joe;Bill;Sam;
1,Cathy;Mike;

community_id,count
0,6
1,2

DB Writeback

Writes the community_id values from the results to the specified node property. The property type is uint32.

CALL algo.connected_component.write("hdc_cc", {
  params: {},
  return_params: {
    db: {
      property: "wcc_id"
    }
  }
})

algo(connected_component).params({
  project: "hdc_cc"
}).write({
  db: {
    property: "wcc_id"
  }
})

Stats Writeback

CALL algo.connected_component.write("hdc_cc", {
  params: {},
  return_params: {
    stats: {}
  }
})

algo(connected_component).params({
  project: "hdc_cc"
}).write({
  stats: {}
})

Result:

Full Return

CALL algo.connected_component("hdc_cc", {
  params: {
    return_id_uuid: "id",
    cc_type: 2
  },
  return_params: {}
}) YIELD r
RETURN r

exec{
  algo(connected_component).params({
    return_id_uuid: "id",
    cc_type: 2
  }) as r
  return r
} on hdc_cc

Result:

Stream Return

This Stream Return supports two modes:

CALL algo.connected_component("hdc_cc", {
  params: {
    return_id_uuid: "id",
    cc_type: 2
  },
  return_params: {
  	stream: {}
  }
}) YIELD r
RETURN r

exec{
  algo(connected_component).params({
    return_id_uuid: "id",
    cc_type: 2
  }).stream() as r
  return r
} on hdc_cc

Result:

CALL algo.connected_component("hdc_cc", {
  params: {
    return_id_uuid: "id",
    cc_type: 2,
    order: "asc"
  },
  return_params: {
    stream: {
      mode: 2
    }
  }
}) YIELD r
RETURN r

exec{
  algo(connected_component).params({
    return_id_uuid: "id",
    cc_type: 2,
    order: "asc"
  }).stream({
    mode: 2
  }) as r
  return r
} on hdc_cc

Result:

Stats Return

CALL algo.connected_component("hdc_cc", {
  params: {},
  return_params: {
  	stats: {}
  }
}) YIELD wcc_count
RETURN wcc_count

exec{
  algo(connected_component).params().stats() as wcc_count
  return wcc_count
} on hdc_cc

Result:

Running on Distributed Projections

Creating Distributed Projection

To project the entire graph to its shard servers as dist_wcc:

create().project("dist_wcc", {
  nodes: {"*": ["*"]}, 
  edges: {"*": ["*"]},
  direction: "undirected",
  load_id: true
})

Parameters

Algorithm name: wcc

The algorithm does not require any parameters.

The distributed version of this algorithm supports identifying only weakly connected components (WCC) in the graph. In the results of this algorithm, each connected component is represented by the same community_id.

File Writeback

CALL algo.wcc.write("dist_wcc", {
  params: {},
  return_params: {
    file: {
      filename: "wcc"
    }
  }
})

algo(wcc).params({
  project: "dist_wcc"
}).write({
  file: {
    filename: "wcc"
  }
})

Result:

_id,community_id
Anna,4827860999564427272
Joe,4827860999564427272
Sam,4827860999564427272
Mike,6413128068398841858
Bill,4827860999564427272
Cathy,6413128068398841858
Alice,4827860999564427272
Bob,4827860999564427272

DB Writeback

Writes the community_id values from the results to the specified node property. The property type is uint64.

CALL algo.wcc.write("dist_wcc", {
  params: {},
  return_params: {
    db: {
      property: "wcc_id"
    }
  }
})

algo(wcc).params({
  project: "dist_wcc"
}).write({
  db: {
    property: "wcc_id"
  }
})