Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using TFX components with TF 1.x contrib ops #838

Closed
misterpeddy opened this issue Oct 29, 2019 · 5 comments
Closed

Using TFX components with TF 1.x contrib ops #838

misterpeddy opened this issue Oct 29, 2019 · 5 comments

Comments

@misterpeddy
Copy link
Member

Due to the deprecation of TF contrib ops, any SavedModel produced using contrib ops (or indirectly using for example, tf.Transform ops that used tf.contrib ops underneath the hood such as tft.quantiles, tft.bucketize, etc.) cannot be loaded with TF 2.0.
Is there a migration story for users beyond rewriting our models to use TF core ops?

@zhitaoli
Copy link
Contributor

I would think this is more of a tensorflow question, and @martinwicke or @karmel can probably give some better guidance.

Specifically, I wonder whether there is a list of ops which were previously in contrib but removed in TF 2.0, and where can users find their replacements.

@misterpeddy
Copy link
Member Author

There's been a bunch of documentation published by TF (ex).

More than providing more solutions, this issue aims to be used as a means of recording problems of TFX users who come to us with issues concerning contrib ops deprecation so that we can track them in a central issue.

@martinwicke
Copy link
Member

I never made a list of ops, but the RFC (https://github.com/tensorflow/community/blob/master/rfcs/20180907-contrib-sunset.md) contains a list of what happened to which projects.
 
Many ops moved to core or addons or io, although the ops which were used only in TFT wouldn't have been moved elsewhere.

@gowthamkpr
Copy link

Is it still an issue? As tensorflow does not officially support contib anymore, can we go ahead and close this issue. Thanks!

@gowthamkpr
Copy link

Closing as stale. Please reopen if you'd like to work on this further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants