[
https://issues.apache.org/jira/browse/NIFI-8244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess resolved NIFI-8244.
--------------------------------
Fix Version/s: 1.13.1
1.14.0
Assignee: Matt Burgess
Resolution: Fixed
I tried the scenario from the description with the fix from NIFI-8237, so I
think it is fixed as well. Please feel free to reopen if that's not the case.
> PutDatabaseRecord incorrect type resolution for partial columns
> ---------------------------------------------------------------
>
> Key: NIFI-8244
> URL: https://issues.apache.org/jira/browse/NIFI-8244
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.13.0
> Reporter: Dorian Bugeja
> Assignee: Matt Burgess
> Priority: Major
> Fix For: 1.14.0, 1.13.1
>
> Attachments: image-2021-02-20-02-18-10-670.png,
> image-2021-02-20-02-18-51-952.png, image-2021-02-20-02-26-24-986.png
>
>
> Record schema type resolution for PutDatabaseRecord is being performed using
> fieldIndexes computed in generateInsert/Update/Delete. Problem is that when
> not all keys in the records are defined or the sequence of the keys in the
> record does not match the sequence of the column name of the table,
> includedColumns, which is being populated with the index of the currentRecord
> (JSON for example) rather than the index of the table schema, will result in
> incorrect type resolution. Meaning that in the following example, `count`
> will be converted to String, as the second column in table is a String
> (Performing UPDATE in PutDatabaseRecord with Update key set to id)
> Table definition =
> id INT,
> title VARCHAR,
> count INT
> Record Update
> {"id": 1, "count": 10}
> !image-2021-02-20-02-18-51-952.png!
> !image-2021-02-20-02-18-10-670.png!
> !image-2021-02-20-02-26-24-986.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
