[NIFI-8223] PutDatabaseRecord should use table column datatype instead of field datatype

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.13.0
• Component/s: Extensions
• Assignee: Matt Burgess
• Reporter: Matt Burgess
• Created: 10/Feb/21 22:26
• Updated: 22/Feb/21 19:40
• Resolved: 11/Feb/21 01:03

Description

When PutDatabaseRecord calls putObject() to insert a field value into a prepared statement, it passes is the SQL type as determined from the NiFi record field's type. Most of the time this matches the table column's data type or else an error would occur when trying to put incompatible values into the column.

However in the case of the BIGINT and TIMESTAMP types, the field could be inferred to be BIGINT when the column is of type TIMESTAMP. There's no way to know for large integers whether they correspond to a "plain" number or a number of (milli)seconds for example. In this case PutDatabaseRecord throws an error because it tries to put a BIGINT value into a TIMESTAMP field.

This Jira proposes to improve this by comparing the field and column datatypes. If they match, either can be used. If they don't match, attempt to convert the value to the column datatype and use the column datatype in setObject(). If conversion is unsuccessful, fall back to the current behavior of using the field datatype and value.

Issue Links

• causes: NIFI-8237 PutDatabaseRecord can not insert into mysql table with TEXT column
• links to: GitHub Pull Request #4819