I would log into cloudera, community support, and crest an issue.
Cloudera support is extremely good and they can certainly help you get started.
Vr
Sent from my iPhone
> On Aug 18, 2023, at 1:58 AM, huacheng xian wrote:
>
>
> Dear Nifi Team,
>
> I am a user of Nifi and I am facing some
Ah, so these processors have all been written for Elasticsearch, and use the
Elasticsearch low-level REST API library to form connections. They've not been
tested against OpenSearch, although hopefully should work for any interactions
where the API is the same, but the two products continue to d
Dear Nifi Team,
I am a user of Nifi and I am facing some issues that I hope you can help me
with. I have successfully installed Nifi on my local machine and can log in
to Nifi using localhost without any problems. However, I am unable to log
in when using a different address, such as my local netw
I did use the example and got errors. I'll revisit that (perhaps it is an
opensearch idiosyncrasy). The per response option is probably my issue.
I'll check that out and get back to you.
Thanks again
On Fri, Aug 18, 2023 at 2:30 PM Chris Sampson wrote:
> Check the example in the processor's add
Check the example in the processor's additional details docs [1] for how you
could set size and sort fields for the query - size is used to determine the
number of documents returned per page, sorry is required if using a "search
after" or "point in time" query type.
If the Query property is se
Thanks, that makes sense. I've had trouble getting a size parameter
accepted, but will work on that later.
However, I'm unsure what I should expect to see in the following test
scenario.
A fixed query in the Query parameter - a match all. i.e. nothing dynamic
set by upstream processing
An empty
Again, sounds like it's working as documented [1] - an input is required to
trigger the PaginatedJsonQueryElasticsearch processor, so something like
GenerateFlowFile is a way to achieve that if you want to periodically execute a
paginated query, e.g. by setting the Generate processor's schedule
I must be missing something simple. I've copied the parameters and query
from the SearchElasticSearch processor and I'm not getting errors, but no
flowfiles are produced.
I'm forced to add an input connection, despite coding the query in the
Query property. I have a GenerateFlowFile processor conn
There is no separate credential controller service for PutAzureEventHub.
The credential properties can be configured on the processor itself.
Setting "Use Azure Managed Identity" processor property to "true" should
work, assuming the Azure config is correct. I tested it with NiFi 1.23.0
running on
