You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 👍.
The text was updated successfully, but these errors were encountered:
Feature Area
/area sdk
What feature would you like to see?
Context:
pipelines/sdk/python/kfp/dsl/types/type_utils.py
Line 497 in 0948561
Python dsl users should be able to use custom namespaces for their artifacts. The currently enforced
system
andgoogle
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 thetfx
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 fromgoogle
orsystem
.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 👍.
The text was updated successfully, but these errors were encountered: