bbende commented on PR #11184: URL: https://github.com/apache/nifi/pull/11184#issuecomment-4353109168
@markap14 after looking at this integration test that keeps failing, I clicked the button to have Copiliot explain the build failure and this seems like a legit issue... ``` The failing tests show a critical issue: IllegalArgumentException: Cannot migrate from a StandardProcessSession to a class org.apache.nifi.controller.repository.WeakHashMapProcessSessionFactory$FactoryRetainingProcessSession This error occurs in the MergeRecord processor when attempting to migrate a FlowFile between different ProcessSession implementations. The root cause is that the code is trying to migrate a StandardProcessSession to a FactoryRetainingProcessSession, which are incompatible types. Key Issues from the Logs: Session Type Mismatch: The StandardProcessSession.migrate() method at line 1505 is rejecting the migration because it validates that the target session type is compatible. Cascading Failures: The migration error prevents the MergeRecord processor from functioning, causing FlowFiles to be routed to failure and blocking the connector from draining. Timeout Chain: The inability to process FlowFiles causes the connector to timeout during prepareForUpdate(), which is called during dynamic flow updates (like the schema registry test). Root Cause: The WeakHashMapProcessSessionFactory is creating FactoryRetainingProcessSession instances, but the MergeRecord processor (or related code) is attempting to migrate sessions created by StandardProcessSession to these incompatible session types. Solution: The fix is to validate session type compatibility before attempting migration in StandardProcessSession.migrate(). Modify the migration logic to handle or reject incompatible session types gracefully: ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
