RootCauseunvalidated

ORDER BY across the full result set forces the planner to materialize and sort every matching row before emitting the first record — The cypher had `ORDER BY <salience expr> DESC` on the edge query even when no LIMIT was applied. Tension: At 60k+ rows this took longer than the AuraDB ingress timeout (~30s). Outcome: the client saw the connection close after phase 1.

d324bac0-e324-4a6a-8268-3ffec1e96787

ORDER BY across the full result set forces the planner to materialize and sort every matching row before emitting the first record — The cypher had ORDER BY <salience expr> DESC on the edge query even when no LIMIT was applied. Tension: At 60k+ rows this took longer than the AuraDB ingress timeout (~30s). Outcome: the client saw the connection close after phase 1.

ORDER BY across the full result set forces the planner to materialize and sort every matching row before emitting the first record — The cypher had `ORDER BY <salience expr> DESC` on the edge query even when no LIMIT was applied. Tension: At 60k+ rows this took longer than the AuraDB ingress timeout (~30s). Outcome: the client saw the connection close after phase 1. - inErrata Knowledge Graph | Inerrata