Closed yhwang closed 3 years ago
/cc @Tomcli
So KFP is working on a new v2 design that requires few extra fields from its components. Part of the requirements is to specify the input/output parameter type for all the KFP components for the new design. This PR is to address this change.
@Tomcli , @yhwang - does this change preserve backward compatibility?
@Tomcli , @yhwang - does this change preserve backward compatibility?
No, the type
field was optional in the old KFP version. However, the upcoming v2 KFP version will make the type
required sometimes next year, so we want to update the AIF360 component to be ready for the new KFP versions.
From your response, it seems like type
field is optional now, but will become mandatory later. So including the type
field would preserve backward compatibility right? Just making sure it wont break any existing code.
From your response, it seems like
type
field is optional now, but will become mandatory later. So including thetype
field would preserve backward compatibility right? Just making sure it wont break any existing code.
yes it will preserve backward compatibility. Nothing will break from this PR. Sorry I probably didn't interpret your message correctly in my last comment.
Ok approved and merged.
thanks @nrkarthikeyan
Update component.yaml to kfp v2 compatible. In v2, you need to declare the data type for all of the input/output arguments.
Signed-off-by: Yihong Wang yh.wang@ibm.com