Skip to content

feat(idl): add RELATION_TYPE_FORK to RelationType - #8299

Closed
samhita-alla wants to merge 1 commit into
mainfrom
feat/relation-type-fork
Closed

samhita-alla wants to merge 1 commit into
mainfrom
feat/relation-type-fork

Conversation

@samhita-alla

@samhita-alla samhita-alla commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Tracking issue

Related to unionai/cloud#19745, which uses this value.

Why are the changes needed?

A fork recovers a parent run with different code, such as a new task version built from local changes. Today it can only be recorded as a plain recovery, so clients label it as one.

What changes were proposed in this pull request?

  • Add RELATION_TYPE_FORK = 6 to RelationType. It recovers the same way as RELATION_TYPE_RECOVER and only records provenance. Readers that don't know the value treat it as unknown, so the change is backward compatible.
  • Document the recover config as valid with either type.
  • Regenerate the checked-in code. Nothing in this repo switches on RelationType, so behavior doesn't change here.

How was this patch tested?

  • buf lint and buf format pass, and the generated Go and Rust build.
  • Regenerating produces no further diff.

Labels

  • added

Check all the applicable boxes

  • I updated the documentation accordingly.
  • All new and existing tests passed.
  • All commits are signed-off.

Related PRs

  • unionai/cloud#19745 stores and displays FORK. Its flyte2 submodule is pinned to a cherry-pick of this commit and should move to this PR's merge commit once it lands.
  • flyte-sdk needs a flyteidl2 bump to a release with this value before the backend sends it; older SDKs raise when printing a relation type they don't know.

🤖 Generated with Claude Code

A fork recovers a parent run with different code: the new run's root task
differs from the parent's root task, for example a new task version built
from local changes. Recording it as RELATION_TYPE_RECOVER makes it
indistinguishable from a plain recovery, so clients label it as one.

RELATION_TYPE_FORK = 6 lets the server record that provenance. Recovery
semantics are the same as RELATION_TYPE_RECOVER, and readers that do not
know the value keep treating it as an unknown relation type.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Samhita Alla <aallasamhita@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant