Add copy
flag that enables a deep copy of the entire stream pipeline.
#362
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.
The flag introduced in this commit could be used to split a stream into multiple ones and use each branch independently.
AbstractDataStream
now accepts an optional flagcopy
which isFalse
by default. When set toTrue
, theDataIterator
in theAbstractDataStream.get_epoch_iterator
is always provided with a unique deep copy of the data stream.In addition,
Merge
now accepts and forwards**kwargs
toAbstractDataStream
for compatibility reasons.The following code demonstrates the unexpected behavior which could be avoided by using the
copy=True
flag. The code splits a stream of two variables into two independent streams. Then the streams are merged back into a single stream again. An expected behavior is that the resulting stream generates the same data as the original stream. However, this is not the case.