No API in this release is deprecated for removal.
| Since | Deprecated Item and Description |
|---|---|
reactor.
the input and output value type T>To be removed in 3.5, prefer clear cut usage of | |
Returns: a fresh processorTo be removed in 3.5. Closest sink is | |
reactor.
the input and output value type T>To be removed in 3.5. Prefer clear cut usage of This processor was blocking in
| |
reactor.
Deprecated as a consequence of | |
reactor.
Deprecated as a consequence of | |
reactor.
Deprecated as a consequence of | |
reactor.
Deprecated as a consequence of | |
Returns: a fresh processoruse | |
Returns: a fresh processorautomatically cancel autoCancel)use | |
Returns: a fresh processorthe internal buffer size to hold signals bufferSize)use | |
Returns: a fresh processorthe internal buffer size to hold signals bufferSize, boolean automatically cancel autoCancel)use | |
Returns: a newFlux behaving like the fastest of its sourcesThe competing source publishers sources)use | |
Returns: a newFlux behaving like the fastest of its sourcesThe competing source publishers sources)use | |
reactor.
the number of elements to emit from this flux, which is also the backpressure
cap for all of downstream's request n)replace with | |
Returns: a mergedFlux that compares latest values from each source, using the
smallest value and replenishing the source that produced itPublisher sources of Comparable to mergeUse | |
Returns: a mergedFlux that compares latest values from each source, using the
smallest value and replenishing the source that produced itthe comparator, Publisher<? extends T>... Comparator to use to find the smallest valuePublisher sources to mergeUse | |
Returns: a mergedFlux that compares latest values from each source, using the
smallest value and replenishing the source that produced itthe number of elements to prefetch from each source (avoiding too
many small requests to the source when picking) prefetch, Comparator<? super T> the comparator, Publisher<? extends T>... Comparator to use to find the smallest valuePublisher sources to mergeUse | |
Returns: a newFlux that compares latest values from the given publisher
and this flux, using the smallest value and replenishing the source that produced itthe other, Comparator<? super T> Publisher to merge withthe otherComparator)Comparator to use for mergingUse | |
Returns: an instrumentedFluxPrefer using the | |
Returns: a newMonouse | |
reactor.
the consumer to invoke on each value consumer, Consumer<? super Throwable> the consumer to invoke on error signal errorConsumer, Runnable the consumer to invoke on complete signal completeConsumer, Consumer<? super Subscription> the consumer to invoke on subscribe signal, to be used
for the initial subscriptionConsumer)request, or null for max requestBecause users tend to forget to | |
reactor.
the produced demand for inner sources prefetch)to be removed in 3.6.0 at the earliest. In 3.5.0, you should replace calls with prefetch=0 with calls to switchMap(fn), as the default behavior of the single-parameter variant will then change to prefetch=0. | |
Returns: aSinkManyAbstractBase accepting publishers and producing Tthe inner source request size prefetch)to be removed in 3.6.0 at the earliest. In 3.5.0, you should replace calls with prefetch=0 with calls to switchOnNext(mergedPublishers), as the default behavior of the single-parameter variant will then change to prefetch=0. | |
reactor.
the input value type IN, the output value type OUT>Processors will be removed in 3.5. Prefer using | |
Returns: a serializingFluxProcessorDeprecated as a consequence of | |
Returns: a serializingFluxSinkTo be removed in 3.5, prefer clear cut usage of | |
Returns: a serializingFluxSinkthe overflow strategy, see strategyFluxSink.
for the
available strategiesTo be removed in 3.5, prefer clear cut usage of | |
Returns: aFluxProcessor accepting publishers and producing Tshould use | |
Returns: a new blackboxedFluxProcessorthe upstream subscriber upstream, final Publisher<OUT> the downstream publisher downstream)Deprecated as a consequence of | |
reactor.
To be removed in 3.6.0 at the earliest. Prefer using #contextView() instead. | |
reactor.
Should only be used by the instrumentation, DOES NOT guarantee any compatibility | |
reactor.
Should only be used by the instrumentation, DOES NOT guarantee any compatibility | |
Returns: a newMono behaving like the fastest of its sources.The deferred monos to use. monos)use | |
Returns: a newMono behaving like the fastest of its sources.The deferred monos to use. monos)use | |
Returns: an instrumentedMonoPrefer using the | |
reactor.
Deprecated as a consequence of | |
reactor.
the type of the value that will be made available O>Processors will be removed in 3.5. Prefer using | |
reactor.
the | |
Returns: AMonoProcessor.Use | |
Returns: true if this MonoProcessor is cancelled, false
otherwise.the | |
reactor.
this method is discouraged, consider peeking into a MonoProcessor by | |
reactor.
the request amount n)the | |
reactor.
To be removed in 3.6.0 at the earliest. Prefer using #contextView() instead. | |
reactor.
Deprecated as a consequence of | |
reactor.
Deprecated as a consequence of | |
reactor.
Deprecated as a consequence of | |
reactor.
the value type T>To be removed in 3.5, prefer clear cut usage of | |
reactor.
Deprecated as a consequence of | |
reactor.
Deprecated as a consequence of | |
reactor.
use | |
Returns: a newReplayProcessor that replays its last pushed element to each new
Subscriber, or a default one if nothing was pushed yeta default value to start the sequence with in case nothing has been
cached yet. value)use | |
reactor.
use | |
reactor.
the backlog size, ie. maximum items retained for replay. historySize)use | |
Returns: a newReplayProcessor that replays the whole history to each new
Subscriber if configured as unbounded, a limited history otherwise.maximum items retained if bounded, or initial link size if unbounded historySize, boolean true if "unlimited" data store must be supplied unbounded)use | |
Returns: a newReplayProcessor that replay up to size elements, but
will evict them from its history based on their age.the maximum number of buffered items size, Duration the maximum age of the contained items maxAge)use | |
Returns: a newReplayProcessor that replay up to size elements, but
will evict them from its history based on their age.the maximum number of buffered items size, Duration the maximum age of the contained items in milliseconds maxAge, Scheduler the scheduler)Scheduler that provides the current timeuse | |
Returns: a newReplayProcessor that replays elements based on their age.the maximum age of the contained items maxAge)use | |
Returns: a newReplayProcessor that replays elements based on their age.the maximum age of the contained items maxAge, Scheduler scheduler)use | |
reactor.
Deprecated as a consequence of | |
reactor.
Deprecated as a consequence of | |
reactor.
Deprecated as a consequence of | |
reactor.
Deprecated as a consequence of | |
reactor.
Deprecated as a consequence of | |
Returns: the current subscriberContext.To be removed in 3.6.0 at the earliest. Prefer using #contextView() instead. | |
reactor.
the input and output type T>to be removed in 3.5, prefer clear cut usage of | |
reactor.
| |
Returns: a unicastFluxProcessoruse | |
Returns: a unicastFluxProcessorthe buffering queue queue)use | |
Returns: a unicastFluxProcessorthe buffering queue queue, Disposable called on any terminal signal endcallback)use | |
Returns: a unicastFluxProcessorthe buffering queue queue, Consumer<? super E> called when queue.offer return false and unicastProcessor is
about to emit onError. onOverflow, Disposable called on any terminal signal endcallback)use | |
reactor.
Use | |
reactor.
prefer using Micrometer#timedScheduler from the reactor-core-micrometer module. To be removed at the earliest in 3.6.0. | |
reactor.
prefer using Micrometer#timedScheduler from the reactor-core-micrometer module. To be removed at the earliest in 3.6.0. | |
reactor.
prefer using the new reactor-core-micrometer module Micrometer entrypoint. To be removed in 3.6.0 at the earliest. | |
reactor.
Prefer using the reactor-core-micrometer module and configuring it using the Micrometer entrypoint. | |
Returns: the configured registryprefer using Micrometer setup in new reactor-core-micrometer module. To be removed at the earliest in 3.6.0. | |
Returns: the previously configured registry.prefer using Micrometer setup in new reactor-core-micrometer module. To be removed at the earliest in 3.6.0. | |
Returns: true if the Micrometer instrumentation facade is availableprefer explicit usage of the reactor-core-micrometer module. To be removed in 3.6.0 at the earliest. | |
Returns: a newContext with a merge of the entries from this context and the given context.the context)Context from which to copy entrieswill be removed in 3.5, kept for backward compatibility with 3.3. Until
then if you need to work around the deprecation, use |