[GitHub] [nifi] ChrisSamo632 commented on pull request #4691: NIFI-7990 add properties to map Record field as @timestamp in output …

[GitBox <gi...@apache.org>]

ChrisSamo632 commented on pull request #4691:
URL: https://github.com/apache/nifi/pull/4691#issuecomment-937314291


   > I noticed that using the NIFI-7990.json flow definition, using `PutElasticsearchHttpRecord`, `@timestamp` for record "1" appears to be a numeric type but for record "2" it appears to be a string type:
   > ...
   > However, using `PutElasticsearchRecord`, `@timestamp` is consistently a numeric type:
   > ...
   > I don't know if this is actually a problem in ES, but wanted to point it out in case we need to update the @timestamp code to make it consistent in the two cases.
   
   Good spot! I think this was likely due to the `PutElasticsearchHttpRecord` processor **not** attempting to coerce the `@timestamp` field value if it had been provided via the direct `@timestamp` property _or_ from a Record Path field that was of DataType STRING. I intentionally changed `PutElasticsearchRecord` to `coerceStringToLong` - basically this is an addition to a [question I previously asked myself on this PR](https://github.com/apache/nifi/pull/4691#discussion_r532728519)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@nifi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org