Hi Phil,
You might have uncovered a gap in the permission policy. Have you tried using
the “modify the data” permission [1]? If a user does not have write permission
to the queue, I think they can empty it but not modify/delete the queue itself.
I am speculating here because I haven’t had a ch
Hi there,
I am trying to stratify my userbase. I need to allow certain users/groups
the ability to clear queues, but cannot find the right policy to allow that
without also allowing them to delete queues, which I absolutely don’t want
to do.
Am currently using 1.9.2 (putting off the upgrade proce
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
I’m working on deploying NiFi to Kubernetes and I’ve ran across several things
that could be improved.
1. Currently flow.xml.gz is stored in ./conf by default which has been
designated a Docker volume. In Kubernetes volumes are not pre-populated from
the image so I’m left with some init con
