[
https://issues.apache.org/jira/browse/NIFI-10635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618956#comment-17618956
]
ASF subversion and git services commented on NIFI-10635:
--------------------------------------------------------
Commit a76abef270f7ac875a509060f81a491ca49b0a9d in nifi's branch
refs/heads/main from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a76abef270 ]
NIFI-10635: Fix handling of enums in PutDatabaseRecord
Signed-off-by: Nathan Gough <thena...@gmail.com>
This closes #6518.
> Enum in Avro schema not working in PutDatabaseRecord
> ----------------------------------------------------
>
> Key: NIFI-10635
> URL: https://issues.apache.org/jira/browse/NIFI-10635
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Jonathan Keller
> Assignee: Matt Burgess
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> There appears to be a regression in the PutDatabaseRecord processor with
> 1.13.0 (works in 1.12.1)
> I have an Avro schema for a record which contained enum fields. After
> upgrading, a processor which had been working was failing on errors, stating
> it could not find the record type. The field in question is defined as below.
> The files which were erroring out were the exact same files, and no changes
> had been made to the schema or the CSV reader controller between the tests.
> I was also able to successfully move the flow.xml.gz file back to the older
> version of NiFi and the PutDatabaseRecord processor was able to work again to
> insert the database records.
> {noformat}
> {
> "name": "PER_ORG",
> "type": {
> "type": "enum",
> "name": "PerOrgFlag",
> "symbols": [
> "EMP",
> "CWR"
> ]
> }
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
