[
https://issues.apache.org/jira/browse/NIFI-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18072606#comment-18072606
]
ASF subversion and git services commented on NIFI-15803:
--------------------------------------------------------
Commit ec9a3a7be268a16c0aab112e9418b26b5e95a79c in nifi's branch
refs/heads/dependabot/npm_and_yarn/nifi-frontend/src/main/frontend/hono-4.12.12
from Alaksiej Ščarbaty
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ec9a3a7be26 ]
NIFI-15803 Record path format returns a string type (#11115)
> Invalid output field type in Format record path function
> --------------------------------------------------------
>
> Key: NIFI-15803
> URL: https://issues.apache.org/jira/browse/NIFI-15803
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 2.8.0
> Reporter: Alaksiej Ščarbaty
> Assignee: Alaksiej Ščarbaty
> Priority: Major
> Fix For: 2.10.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The {{format()}} RecordPath function preserves the source field's data type
> (e.g., LONG, INT) on the returned {{FieldValue}} instead of using STRING.
> When used with {{UpdateRecord}} to write a formatted timestamp into a new
> field, the destination field inherits the source's numeric type, which is
> incorrect.
> E.g. record:
> { "event_time": 1234567890 }
> expression in _UpdateRecord:_
> _/DATE = format(/event_time, 'yyy-MM-dd')_
> causes {{{}NumberFormatException{}}}, as writer expects the "DATE" fields to
> be of "LONG" type - based on the type of "event_time".
> Formatted fields should always be of a STRING type.
> *A concern:* this is a bug fix, but it's a breaking change. If someone
> expects that original data type is returned from format, the flow might break.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
