David,
Attributes are always Strings. I don’t think you can change how they are
represented in AttributesToJSON.
My recommendation would be to not use that processor and instead use
ReplaceText with a Replacement Strategy as Always. Then you can build the JSON
to look however you want by doing
You could probably use a JOLT Transform on the NiFi side (although I’m no JOLT
expert).
From an Elasticsearch point of view, if you create an index template [1] for
the destination index with mappings to store the fields as numbers, I think
Elasticsearch will do the conversion for you (pretty s
Hi
I am using the attributesToJSON processor to create a JSON flowfile which I
then send to Elastic, I have noticed that some of my attributes which ar
numbers such as file size always come out of the attributesToJSON processor as
string values (ie with double quotes around them), therefore when
