ExecutionType and ArtifactType themselves need properties and metadata

[Ark-kun]

For ExecutionType, we want to store the ComponentSpec that is used to spawn the Executions.
For ArtifactType we want to store some information like deep JSON schema, visualization parameters serializers etc.

[hughmiao]

We discussed this before as static properties of the Artifact/ExecutionType. latter some of these problem can be resolved by putting it to some PipelineContext, as per pipeline or per run properties. Will this approach work for you?

[Ark-kun]

We discussed this before as static properties of the Artifact/ExecutionType. latter some of these problem can be resolved by putting it to some PipelineContext, as per pipeline or per run properties. Will this approach work for you?

Context is a different entity. ArtifactTypes and ExecutionTypes are not limited to a single Context or ContextType.

Can the MLMD team just add custom_properties to ArtifactTypes and ExecutionTypes? I think it should be doable.

[Ark-kun]

Are there any objections to adding custom_properties to ArtifactType and ExecutionType?