[NIFI-2531] SQL-to-Avro processors do not convert BIGINT correctly

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0, 0.7.0
• Fix Version/s: 1.0.0
• Assignee: Matt Burgess
• Reporter: Matt Burgess
• Created: 09/Aug/16 17:51
• Updated: 27/Sep/16 13:29
• Resolved: 10/Aug/16 19:20

Description

For the SQL to Avro processors that use JdbcCommon (such as ExecuteSQL), if a BigInteger object is being put into an Avro record, it is being put in as a String. However when the Avro schema is created and the SQL type of the column is BIGINT, the schema contains the expected type "long" (actually a union between null and long to allow for null values). This causes errors such as:
UnresolvedUnionException: not in union: ["null", "long"]

If a BigInteger is retrieved from the result set and the SQL type is BIGINT, then its value is expected to fit into 8 bytes and should thus be converted to a long before storing in the Avro record.

Issue Links

• relates to: NIFI-2811 JdbcCommon doesn't convert bigint(20) column.
• relates to: NIFI-2624 JDBC-to-Avro processors handle BigDecimals as Strings
• links to: GitHub Pull Request #823