Hi Joe,
Thanks for the explanation, is there a Jira ticket for for a job management
mechanism? Is this a priority for a coming release?
Is there a lag between events occurring and them becoming searchable, if so
what settings help control this lag?
Thanks,
Eric
On Tue, Nov 3, 2020 at 2:35 PM
Thanks for the reply. Can you explain me in more detail. Where i can
configure end_point url and how to choose reigion "us-asburn-1" in existing
puts3 processor.
--
Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
Thanks, Matt! That's very helpful.
On Mon, Nov 2, 2020 at 12:57 PM Matt Burgess wrote:
> David,
>
> The documentation for the metrics is in the "help" section of the
> datapoint definition, if you hit the REST endpoint you can see the
> descriptions, also they are listed in code [1].
>
>
Eric,
short version: Provenance queries can absolutely take away CPU time from
the flow.
longer version:
They get the same priority as any other thread in nifi. Once prov queries
are being executed they use CPU. I would strongly advise against any
blending of the flow execution with provenance
Hello everyone,
I was wondering if it were possible for excessive use of the provenance api
would cause flowfile processing to slow down and even come to a halt? My
test setup queries the provenance API to see if all flowfiles that
descended from a given input file have completed processing. This
Hello,
Oracle Cloud Storage has an S3-compatible interface, so you should be able
to use the built-in List/Fetch/Put/Delete S3 processors as long as you can
handle the limitations of the S3 compatible API vs Oracle's native API.
See here for more information about using the S3 compatible API:
Pavel
What problem did you run into?
If it is pulling an empty result set, you just need to add the trailing slash.
See the solution here:
https://stackoverflow.com/questions/63549400/prometheusreportingtask-not-emitting-metrics-in-nifi
> On Oct 28, 2020, at 7:18 PM, Pavel S wrote:
>
> I
