Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support importing datasets/workflows with legacy filters #2156

Closed
tcompa opened this issue Dec 19, 2024 · 2 comments
Closed

Support importing datasets/workflows with legacy filters #2156

tcompa opened this issue Dec 19, 2024 · 2 comments
Assignees
Labels
flexibility Support more workflow-execution use cases

Comments

@tcompa
Copy link
Collaborator

tcompa commented Dec 19, 2024

This concerns the support for importing previously-exported workflows or datasets, and how to handle their filters-related fields. See also #1401 (comment).

This issue will be "easy" to define after we clarify #2153 and #2154.

@tcompa tcompa added the flexibility Support more workflow-execution use cases label Dec 19, 2024
@tcompa tcompa changed the title Defin backwards compatibility for complex filters Define backwards compatibility for complex filters Dec 30, 2024
@tcompa
Copy link
Collaborator Author

tcompa commented Jan 15, 2025

Self-reminder: We will have to handle {DatasetV2,WorkflowTaskV2}Import schemas in the same way as we do for TaskOutput.
Ref

@tcompa tcompa changed the title Define backwards compatibility for complex filters Support importing datasets/workflows with legacy filters Jan 16, 2025
@tcompa tcompa assigned tcompa and unassigned ychiucco Jan 16, 2025
tcompa added a commit that referenced this issue Jan 16, 2025
@tcompa
Copy link
Collaborator Author

tcompa commented Jan 20, 2025

Superseded by #2188

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flexibility Support more workflow-execution use cases
Projects
Development

No branches or pull requests

2 participants