[
https://issues.apache.org/jira/browse/NIFI-12217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Steinebrey resolved NIFI-12217.
-----------------------------------
Fix Version/s: 2.0.0-M3
1.26.0
Resolution: Fixed
This was noticed independently and fixed as part of NIFI-13103
> In PutDatabaseRecord processor, when you try to insert a CLOB and a
> SQLException gets catched, the exception message gets lost
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-12217
> URL: https://issues.apache.org/jira/browse/NIFI-12217
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.23.2
> Reporter: Alessandro Polselli
> Priority: Trivial
> Labels: putdatabaserecord
> Fix For: 2.0.0-M3, 1.26.0
>
>
> 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
> {code:java}
> } catch (SQLException e) {
> throw new IOException("Unable to parse data as
> CLOB/String " + value, e.getCause());
> } {code}
> with
> {code:java}
> } catch (SQLException e) {
> throw new IOException("Unable to parse data as
> CLOB/String " + value, e);
> } {code}
>
> Thank you
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
