[
https://issues.apache.org/jira/browse/NIFI-8535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17344829#comment-17344829
]
ASF subversion and git services commented on NIFI-8535:
-------------------------------------------------------
Commit f812dfdfc0f008d372581c6e4c8770c88ad1c3e6 in nifi's branch
refs/heads/main from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f812dfd ]
NIFI-8535: Better error message in PutDatabaseRecord when table does not exist
(#5070)
* NIFI-8535: Better error message in PutDatabaseRecord when table does not exist
> PutDatabaseRecord should give a better message when the table cannot be found
> -----------------------------------------------------------------------------
>
> Key: NIFI-8535
> URL: https://issues.apache.org/jira/browse/NIFI-8535
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently PutDatabaseRecord calls DatabaseMetaData.getColumns() to try and
> match the columns from the specified table to the fields in the incoming
> record(s). However if the table itself is not found, this method returns an
> empty ResultSet, so it is not known whether the table does not exist or if it
> exists with no columns.
> PutDatabaseRecord should call DatabaseMetaData.getTables() if the column list
> is empty, and give a more descriptive error message if the table is not
> found. This can help the user determine whether there is a field/column
> mismatch or a catalog/schema/table name mismatch.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
