Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2868
This is a good generic solution to the referenced Jiras (which usually
reference the DB2 issue with "ResultSet is closed", which in itself does have a
PR to fix #2629), however I wonder if we should locate the fix in
MaxValueResultSetRowCollector rather than the outer processing loop? Keep a
reference to the original map and return it on error rather than the updated
one? Pretty sure I'm responsible for the bad code that passes in a mutable map,
should have at least kept a sub-map for updates and then updated the original
map with successful updates.
---
