Allow LogRotatorSink be a Sink[T] instead of Sink[ByteString] #2323
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 current implementation of
LogRotatorSink
works well for time-based rotation, if the time is the real time. It does not fit well, if the time to trigger on is contained in the stream itself, since the stream is already of typeByteString
. You had to parse thatByteString
to gain access to the time contained in the data (or anything else you would like to trigger on).This PR slightly modifies
LogRotatorSink
to accept an additional type parameterT
. The triggerGeneratorCreator function becomesT => Option[C]
, the sinkFactory becomesC => Sink[T, Future[R]]
. This allows to trigger on data contained inT
, the sink also works onT
and probably uses a transformerT => ByteString
. For details, have a look at the new test inLogRotatorSinkSpec
.