What's the purpose of partitioningBy

Question

For example, if I intend to partition some elements, I could do something like:

Stream.of("I", "Love", "Stack Overflow")       .collect(Collectors.partitioningBy(s -> s.length() > 3))       .forEach((k, v) -> System.out.println(k + " => " + v)); 

which outputs:

false => [I] true => [Love, Stack Overflow] 

But for me partioningBy is only a subcase of groupingBy. Although the former accepts a Predicate as parameter while the latter a Function, I just see a partition as a normal grouping function.

So the same code does exactly the same thing:

 Stream.of("I", "Love", "Stack Overflow")        .collect(Collectors.groupingBy(s -> s.length() > 3))        .forEach((k, v) -> System.out.println(k + " => " + v)); 

which also results in a Map<Boolean, List<String>>.

So is there any reason I should use partioningBy instead of groupingBy? Thanks

Answer 1

partitioningBy will always return a map with two entries, one for where the predicate is true and one for where it is false. It is possible that both entries will have empty lists, but they will exist.

That's something that groupingBy will not do, since it only creates entries when they are needed.

At the extreme case, if you send an empty stream to partitioningBy you will still get two entries in the map whereas groupingBy will return an empty map.

EDIT: As mentioned below this behavior is not mentioned in the Java docs, however changing it would take away the added value partitioningBy is currently providing. For Java 9 this is already in the specs.

Answer 2

partitioningBy is slightly more efficient, using a special Map implementation optimized for when the key is just a boolean.

(It might also help to clarify what you mean; partitioningBy helps to effectively get across that there's a boolean condition being used to partition the data.)