Skip to content

feat: add data-model/relationship-candidates endpoint spec#153

Open
wemrysi wants to merge 2 commits into
masterfrom
feature/cross-source-relationship-candidates
Open

feat: add data-model/relationship-candidates endpoint spec#153
wemrysi wants to merge 2 commits into
masterfrom
feature/cross-source-relationship-candidates

Conversation

@wemrysi
Copy link
Copy Markdown
Contributor

@wemrysi wemrysi commented May 14, 2026

Adds a GET /data-model/relationship-candidates?pipeline=<id>&sources=<s1>,<s2>,...,<sN> endpoint for retrieving pairwise relationship candidates between the datasets of the specified sources in the specified pipeline.

required:
- candidates

relationship-candidate:
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could we have anyway of determining potential cardinality of the relationships based on concept model metadata we have? I understand this isn't straight forward

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I'll add the field so you can consume it, though it will probably be static 1:1 for now until we come up with a reliable means of computing it.

… relationshipType

- Rename left/right to referrer/referent with documented semantics
- Add required relationshipType enum field (oneToOne, oneToMany, manyToMany)
- Document referrer/referent assignment rules for symmetric vs asymmetric types
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants