Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

REST API /controller/search-results query syntax?

Solved Go to solution
Highlighted

REST API /controller/search-results query syntax?

https://nifi.apache.org/docs/nifi-docs/rest-api/index.html

I can pull all of the data about a NiFi data flow using the /controller/search-results api call, but the request section also mentions a 'q' parameter (for query). There was no mention of the query syntax in the doc, however, any pointers? Would like to avoid pulling in a full config every time and parse on a constrained device, if possible.

1 ACCEPTED SOLUTION

Accepted Solutions

Re: REST API /controller/search-results query syntax?

Rising Star

The 'q' parameter is free-form (though URL encoded since it's part of the URL) and is whatever text you are searching for. For instance, it could be the UUID of a Processor, a Property Name or value, etc. If you search in the UI by typing into the Search field in the top-right corner, this just queries that API with whatever you typed into the Search box as the 'q' parameter.

2 REPLIES 2

Re: REST API /controller/search-results query syntax?

Rising Star

The 'q' parameter is free-form (though URL encoded since it's part of the URL) and is whatever text you are searching for. For instance, it could be the UUID of a Processor, a Property Name or value, etc. If you search in the UI by typing into the Search field in the top-right corner, this just queries that API with whatever you typed into the Search box as the 'q' parameter.

Re: REST API /controller/search-results query syntax?

Thanks Mark, so this is a quick way to search for 'expected' components and get an actual ID handle to work with them next. My use case is programmatic flow control through an API.

Don't have an account?
Coming from Hortonworks? Activate your account here