[NIFI-12217] In PutDatabaseRecord processor, when you try to insert a CLOB and a SQLException gets catched, the exception message gets lost

• Type: Bug
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 1.23.2
• Fix Version/s: 1.26.0, 2.0.0-M3
• Component/s: Core Framework
• Labels: putdatabaserecord
• Assignee: Unassigned
• Reporter: Alessandro Polselli
• Created: 12/Oct/23 09:30
• Updated: 09/May/24 18:19
• Resolved: 09/May/24 18:19

Description

In PutDatabaseRecord processor, when you try to insert a CLOB and a SQLException gets catched

https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/PutDatabaseRecord.java#L866C4-L866C4

the original Exception message (the most valuable part) gets completely lost, because only its .getCause() is wrapped in a generic IOException that states "Unable to parse data as CLOB/String", making it extremely difficult to identify which is the real problem.

In my case, the problem was something like "ORA-25153: Tablespace temporanea vuota" but this valuable message wasn't logged at all.

 

I suggest to replace 

                } catch (SQLException e) {
                    throw new IOException("Unable to parse data as CLOB/String " + value, e.getCause());
                } 

with

                } catch (SQLException e) {
                    throw new IOException("Unable to parse data as CLOB/String " + value, e);
                } 

 

Thank you

Issue Links

• duplicates: NIFI-13103 Enhance AutoCommit property to allow no value set in PutDatabaseRecord
• relates to: NIFI-6061 PutDatabaseRecord does not properly handle BLOB/CLOB fields