Yes, once you have a stream of resources you could perform a forEach action upon those resources. In this case you would probably commit your changes once complete rather than passing in the resolver and committing after every update.
Arun Patidar - It is doing repository traversals, not using indices. Similar to SlingQuery, it's going to be best for relatively shallow or targeted Resources structures vs. JCR Queries which are more appropriate for deeper structures or searches across the entire repository.
Watch my video "Achieving Development Tranquility with the Apache Sling Service User WebConsole" to learn more about the Service User WebConsole I contributed to the #ApacheSling project:Achieving Development Tranquility with the Apache Sling Service User WebConsole
Follow up to my previous post about the ideal background job, how to monitor Sling Health Checks in an Adobe Managed Services environment:Proactive Monitoring of AEM in Adobe Managed Services with Sling Health Checks | Perficient Digital