Hi,
I recently developed a combination of a jar file and groovy script
called by the ExecuteGroovyScript processor. I remain confused about
what I need to do to ensure that a new version of the jar file gets
recognised by the processor. Is there a way to force this to happen
without restarting the
A working solution:
PartitionRecord on blobID and blobSize, route on attribute for
blobSize = record.count. The non matching branch goes through
PartitionRecord again, this time on blobID, blobSize and blobIndex,
which functions as split, but attaching content as attributes. Then
through
Hi All,
To further debug this issue, I set the fetch size to 50 and Max rows per
file to 100 as shown below image.
[image: image.png]
I have set the initial heap size to 8GB and Max heap size to 15GB in the
bootstrap.conf file.
I started monitoring CPU and Memory with a 'top' command before
Hi Martin,
This was addressed in 1.13 by NIFI-7856 [1].
Thanks
-Mark
[1] https://issues.apache.org/jira/browse/NIFI-7856
On May 14, 2021, at 6:02 AM, Hengesbach, Martin
mailto:martin.hengesb...@fiz-karlsruhe.de>>
wrote:
Hi All,
I have a problem with the data provenance repository.
In