I think the word “trusted” is doing a lot of work here. As it stands, only
certificates that are either explicitly present or signed by a certificate
present in the corresponding truststore will be accepted. If the certificate is
self-signed, all that means is that an external entity (a
You can use a JsonTreeReader set to Infer Schema and use that in
JoltTransformRecord. But if your payload is one big JSON object (rather than a
top-level array of JSON objects), then you only have one record and should
stick to JoltTransformJson. If you do have an array, JoltTransformJson will
Ryan
By far the largest performance relevant activity is flow design itself. As
a last resort I'd look at repo changes.
Are you using the record processors? Does your data arrive in batches?
Thanks
On Thu, Sep 10, 2020 at 7:27 AM Ryan Hendrickson <
ryan.andrew.hendrick...@gmail.com> wrote:
Hi all,
I've got a NiFi running with a lot of small JSON files and I'm trying to
squeeze the most performance out of it.
I recently saw the new RocksDB FlowFile Repo (
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#rocksdb-flowfile-repository)
and was wondering what
Hi All,
I am using WebSocket for communication between two independently running
instances of NiFi.
SSLContextService is being used for Secure Communication(WSS).
Everything works fine and is tested with Self signed certificates.
However, I would like to make sure that the communication works only
