Closed apryiomka closed 2 years ago
Issue-Label Bot is automatically applying the labels:
Label | Probability |
---|---|
feature | 0.93 |
Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: app homepage, dashboard and code for this bot.
It seems that parts of TensorFlow are used in google/ml-metadata which is a dependency of kubeflow/metadata. The use-case is not very clear to me but it looks like various TensorFlow-specific domain objects are used in the RPC calls between SDK and Metadata Service.
I'm wondering if there's a temporary workaround for this? We're using PyTorch and MXNet and having TensorFlow installed as Metadata SDK dependency impacts our image sizes significantly.
Here's a relevant issue in google/ml-metadata repo with a PR open: https://github.com/google/ml-metadata/issues/25. Once landed, the problem with TensorFlow dependency in Metadata SDK should be resolved after upgrading this dependency.
Kind reminder, there is a new release in google/ml-metadata/releases that solves this issue
Is there a plan to move to ml-metadata>=0.23.0? Current version of 0.21.0 forces an install of tensorflow anywhere someone wants to use kubeflow-metadata, which is undesirable and unintuitive
/kind feature
Describe the solution you'd like Currently a lot of packages are being installed whether requested or not. For instance, we do not use tensorflow and work with sckit-learn instead, but the image gets bloated with tensorflow packages and also tensorflow is loaded automatically when trying to log metrics