Java8的Stream操作

忘是亡心i 2021-10-15 10:25 326阅读 0赞

## Java8的Stream操作，集合处理很是方便 ##

### 1. 写在前面 ###

点击查看，Java8 的新特性

### 2. 创建 Stream ###

有许多方法可以创建不同源的流实例。一旦创建，实例将不会修改其源，因此允许从单个源创建多个实例

#### 2.1. Empty Stream ####

如果创建空流，要使用empty（）方法，避免为没有元素的流返回Null.

Stream<String> streamEmpty = Stream.empty();

public Stream<String> streamOf(List<String> list) {
        return list == null || list.isEmpty() ? Stream.empty() : list.stream();
    }

#### 2.2. Stream of Collection ####

Stream也能被任何Collection (Collection, List, Set)对象创建:

Collection<String> collection = Arrays.asList("a", "b", "c");
    Stream<String> streamOfCollection = collection.stream();

#### 2.3. Stream of Array ####

Stream也可以源自Array:

Stream<String> streamOfArray = Stream.of("a", "b", "c");

它们也可以从现有数组或数组的一部分创建：

String[] arr = new String[]{"a", "b", "c"};
    Stream<String> streamOfArrayFull = Arrays.stream(arr);
    Stream<String> streamOfArrayPart = Arrays.stream(arr, 1, 3);

#### 2.4. Stream.builder() ####

使用builder构建流时，要指定类型

Stream<String> streamBuilder = Stream.<String>builder().add("a").add("b").add("c").build();

#### 2.5. Stream.generate() ####

generate() 方法需要就收一个Supplier对象作为元素生成. 还需指定流的大小，否则会一直gennerate()

Stream<String> streamGenerated =Stream.generate(() -> "element").limit(10);

上面的代码创建了一个包含十个字符串的序列，其值为“element”。

#### 2.6. Stream.iterate() ####

还可以通过iterate() method构建流:

Stream<Integer> streamIterated = Stream.iterate(40, n -> n + 2).limit(20);

#### 2.7. Stream of Primitives ####

Java 8提供了从三种基本类型创建流的可能性：int，long和double。由于Stream 是一个通用接口，并且无法使用基元作为泛型的类型参数，因此创建了三个新的特殊接口：IntStream，LongStream，DoubleStream。  
减轻了不必要的自动装箱，从而提高了效率。

IntStream intStream = IntStream.range(1, 3);
    LongStream longStream = LongStream.rangeClosed(1, 3);

The range(int startInclusive, int endExclusive) method creates an ordered stream from the first parameter to the second parameter. It increments the value of subsequent elements with the step equal to 1. The result doesn’t include the last parameter, it is just an upper bound of the sequence.

The rangeClosed(int startInclusive, int endInclusive) method does the same with only one difference – the second element is included. These two methods can be used to generate any of the three types of streams of primitives.

Since Java 8 the Random class provides a wide range of methods for generation streams of primitives. For example, the following code creates a DoubleStream, which has three elements:

Random random = new Random();
    DoubleStream doubleStream = random.doubles(3);

#### 2.8. Stream of String ####

String can also be used as a source for creating a stream.

With the help of the chars() method of the String class. Since there is no interface CharStream in JDK, the IntStream is used to represent a stream of chars instead.

IntStream streamOfChars = "abc".chars();

The following example breaks a String into sub-strings according to specified RegEx:

Stream<String> streamOfString =
      Pattern.compile(", ").splitAsStream("a, b, c");

#### 2.9. Stream of File ####

Java NIO class Files allows to generate a Stream of a text file through the lines() method. Every line of the text becomes an element of the stream:

Path path = Paths.get("C:\\file.txt");
    Stream<String> streamOfStrings = Files.lines(path);
    Stream<String> streamWithCharset = 
      Files.lines(path, Charset.forName("UTF-8"));

The Charset can be specified as an argument of the lines() method.

### 3. Referencing a Stream ###

It is possible to instantiate a stream and to have an accessible reference to it as long as only intermediate operations were called. Executing a terminal operation makes a stream inaccessible.

To demonstrate this we will forget for a while that the best practice is to chain sequence of operation. Besides its unnecessary verbosity, technically the following code is valid:

