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

[feature] Remove artifact namespace constraint #11505

Open
tferi opened this issue Jan 9, 2025 · 0 comments
Open

[feature] Remove artifact namespace constraint #11505

tferi opened this issue Jan 9, 2025 · 0 comments

Comments

@tferi
Copy link

tferi commented Jan 9, 2025

Feature Area

/area sdk

What feature would you like to see?

Context:

def validate_schema_title(schema_title: str) -> None:

Python dsl users should be able to use custom namespaces for their artifacts. The currently enforced system and google namespaces seem arbitrary, I see no reason why they should be constrained like that. For instance TFX runs perfectly happily on Kubeflow with artifacts from the tfx namespace, and they do so by having their own PipelineSpec compiler that is not the KFP one.

What is the use case or pain point?

We're migrating a TFX Pipeline to Kubeflow, but there are systems that integrate with this pipeline execution, and expect certain components to have certain artifacts with certain types (tfx.Whatever). The native Kubeflow compiler does not allow components to have artifacts that aren't from google or system.

Also, companies other than Google may have perfectly legitimate use cases to introduce their own namespace.

Is there a workaround currently?

Monkey patch the KFP codebase at runtime.

type_utils.validate_schema_title = lambda x: pass


Love this idea? Give it a 👍.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant