Is it possible to set a retry and then commit the chuck regardless of the outcome of the retry?
From my testing, it seems that whenever a retry is exhausted the entire chuck gets rolled back as well including those items that didn't fail. When adding 'no-rollback-exception-classes', it's the other way around, the chuck gets committed but the retry doesn't happen.
It is explained here but I find it is too abstract so I want to be sure that I understand it correctly.
Better yet, is it possible to always commit a chuck regardless of skips or retries?