diff options
| author |  Rohan Jain <rohanj@google.com> | 2018-10-09 08:16:49 -0700 |
|---|---|---|
| committer |  TensorFlower Gardener <gardener@tensorflow.org> | 2018-10-09 08:21:39 -0700 |
| commit | cadcacc6224bcbb8a05bf3b70d625d9024a9c0f3 (patch) | |
| tree | fe73a2d1ed500dbd1e5b0f6f20229e534f813d90 /tensorflow/python/kernel_tests/linalg/linear_operator_diag_test.py | |
| parent | a0ed9452d5c7f897e26788d8dca5164cb6fba023 (diff) | |
Allowing for mixture of V1 and V2 feature columns usage in canned estimators. This is required for TF hub use cases where users might send in new feature columns to old model code. Implemented this support by making V2 feature columns support the V1 API. This is needed temporarily and would definitely be removed by TF 2.0, possibly earlier depending on what guarantees are provided by TF hub.
The only case we don't allow here is mixing in V2 shared embedding columns with V1 Feature columns. V2 Shared FC's depend on a SharedEmbeddingState manager that would have to be passed in to the various API's and there wasn't really a very clean way to make that work.
Mixing V2 feature columns with V1 shared embedding columns is fine though and along with all other combinations
PiperOrigin-RevId: 216359041
Diffstat (limited to 'tensorflow/python/kernel_tests/linalg/linear_operator_diag_test.py')
0 files changed, 0 insertions, 0 deletions