change target formats allowed in dask executor #352
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jperez999
added
enhancement
Documentation preview |
This was referenced Jun 26, 2023
karlhigley
approved these changes
Jun 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes it possible for the dask executor to change the allowed dataformats for the local executor it houses internally. By only allowing dataframe formats, we ensure that the dask dataframe that goes into a dask executor is handled correctly between multiple nodes that may change the format of the data internally. This change is necessary to get batch working correctly. This allows you to attach a PredictTensorflow operator to a nvtabular workflow. Allowing the user to run a dask dataframe through a full systems ensemble.