Skip to main content

In Degrees All

SQL function: cugraph_in_degrees_all

Compute in-degree for every vertex.

Signature

cugraph_in_degrees_all(table_name [, src_col, dst_col [, weight_col [, options_json]]])

Allowed argument counts: 1, 3, 4, 5.

Quickstart

SELECT * FROM cugraph_in_degrees_all('target_edges')

Positional arguments

ArgumentTypeRequiredDefaultNotes
table_nameUtf8yes
src_colUtf8nosrc
dst_colUtf8nodst
weight_colUtf8|nullnoaccepted as an edge-column binding; native algorithm execution does not consume weights; semantic effect: none for this algorithm
options_jsonUtf8no

JSON options

This algorithm has no algorithm-specific options.

Graph construction options

Shared by all cuGraph functions, shown here with this function's defaults. The construction_policy option controls whether Nexus requests Python cuGraph-compatible edge normalization or bypasses it for raw libcugraph-style construction; see graph construction options for the full policy guide.

OptionTypeDefaultConstraintsDescription
construction_policyUtf8"python_cugraph"one of "python_cugraph", "raw_libcugraph"Edge-list construction semantics used before calling libcugraph.
directedBooleantrueWhether graph construction treats edges as directed.
renumberBooleantrueWhether graph construction may renumber external vertex identifiers internally.

Output schema

ColumnTypeNullableDescription
vertexInt64noVertex whose in-degree count is reported.
in_degreeInt64noNumber of incoming edges for the vertex.
note

These are the generic registry schemas. Run cugraph_validate_call for the concrete, table-specific output schema of a particular call.

Examples

This example runs on the citation network demo dataset.

In-graph citations vs. what the metadata claims

papers.n_citation is AMiner's global citation count; in_degree counts only edges present in this corpus. Joining the two measures how much of each paper's audience lies outside the dataset:

SELECT p.year, d.in_degree AS in_graph, p.n_citation AS reported,
p.n_citation - d.in_degree AS outside,
p.title AS paper
FROM cugraph_in_degrees_all('citation_edges', 'src', 'dst') d
JOIN papers p ON p.paper_id = d.vertex
ORDER BY d.in_degree DESC
LIMIT 5;
yearin_graphreportedoutsidepaper
200422,89235,54112,649Distinctive Image Features from Scale-Invariant Keypoints
201119,66231,04711,385LIBSVM: A library for support vector machines
198917,20744,17526,968Genetic algorithms in search, optimization, and machine learning
199616,57942,43725,858Fuzzy sets
200115,04834,74119,693Random Forests

SIFT is the most-cited paper within the corpus. Older cross-disciplinary classics (genetic algorithms, fuzzy sets) show the biggest gap — more than half their citations come from fields this CS-centric corpus doesn't cover.

Limitations & notes

  • dry-run validates table resolution, column presence, static dtypes, and options only
  • dry-run does not scan edge data, construct a graph, or prove source-vertex existence

Validate before running

Always dry-run a call before executing it. Validation checks the function, table, columns, dtypes, and options without touching the GPU:

SELECT * FROM cugraph_validate_call(
'cugraph_in_degrees_all',
'your_edges_table',
'{"src_col":"src","dst_col":"dst"}'
);

See Discovery & validation for the full cugraph_validate_call contract.