Last week, I described a use-case for a custom Stream Collector.
I received a intriguing comment on Twitter:
Interesting article. For completness' sake this specific problem could also be solved using the standard teeing collector
— Miguel Martins (@Miguucm) May 3, 2021
Hats off to you, Miguel! Your comment revealed a method I didn’t know!
So I decided to investigate what the teeing() method is about.
Returns a Collector that is a composite of two downstream collectors. Every element passed to the resulting collector is processed by both downstream collectors, then their results are merged using the specified merge function into the final result.
The resulting collector functions do the following:
- supplier: creates a result container that contains result containers obtained by calling each collector’s supplier
- accumulator: calls each collector’s accumulator with its result container and the input element
- combiner: calls each collector’s combiner with two result containers
- finisher: calls each collector’s finisher with its result container, then calls the supplied merger and returns its result.
We can indeed replace our custom Collector with two simple Collector implementations, one aggregating price rows and the other summing the cart’s price.
Let’s look at the final code and explain it line by line.
public PriceAndRows getPriceAndRows(Cart cart) {
return cart.getProducts()
.entrySet()
.stream()
.map(CartRow::new) (1)
.collect(Collectors.teeing( (2)
Collectors.reducing(BigDecimal.ZERO, CartRow::getRowPrice, BigDecimal::add),(3)
Collectors.toList(), (4)
PriceAndRows::new (5)
));
}| 1 | Map each Entry to a CartRow |
| 2 | Call the teeing() method |
| 3 | The first collector computes the price.
It’s a simple reducing() call, with:
|
| 4 | The second collector aggregates the CartRow into a list |
| 5 | Finally, the last parameter creates a new object that aggregates the results from the first and the second collector |
On the implementation side, teeing():
- Extracts each of the individual components of both
Collector, i.e.,supplier(),accumulator(),combiner()andfinisher() - Pairs them side-by-side
- Creates a single new
Collectorby passing the pairs
Thus, there will be a single Collector and a single pass in the end.
I hope this post made you consider using teeing() before creating a custom Collector. Thanks again to Miguel!
By the way, I’m always happy to learn new things. In case you’ve got insights to share, you can use the commenting system below or Twitter.