Sander Bylemans created NIFI-11647:
--------------------------------------
Summary:
org.apache.nifi.serialization.record.util.DataTypeUtils.getSQLTypeValue does
not map UUID RecordFieldType
Key: NIFI-11647
URL: https://issues.apache.org/jira/browse/NIFI-11647
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Reporter: Sander Bylemans
org.apache.nifi.serialization.record.util.DataTypeUtils.getSQLTypeValue does
not map the RecordFieldType UUID.
This causes the PutDatabaseRecord to fail when trying to INSERT a flowfile with
a UUID as logical type with the error message:
{code}
2023-06-05 22:03:29,872 ERROR [Timer-Driven Process Thread-11]
o.a.n.p.standard.PutDatabaseRecord
PutDatabaseRecord[id=8f505e85-8058-3714-ac24-aaeeb5efc6a3] Failed to put
Records to database for
StandardFlowFileRecord[uuid=cedad728-117a-4235-9251-ded3b7580b7b,claim=StandardContentClaim
[resourceClaim=StandardResourceClaim[id=1685995389355-150, container=default,
section=150], offset=2643,
length=6551],offset=0,name=fase_3.2.23_00000000000000699164_00000000000000699164.parquet,size=4991].
Routing to failure.
org.apache.nifi.serialization.record.util.IllegalTypeConversionException:
Cannot convert unknown type UUID
at
org.apache.nifi.serialization.record.util.DataTypeUtils.getSQLTypeValue(DataTypeUtils.java:2148)
at
org.apache.nifi.processors.standard.PutDatabaseRecord.executeDML(PutDatabaseRecord.java:723)
at
org.apache.nifi.processors.standard.PutDatabaseRecord.putToDatabase(PutDatabaseRecord.java:970)
at
org.apache.nifi.processors.standard.PutDatabaseRecord.onTrigger(PutDatabaseRecord.java:493)
at
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1356)
at
org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:246)
at
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:102)
at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at
java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
{code}
Possibly more are affected.
This was added in https://issues.apache.org/jira/browse/NIFI-9981 and there was
already concern for the need of mapping a UUID.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
