[ 
https://issues.apache.org/jira/browse/NIFI-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Villard resolved NIFI-15803.
-----------------------------------
    Fix Version/s: 2.10.0
       Resolution: Fixed

> 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)

Reply via email to