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
Run completion events emitted by the KFP provider only contain ServingModelArtifacts, not Artifacts. This means that dependent run configurations do not work using this provider.
The text was updated successfully, but these errors were encountered:
On starting to develop this it became apparent that a functional regression has been made on upgrading to TFX > 1.2.0 which stops us from implementing a fix.
The "name" custom property which is relied upon to do the filtering in the metadata store in getArtifacts is now not set.
When executing the following gRPC calls:
grpcurl -d '{"type_name": "pipeline_run", "context_name": "kfp-operator-quickstart-kfp-k49nf"}' -proto ml_metadata/proto/metadata_store_service.proto -plaintext 127.0.0.1:8085 ml_metadata.MetadataStoreService.GetContextByTypeAndName
> returns the content_id to use in following call
grpcurl -d '{"context_id":"143456"}' -proto ml_metadata/proto/metadata_store_service.proto -plaintext 127.0.0.1:8085 ml_metadata.MetadataStoreService.GetArtifactsByContext
Describe the bug
Run completion events emitted by the KFP provider only contain
ServingModelArtifacts
, notArtifacts
. This means that dependent run configurations do not work using this provider.The text was updated successfully, but these errors were encountered: