Hi Alex, Listing only supports the top 100 items. It is not meant to provide exhaustive listing of flow files in a given queue. It's more a way to have a live look into the queue: check attributes, content, ordering, etc.
What is your use case? Any specific reason to list all the flow files in a given queue? Pierre 2017-10-18 11:35 GMT+02:00 Willmer, Alex (UK Defence) <[email protected]> : > Hello all, > > Is it possible to list more than 100 flow files in a Queue? Either through > specifying a higher maxResults, or requesting paged results? > > The endpoint when creating a listing request defaults to maxResults=100, > and doesn't appear to allow overriding it. E.g. to give an anonymised > example, using HTTPie as the client against NIFI 1.2.0 from HDF 3.0.0.0 > > $ http POST https://example.org/nifi-api/01234567-89ab-cdef-0123- > 456789abcdef/listing-requests > POST /nifi-api/01234567-89ab-cdef-0123-456789abcdef/listing-requests > HTTP/1.1 > Accept: application/json, */* > Accept-Encoding: gzip, deflate > Content-Type: application/json > Host: example.org > > { > "listingRequest": { > ... > "maxResults": 100, > ... > } > } > > Sending {"maxRequests": 1000} or {"listingRequest": {"maxResults": 1000}) > in the request body has the same result. Sending maxRequests=1000 as a URL > parameter or form data causes an HTTP 500 error. > > Is 100 results a hard coded limit? If so, is that intentional? > > With thanks, Alex > -- > Alex Willmer | Developer > Space, Defence and National Security | CGI > 250 Brook Drive, Green > <https://maps.google.com/?q=250+Brook+Drive,+Green&entry=gmail&source=g> > Park, Reading, RG2 6UA > [email protected] | cgi-group.co.uk >
