2

Could someone explain me why does it behave this way?

Flux.combineLatest(
    Tuples::fromArray,
    Flux.just(1, 2, 3),
    Mono.just("x"))
.collectList()
.block();
// [{3, "x"}]

Flux.combineLatest(
    Tuples::fromArray,
    Mono.just("x"),
    Flux.just(1, 2, 3))
.collectList()
.block();
// [{"x", 1}, {"x", 2}, {"x", 3}]

And is it possible to make it agnostic to arguments order (I expect option 2 to be a correct one)?

Mikhail Kadan
  • 556
  • 1
  • 5
  • 15

1 Answers1

1

Since every value in just is readily available, there is a form of optimization that can immediately iterates through the elements. In the first snippet, the 3 element just is the first that gets subscribed to and that optimisation kicks in, making it look like the whole sequence has already completed by the time the second Flux is subscribed to, hence the result you see.

To deactivate that optimisation, you can chain in a .hide() and it should produce the same result as in case 2.

Simon Baslé
  • 27,105
  • 5
  • 69
  • 70
  • Do you mean I should use `Flux.just(1, 2, 3).hide()` instead of a simple `Flux.just(1, 2, 3)`? Tried this but unfortunately got the same result. – Mikhail Kadan Jan 20 '18 at 19:04