CODEWITHSUNDEEP
javajava-8java-stream
Shan
Shan

Reputation: 335

Based on condition set object value and return boolean using java 8 streams

I have nested list and am able to set isMatched and department.setMatchedStatus(true) when if condition is true.

boolean isMatched = false;
for (Employee employee: company.getEmployees()) {
    for (Department department: employee.getDepartments()) {
        if(departmentList.contains(department.getDepartmentName())){
             isMatched = true;
             department.setMatchedStatus(true);
        }
    }
}
return isMatched;

Would like to achieve the same using java 8 streams, which i tried using below code, but couldn't return boolean. 

 isMatched = company.getEmployees().stream()
.flatMap(employee-> employee.getDepartments().stream())
.filter((department) -> departmentList.contains(department.getDepartmentName()))
.forEach((department) -> department.setMatchedStatus(true));

Could anyone help me on this please ?

Upvotes: 3

Views: 9873

Answers (3)

Tagir Valeev
Tagir Valeev

Reputation: 100209

To me, the most clear solution would be the following:

Set<Department> matchingDepartments =
    company.getEmployees().stream()
           .flatMap(employee -> employee.getDepartments().stream())
           .filter(department -> departmentList.contains(department.getDepartmentName()))
           .collect(Collectors.toSet());
matchingDepartments.forEach(department -> department.setMatchedStatus(true));
return !matchingDepartments.isEmpty();

It's somewhat less efficient as produces an intermediate Set, but looks better than other proposed variants from the code readability point of view.

Upvotes: 0

Stuart Marks
Stuart Marks

Reputation: 132390

The difficulty here is that you have two side effects you want performed: setting the matched state on the Department object, and setting a local flag value to determine if there were any matches. The approach of using peek and count in sisyphus' answer will work, since in this case we can be assured that count won't short-circuit. However, it may cause problems under maintenance. If somebody were to copy and rearrange this code, it might silently break because of short-circuiting, and this would be quite subtle.

Perhaps a better approach is to pack the side effects into the forEach operation. This uses AtomicBoolean as a mutable "box" to work around the inability to mutate captured local variables. It's also preferable to the single-element array trick, as the atomics are safe in case the stream is run in parallel.

This also uses a statement lambda, which I generally prefer to avoid. In this case it's not too bad, and it makes clear that multiple side effects are occurring.

    AtomicBoolean isMatched = new AtomicBoolean(false);
    company.getEmployees().stream()
           .flatMap(employee -> employee.getDepartments().stream())
           .filter(department -> departmentList.contains(department.getDepartmentName()))
           .forEach(department -> {
               department.setMatchedStatus(true);
               isMatched.set(true);
           });
    return isMatched.get();

Upvotes: 5

sisyphus
sisyphus

Reputation: 6392

You could use the 'peek()' method on the Stream, which allows you to consume the items in the stream without altering the contents of the stream. After you've updated each object you just need to know if any were matched.

return company.getEmployees().stream()
               .flatMap(employee-> employee.getDepartments().stream())
               .filter((department) -> departmentList.contains(department.getDepartmentName()))
               .peek((department) -> department.setMatchedStatus(true))
               .count() > 0;

Upvotes: 3

Related Questions