<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: REST API /controller/search-results query syntax? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/REST-API-controller-search-results-query-syntax/m-p/96485#M9993</link>
    <description>&lt;P&gt;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.&lt;/P&gt;</description>
    <pubDate>Thu, 05 Nov 2015 02:31:57 GMT</pubDate>
    <dc:creator>andrewg</dc:creator>
    <dc:date>2015-11-05T02:31:57Z</dc:date>
    <item>
      <title>REST API /controller/search-results query syntax?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/REST-API-controller-search-results-query-syntax/m-p/96483#M9991</link>
      <description>&lt;P&gt;&lt;A target="_blank" href="https://nifi.apache.org/docs/nifi-docs/rest-api/index.html"&gt;https://nifi.apache.org/docs/nifi-docs/rest-api/index.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I can pull all of the data about a NiFi data flow using the &lt;STRONG&gt;/controller/search-results&lt;/STRONG&gt; 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.&lt;/P&gt;&lt;P&gt;&lt;A target="_blank" href="https://nifi.apache.org/docs/nifi-docs/rest-api/index.html"&gt;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Apr 2026 12:34:39 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/REST-API-controller-search-results-query-syntax/m-p/96483#M9991</guid>
      <dc:creator>andrewg</dc:creator>
      <dc:date>2026-04-21T12:34:39Z</dc:date>
    </item>
    <item>
      <title>Re: REST API /controller/search-results query syntax?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/REST-API-controller-search-results-query-syntax/m-p/96484#M9992</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Nov 2015 02:30:02 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/REST-API-controller-search-results-query-syntax/m-p/96484#M9992</guid>
      <dc:creator>mpayne</dc:creator>
      <dc:date>2015-11-05T02:30:02Z</dc:date>
    </item>
    <item>
      <title>Re: REST API /controller/search-results query syntax?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/REST-API-controller-search-results-query-syntax/m-p/96485#M9993</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Nov 2015 02:31:57 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/REST-API-controller-search-results-query-syntax/m-p/96485#M9993</guid>
      <dc:creator>andrewg</dc:creator>
      <dc:date>2015-11-05T02:31:57Z</dc:date>
    </item>
  </channel>
</rss>