Stream<String> stream = 
      Stream.of("a", "b", "c").filter(element -> element.contains("b"));
    Optional<String> anyElement = stream.findAny();

But an attempt to reuse the same reference after calling the terminal operation will trigger the IllegalStateException:

Optional<String> firstElement = stream.findFirst();

As the IllegalStateException is a RuntimeException, a compiler will not signalize about a problem. So, it is very important to remember that Java 8 streams can’t be reused.

This kind of behavior is logical because streams were designed to provide an ability to apply a finite sequence of operations to the source of elements in a functional style, but not to store elements.

So, to make previous code work properly some changes should be done:

List<String> elements =
      Stream.of("a", "b", "c").filter(element -> element.contains("b"))
        .collect(Collectors.toList());
    Optional<String> anyElement = elements.stream().findAny();
    Optional<String> firstElement = elements.stream().findFirst();

### 4. Stream Pipeline ###

To perform a sequence of operations over the elements of the data source and aggregate their results, three parts are needed – the source, intermediate operation(s) and a terminal operation.

Intermediate operations return a new modified stream. For example, to create a new stream of the existing one without few elements the skip() method should be used:

Stream<String> onceModifiedStream =
      Stream.of("abcd", "bbcd", "cbcd").skip(1);

If more than one modification is needed, intermediate operations can be chained. Assume that we also need to substitute every element of current Stream with a sub-string of first few chars. This will be done by chaining the skip() and the map() methods:

Stream<String> twiceModifiedStream =
      stream.skip(1).map(element -> element.substring(0, 3));

As you can see, the map() method takes a lambda expression as a parameter. If you want to learn more about lambdas take a look at our tutorial Lambda Expressions and Functional Interfaces: Tips and Best Practices.

A stream by itself is worthless, the real thing a user is interested in is a result of the terminal operation, which can be a value of some type or an action applied to every element of the stream. Only one terminal operation can be used per stream.

The right and most convenient way to use streams are by a stream pipeline, which is a chain of stream source, intermediate operations, and a terminal operation. For example:

List<String> list = Arrays.asList("abc1", "abc2", "abc3");
    long size = list.stream().skip(1)
      .map(element -> element.substring(0, 3)).sorted().count();

### 5. Lazy Invocation ###

Intermediate operations are lazy. This means that they will be invoked only if it is necessary for the terminal operation execution.

To demonstrate this, imagine that we have method wasCalled(), which increments an inner counter every time it was called:

private long counter;
      
    private void wasCalled() {
        counter++;
    }

Let’s call method wasCalled() from operation filter():

List<String> list = Arrays.asList(“abc1”, “abc2”, “abc3”);
    counter = 0;
    Stream<String> stream = list.stream().filter(element -> {
        wasCalled();
        return element.contains("2");
    });

As we have a source of three elements we can assume that method filter() will be called three times and the value of the counter variable will be 3. But running this code doesn’t change counter at all, it is still zero, so, the filter() method wasn’t called even once. The reason why – is missing of the terminal operation.

Let’s rewrite this code a little bit by adding a map() operation and a terminal operation – findFirst(). We will also add an ability to track an order of method calls with a help of logging:

Optional<String> stream = list.stream().filter(element -> {
        log.info("filter() was called");
        return element.contains("2");
    }).map(element -> {
        log.info("map() was called");
        return element.toUpperCase();
    }).findFirst();

Resulting log shows that the filter() method was called twice and the map() method just once. It is so because the pipeline executes vertically. In our example the first element of the stream didn’t satisfy filter’s predicate, then the filter() method was invoked for the second element, which passed the filter. Without calling the filter() for third element we went down through pipeline to the map() method.

The findFirst() operation satisfies by just one element. So, in this particular example the lazy invocation allowed to avoid two method calls – one for the filter() and one for the map().

### 6. Order of Execution ###

From the performance point of view, the right order is one of the most important aspects of chaining operations in the stream pipeline:

long size = list.stream().map(element -> {
        wasCalled();
        return element.substring(0, 3);
    }).skip(2).count();

