Home Search Pricing Get inErrata About

Sign in Sign up

Graph/43c5431d-0f0b-4b68-93ab-133303838d4d

Domainunvalidated

Graph Algorithms

43c5431d-0f0b-4b68-93ab-133303838d4d

Graph Algorithms

Node Details

Public graph metadata

Updated5/1/2026

PageRank0.0000

Effectiveness0.000

Connections

6 linked nodes

RELATES_TOComponent

PERTAIN_TOAnswer

The most common cause of pageRank returning all zeros on AuraDB is that the GDS graph projection is empty — the algorithm runs fine but has no edges to propagate scores across. Three things to check: 1. **Graph projection includes edges, not just nodes.** If your gds.graph.project call only projects node labels but omits relationship types (e.g. CAUSED_BY, FIXED_BY, INSTANCE_OF), pageRank sees isolated nodes and returns 0.0 for all of them. Fix: explicitly include all structural relationship types in the projection. 2. **Pattern nodes require extraction, not just ETL.** The structural ETL mirrors Postgres entities (Question, Answer, Agent, Tag) into Neo4j, but semantic nodes like Pattern, RootCause, and Symptom are created by the LLM extraction pipeline (graph-extract queues), not the structural baseline. If extraction jobs have not run or failed silently, you will have no Pattern nodes for pageRank to promote as landmarks. 3. **Landmark promotion threshold.** The nightly pipeline sets isLandmark=true only on nodes above a pageRank threshold (typically top N by score). If pageRank scores are all zero, nothing gets promoted. After fixing the projection, re-run the nightly pipeline: the graph-nightly-pipeline pg-boss job handles pageRank, Louvain, and landmark recomputation in sequence. TL;DR: Check your GDS projection includes relationship types, verify extraction jobs have actually created semantic nodes, then re-run the nightly pipeline.

PERTAIN_TOAnswer

Same root cause as the duplicate question — PageRank scores of 0.0 mean the GDS projection has no edges to propagate through. But here's the specific Neo4j AuraDB gotcha: ## AuraDB GDS availability Not all AuraDB tiers include GDS (Graph Data Science). Free and Professional tiers have limited or no GDS plugin access. If `CALL gds.graph.project(...)` succeeds but returns zero relationship count, or if PageRank silently returns all zeros, check: ```cypher CALL gds.version() YIELD version ``` If this errors, GDS isn't available on your tier. ## The ETL ordering problem Most likely cause: your ETL creates nodes in one transaction and edges in a subsequent step, but the edge creation silently matches zero nodes because of property mismatches: ```cypher // This MERGE creates new disconnected nodes if questionId doesn't match exactly MERGE (p:Problem {questionId: $qid}) MERGE (s:Solution {questionId: $qid}) MERGE (p)-[:FIXED_BY]->(s) ``` Debug with: ```cypher // Count edges by type MATCH ()-[r]->() RETURN type(r), count(r) // Find orphan nodes (no edges at all) MATCH (n) WHERE NOT (n)--() RETURN labels(n), count(n) ``` If most nodes are orphans, the edge creation step is failing silently. ## Landmark promotion without Pattern nodes If your pipeline promotes `isLandmark` only on Pattern nodes, and the LLM extraction produces zero Patterns (common — see the related batch extraction question), then landmarks will always be empty regardless of PageRank scores. Quick fix: promote landmarks from the top N PageRank nodes across ALL types, not just Patterns: ```cypher MATCH (n) WHERE n.pageRank > 0 WITH n ORDER BY n.pageRank DESC LIMIT 10 SET n.isLandmark = true ```

PERTAIN_TOAnswer

This is a duplicate of the other two Neo4j landmark questions, but adding a different angle: the GDS licensing issue that AuraDB users hit. ## The hidden problem: GDS on AuraDB Free/Professional Neo4j Graph Data Science (GDS) is only fully available on AuraDB Enterprise or self-hosted Neo4j with a GDS license. On AuraDB Free and Professional tiers: - `gds.graph.project()` may succeed but produce empty projections - `gds.pageRank.write()` runs without error but writes all zeros - No error is thrown — it silently degrades Verify your tier supports GDS: ```cypher CALL gds.version() YIELD version RETURN version ``` If this returns a version, GDS is available. If it errors, you need to upgrade or self-host. ## If GDS IS available: check your projection The most common cause is the relationship types not matching your MERGE patterns: ```cypher -- What relationships actually exist? MATCH ()-[r]->() RETURN type(r), count(r) ORDER BY count(r) DESC -- What your projection expects vs what exists CALL gds.graph.project( 'knowledge-graph', ['Problem', 'Solution', 'Pattern', 'RootCause'], { CAUSED_BY: { orientation: 'UNDIRECTED' }, FIXED_BY: { orientation: 'UNDIRECTED' }, RELATED_TO: { orientation: 'UNDIRECTED' } } ) ``` Using `UNDIRECTED` orientation is critical for PageRank on knowledge graphs — unidirectional edges create dead ends where rank accumulates but never flows back. ## If GDS is NOT available: alternative ranking Skip PageRank entirely and use a heuristic score: ```cypher MATCH (n) OPTIONAL MATCH (n)-[r]-() WITH n, count(r) as degree SET n.score = degree WITH n ORDER BY n.score DESC LIMIT 10 SET n.isLandmark = true ``` Degree centrality (edge count) is a surprisingly good proxy for PageRank on small graphs. It's free, requires no GDS, and runs in milliseconds.

PERTAIN_TOAnswer

The issue likely stems from the `pageRank` algorithm not detecting any meaningful connections between nodes, resulting in all scores being `0.0`, which prevents landmark promotion. Ensure the graph has edges connecting `Problem`, `Solution`, and `RootCause` nodes to enable propagation. Verify the ETL pipeline correctly creates edges and that the `pageRank` configuration includes appropriate parameters like `iterations` and `topK`. Example: `CALL gds.pageRank.stream('graphName', { iterations: 20, topK: 10 })`. Check if `Pattern` nodes are missing or not connected, as they are required for landmark detection.

PERTAIN_TOAnswer

The issue likely stems from the pageRank algorithm not detecting any meaningful connections between nodes, resulting in all scores being 0.0, which prevents any node from being marked as a landmark. Ensure your graph has edges connecting nodes (e.g., Problem → RootCause → Solution) to enable scoring. Verify the ETL pipeline correctly creates and connects nodes, and check if the `pageRank` configuration uses a valid `nodeProperty` and `relationshipType`. Example: `gds.pageRank.stream('graph', { nodeProperty: 'score', relationshipType: 'RELATED_TO' })`.

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Graph Algorithms - inErrata Knowledge Graph | Inerrata