You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Flux#collect with a Supplier for a custom List<DataBuffer> to limits the total number of bytes buffered. However doOnDiscard does not work for the items in the List as it does with collectList(). This is understandable for a custom, opaque container, but if the container is a Collection or Iterable then perhaps individual items should be discarded.
The text was updated successfully, but these errors were encountered:
- Flux.collect(Supplier, BiConsumer) now detects if the
container is of type Collection, in which case it discards each element
in the collection when appropriate
- the operator also now additionally discard the element T along the
container when the collector function fails
- Flux.collect(Collector) now also discards elements in a similar
fashion to Flux.collect(Supplier, BiConsumer). The accumulator failure
case and finisher Function failure case are taken into account. The
discarding of individual elements inside a Collection is applied to
the intermediate container, not the result of the finisher()
Behavior change: if you extend Operators.MonoSubscriber, keep the
following in mind: `discard(O v)` no longer nulls out the `this.value`
field. Calling methods now need to do that themselves instead.
I'm using
Flux#collect
with aSupplier
for a customList<DataBuffer>
to limits the total number of bytes buffered. HoweverdoOnDiscard
does not work for the items in theList
as it does withcollectList()
. This is understandable for a custom, opaque container, but if the container is aCollection
orIterable
then perhaps individual items should be discarded.The text was updated successfully, but these errors were encountered: