Skip to content

Name projected-graph parameter in GDS signatures - #127

Merged
adsharma merged 4 commits into
mainfrom
fix/gds-graph-name-signature
Oct 16, 2026
Merged

adsharma merged 4 commits into
mainfrom
fix/gds-graph-name-signature

Conversation

@adsharma

Copy link
Copy Markdown
Contributor

Companion to LadybugDB/ladybug#1265 for LadybugDB/ladybug#1223.

All GDS table functions take a projected-graph name yet registered a bare ANY parameter, so e.g. CALL page_rank('v','e') reported the unhelpful Expected: (ANY). This registers STRING with parameterNames {"graph_name"} (plus LIST "sources" for the PPR extra arg), so failures read Expected: (graph_name STRING) with a CALL PROJECT_GRAPH(...) hint from core.

All GDS table functions take a projected-graph name yet registered a
bare ANY parameter, so arity mismatches reported the unhelpful
'Expected: (ANY)'. Register STRING with parameterNames {"graph_name"}
(plus LIST "sources" for the PPR extra arg) so failures read
'Expected: (graph_name STRING)'.

Pairs with LadybugDB/ladybug#1265, which adds parameterNames support
and a CALL PROJECT_GRAPH(...) hint to the core function-match error.
Renders as (graph_name STRING,sources INT64[]) in signatures and
function-match errors.
@adsharma
adsharma added this pull request to stack #131 October 16, 2026 15:52
CALLs with a LIST-typed extra (GDS_PPR sources) fail to bind: the
binder builds input LogicalTypes from the declared LogicalTypeIDs and
a bare LIST ID carries no child info. Set inferInputTypes when the
descriptor takes extra args so the nested type comes from the
CALL-site argument instead.
@adsharma
adsharma merged commit d275ccd into main Oct 16, 2026
2 checks passed
@adsharma
adsharma deleted the fix/gds-graph-name-signature branch October 16, 2026 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant