A stream pipeline is lazy. Without a terminal operation, your stream pipeline is not even executed. Stream.map
is an intermediate operation so it won't trigger pipeline execution.
Now you could add a forEach
step with the lambda expression cf -> cf.join()
for joining on your created CompletableFuture
instances for your pipeline to be executed and wait for each of your async futures to complete. But doing this way will defeat the whole purpose of using asynchronous futures, because you're submitting them sequentially and waiting on the completion of each one before submitting the next one.
Better yet, you could convert your stream to a parallel stream, use map
with your async lambda body directly by removing the CompletableFuture.supplyAsync
part and collecting with collect
for a similar effect without the extra clutter.
List<Book> bookList = isbnList.parallelStream()
.map(isbn -> {
try {
List<String> pageContents = getUrlContents(webLink + isbn);
return new Book(
parseBookTitle(pageContents),
isbn,
parseRank(pageContents)
);
} catch (IOException ex) {
throw new RuntimeException(ex);
}
}).collect(Collectors.toList());
Further reading: Stream operations and pipelines in the stream API javadoc.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…