Execution of this code will increase the value of the counter by three. This means that the map() method of the stream was called three times. But the value of the size is one. So, resulting stream has just one element and we executed the expensive map() operations for no reason twice out of three times.

If we change the order of the skip() and the map() methods, the counter will increase only by one. So, the method map() will be called just once:

long size = list.stream().skip(2).map(element -> {
        wasCalled();
        return element.substring(0, 3);
    }).count();

This brings us up to the rule: intermediate operations which reduce the size of the stream should be placed before operations which are applying to each element. So, keep such methods as skip(), filter(), distinct() at the top of your stream pipeline.

### 7. Stream Reduction ###

The API has many terminal operations which aggregate a stream to a type or to a primitive, for example, count(), max(), min(), sum(), but these operations work according to the predefined implementation. And what if a developer needs to customize a Stream’s reduction mechanism? There are two methods which allow to do this – the reduce() and the collect() methods.

#### 7.1. The reduce() Method ####

There are three variations of this method, which differ by their signatures and returning types. They can have the following parameters:

*  identity – the initial value for an accumulator or a default value if a stream is empty and there is nothing to accumulate;
 *  accumulator – a function which specifies a logic of aggregation of elements. As accumulator creates a new value for every step of reducing, the quantity of new values equals to the stream’s size and only the last value is useful. This is not very good for the performance.
 *  combiner – a function which aggregates results of the accumulator. Combiner is called only in a parallel mode to reduce results of accumulators from different threads.

So, let’s look at these three methods in action:

OptionalInt reduced =
      IntStream.range(1, 4).reduce((a, b) -> a + b);
    reduced = 6 (1 + 2 + 3)

int reducedTwoParams =
      IntStream.range(1, 4).reduce(10, (a, b) -> a + b);
    reducedTwoParams = 16 (10 + 1 + 2 + 3)

int reducedParams = Stream.of(1, 2, 3)
      .reduce(10, (a, b) -> a + b, (a, b) -> {
         log.info("combiner was called");
         return a + b;
      });

The result will be the same as in the previous example (16) and there will be no login which means, that combiner wasn’t called. To make a combiner work, a stream should be parallel:

int reducedParallel = Arrays.asList(1, 2, 3).parallelStream()
        .reduce(10, (a, b) -> a + b, (a, b) -> {
           log.info("combiner was called");
           return a + b;
        });

The result here is different (36) and the combiner was called twice. Here the reduction works by the following algorithm: accumulator ran three times by adding every element of the stream to identity to every element of the stream. These actions are being done in parallel. As a result, they have (10 + 1 = 11; 10 + 2 = 12; 10 + 3 = 13;). Now combiner can merge these three results. It needs two iterations for that (12 + 13 = 25; 25 + 11 = 36).

#### 7.2. The collect() Method ####

Reduction of a stream can also be executed by another terminal operation – the collect() method. It accepts an argument of the type Collector, which specifies the mechanism of reduction. There are already created predefined collectors for most common operations. They can be accessed with the help of the Collectors type.

In this section we will use the following List as a source for all streams:

List<Product> productList = Arrays.asList(new Product(23, "potatoes"),
      new Product(14, "orange"), new Product(13, "lemon"),
      new Product(23, "bread"), new Product(13, "sugar"));
    Converting a stream to the Collection (Collection, List or Set):

List<String> collectorCollection = 
      productList.stream().map(Product::getName).collect(Collectors.toList());
    Reducing to String:

String listToString = productList.stream().map(Product::getName)
      .collect(Collectors.joining(", ", "[", "]"));

The joiner() method can have from one to three parameters (delimiter, prefix, suffix). The handiest thing about using joiner() – developer doesn’t need to check if the stream reaches its end to apply the suffix and not to apply a delimiter. Collector will take care of that.

Processing the average value of all numeric elements of the stream:

double averagePrice = productList.stream()
      .collect(Collectors.averagingInt(Product::getPrice));

Processing the sum of all numeric elements of the stream:

int summingPrice = productList.stream()
      .collect(Collectors.summingInt(Product::getPrice));

Methods averagingXX(), summingXX() and summarizingXX() can work as with primitives (int, long, double) as with their wrapper classes (Integer, Long, Double). One more powerful feature of these methods is providing the mapping. So, developer doesn’t need to use an additional map() operation before the collect() method.

