-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
TFServing Compatibility issue with the TF2.0 model using feature columns #1462
Comments
Update the request from: The input shape of the models are different between tf1.4 and tf2.0. TF2.0: |
hey @brightcoder01 good finding, can I check with you what version of tfs you are using for both tf models? I saw from above msg, you are using tfs 1.14 to support both tf1.14 and tf 2.0 model. |
Yes, we are using tf serving 1.14 to serve the models from tf1.14 and tf2.0. |
The error can be reproduced by followed codes
|
@rohan100jain could you look into this? Looks like a change to lookup table initialization has broken Session-based loading, possibly tensorflow/tensorflow@64586f1. Presumably related to loading multiple tables. If so we should add an integration test with multiple tables in tensorflow/python/saved_model/load_v1_in_v2_test.py |
Please assign @rohan100jain; apparently I have no access. |
@rmothukuru Could you please assign this bug to @rohan100jain as @allenlavoie suggested. It seems that I don't have access either. |
@rohan100jain Can you please take a look at this issue. Thanks! |
Hi, @gowthamkpr @rohan100jain, could you please share some updated information about this issue? It seems that it will block the TFServing usage with tf.feature_column.categorical_column_with_vocabulary_list. |
For the latest reproduction, the one with the table initialization issue - could you specify what version of TF you were using? I ran with the latest version (2.0.0) and seems to run fine. |
Yes, the case runs fine with the latest version tf-serving 2.0.0 which is released on 22 Oct. I used tf-serving 1.14.0 because version 2.0.0 was not released previously. Thanks for your validation. |
So then i'm closing the issue now. Please reopen or file another issue if more problems appear with TF2.0 |
@rohan100jain Could we expect that SavedModel exported by TF 1.x can be serving normally using TF-Serving 2.x |
Have the same problem, but with tensorflow 2.1.0, anyone same? |
System information
MacOS Mojave 10.14.6
Use docker image: docker pull tensorflow/serving
1.14.0
Describe the problem
We use the same model definition, run it using tensorflow 1.14.0 and tensorflow 2.0.0 and then get two models. Host these two models with the same tensorflow/serving:latest docker image and send the same request. The expectation is that the response from these two models should be the same. Actually, the model from tf 1.14 is fine but the model from tf 2.0.0 returns error.
Exact Steps to Reproduce
Source code / logs
census_data.py
census_keras.py
The text was updated successfully, but these errors were encountered: