[DataLoader2] Handle MapDataPipe
by converting to IterDataPipe
internally by default
#1146
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.
Stack from ghstack:
MapDataPipe
by converting toIterDataPipe
internally by default #1146Fixes #1143
I believe since
DataLoader2
would always calliter(map_data_pipe)
at some point anyway, it should make no different to perform the conversion withto_iter_datapipe()
within__init__
.This will also allow prefetchers to be attached to the DataPipe.
Please let me know if this may be BC-breaking.
Differential Revision: D45452068