Collecting statistical information about stream’s elements:

IntSummaryStatistics statistics = productList.stream()
      .collect(Collectors.summarizingInt(Product::getPrice));

By using the resulting instance of type IntSummaryStatistics developer can create a statistical report by applying toString() method. The result will be a String common to this one “IntSummaryStatistics\{count=5, sum=86, min=13, average=17,200000, max=23\}”.

It is also easy to extract from this object separate values for count, sum, min, average by applying methods getCount(), getSum(), getMin(), getAverage(), getMax(). All these values can be extracted from a single pipeline.

Grouping of stream’s elements according to the specified function:

Map<Integer, List<Product>> collectorMapOfLists = productList.stream()
      .collect(Collectors.groupingBy(Product::getPrice));

In the example above the stream was reduced to the Map which groups all products by their price.

Dividing stream’s elements into groups according to some predicate:

Map<Boolean, List<Product>> mapPartioned = productList.stream()
      .collect(Collectors.partitioningBy(element -> element.getPrice() > 15));

Pushing the collector to perform additional transformation:

Set<Product> unmodifiableSet = productList.stream()
      .collect(Collectors.collectingAndThen(Collectors.toSet(),
      Collections::unmodifiableSet));

In this particular case, the collector has converted a stream to a Set and then created the unmodifiable Set out of it.

Custom collector:

If for some reason, a custom collector should be created, the most easier and the less verbose way of doing so – is to use the method of() of the type Collector.

Collector<Product, ?, LinkedList<Product>> toLinkedList =
      Collector.of(LinkedList::new, LinkedList::add, 
        (first, second) -> { 
           first.addAll(second); 
           return first; 
        });

LinkedList linkedListOfPersons =  
productList.stream().collect(toLinkedList);  
In this example, an instance of the Collector got reduced to the LinkedList.

Parallel Streams  
Before Java 8, parallelization was complex. Emerging of the ExecutorService and the ForkJoin simplified developer’s life a little bit, but they still should keep in mind how to create a specific executor, how to run it and so on. Java 8 introduced a way of accomplishing parallelism in a functional style.

The API allows creating parallel streams, which perform operations in a parallel mode. When the source of a stream is a Collection or an array it can be achieved with the help of the parallelStream() method:

Stream<Product> streamOfCollection = productList.parallelStream();
    boolean isParallel = streamOfCollection.isParallel();
    boolean bigPrice = streamOfCollection
      .map(product -> product.getPrice() * 12)
      .anyMatch(price -> price > 200);

If the source of stream is something different than a Collection or an array, the parallel() method should be used:

IntStream intStreamParallel = IntStream.range(1, 150).parallel();
    boolean isParallel = intStreamParallel.isParallel();

Under the hood, Stream API automatically uses the ForkJoin framework to execute operations in parallel. By default, the common thread pool will be used and there is no way (at least for now) to assign some custom thread pool to it. This can be overcome by using a custom set of parallel collectors.

When using streams in parallel mode, avoid blocking operations and use parallel mode when tasks need the similar amount of time to execute (if one task lasts much longer than the other, it can slow down the complete app’s workflow).

The stream in parallel mode can be converted back to the sequential mode by using the sequential() method:

IntStream intStreamSequential = intStreamParallel.sequential();
    boolean isParallel = intStreamSequential.isParallel();

## 结论（Conclusions） ##

The Stream API is a powerful but simple to understand set of tools for processing sequence of elements. It allows us to reduce a huge amount of boilerplate code, create more readable programs and improve app’s productivity when used properly.

In most of the code samples shown in this article streams were left unconsumed (we didn’t apply the close() method or a terminal operation). In a real app, don’t leave an instantiated streams unconsumed as that will lead to memory leaks.

Stream API是一个功能强大但易于理解的工具集，用于处理元素序列。它允许我们减少大量的样板代码，创建更易读的程序，并在正确使用时提高应用程序的工作效率。

used properly.

在本文中显示的大多数代码示例中，流是未消耗的（我们没有应用close（）方法或终端操作）。在真实的应用程序中，不要留下未实例化的流，因为这将导致内存泄漏。