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

range_config doesn't work in TFX < 1.4.0 #8

Open
deep-diver opened this issue Oct 14, 2021 · 0 comments
Open

range_config doesn't work in TFX < 1.4.0 #8

deep-diver opened this issue Oct 14, 2021 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@deep-diver
Copy link
Owner

In the original concept, range_config should work for {SPAN} in ExampleGen. However there is a bug in TFX < 1.4.0. As of writing this issue, the bug fix has been merged, but nightly build or build from scratch version should be working. The nightly build version should be above 1.4.0.dev20211010 (you can find out the dev versions here)

When range_config works properly, we can integrate that functionality to dynamically choose the range of spans to run the training pipeline with Resolver node. For example, initial pipeline run could depend on span-1, but when data drift is detected, the second pipeline run could use both span-1 and span-2 together. In that case, we don't need to process the ExampleGen for the span-1 once again but only the span-2. Resolver node will reuse the ExampleGen artifacts for the span-1 generated from the initial pipeline run and integrate it with the new ExampleGen for the span-2.

More extensive discussion about this issue can be found in the issue from the TFX official repo.

@sayakpaul sayakpaul added the documentation Improvements or additions to documentation label Oct 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants