reactor-core/src/main/java/reactor/core/publisher/Flux.java
public final Disposable subscribe(Consumer<? super T> consumer) {
		Objects.requireNonNull(consumer, "consumer");
		return subscribe(consumer, null, null);
	}
public final Disposable subscribe(Consumer<? super T> consumer) {
		Objects.requireNonNull(consumer, "consumer");
		return subscribe(consumer, null, null);
	}
public final Disposable subscribe ( Consumer < ? super T > consumer ) { Objects . requireNonNull ( consumer , "consumer" ) ; return subscribe ( consumer , null , null ) ; }
Subscribe a {@link Consumer} to this {@link Flux} that will consume all the
elements in the  sequence. It will request an unbounded demand ({@code Long.MAX_VALUE}).
<p>
For a passive version that observe and forward incoming data see {@link #doOnNext(java.util.function.Consumer)}.
<p>
For a version that gives you more control over backpressure and the request, see
{@link #subscribe(Subscriber)} with a {@link BaseSubscriber}.
<p>
Keep in mind that since the sequence can be asynchronous, this will immediately
return control to the calling thread. This can give the impression the consumer is
not invoked when executing in a main thread or a unit test for instance.

<p>
<img class="marble" src="doc-files/marbles/subscribeWithOnNextForFlux.svg" alt="">

@param consumer the consumer to invoke on each value (onNext signal)

@return a new {@link Disposable} that can be used to cancel the underlying {@link Subscription}
Subscribe a { @link Consumer } to this { @link Flux } that will consume all the elements in the sequence . It will request an unbounded demand ( { @code Long . MAX_VALUE } ) . <p > For a passive version that observe and forward incoming data see { @link #doOnNext ( java . util . function . Consumer ) } . <p > For a version that gives you more control over backpressure and the request see { @link #subscribe ( Subscriber ) } with a { @link BaseSubscriber } . <p > Keep in mind that since the sequence can be asynchronous this will immediately return control to the calling thread . This can give the impression the consumer is not invoked when executing in a main thread or a unit test for instance .