[jira] [Updated] (NIFI-8535) PutDatabaseRecord should give a better message when the table cannot be found
[ https://issues.apache.org/jira/browse/NIFI-8535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-8535: --- Fix Version/s: 1.14.0 > 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 > Fix For: 1.14.0 > > Time Spent: 50m > 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)
[jira] [Updated] (NIFI-8535) PutDatabaseRecord should give a better message when the table cannot be found
[ https://issues.apache.org/jira/browse/NIFI-8535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-8535: - Resolution: Fixed Status: Resolved (was: Patch Available) > 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)
[jira] [Updated] (NIFI-8535) PutDatabaseRecord should give a better message when the table cannot be found
[ https://issues.apache.org/jira/browse/NIFI-8535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-8535: --- Status: Patch Available (was: In Progress) > 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: 0.5h > 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)
