FYI, I was able to work around this limitation by piping a GenerateFlowFile processor to my UpdateAttribute processor, and configuring the UpdateAttribute to set one additional attribute for each of the state items. This allowed me to generate a kind of report with all of my counters.
It still may be useful to be able to retrieve more than 500 state items from a processor, though. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Nov 22, 2017 at 11:14 AM, Joe Gresock <[email protected]> wrote: > I have an UpdateAttribute processor with advanced rules that will store a > counter for each of 239 attributes in the local state. This appears to > work just fine, as I see 956 total state items in the View State view (I > have 4 nodes in my cluster). However, I can't seem to retrieve more than > 500 items from the state. Filtering only appears to filter in the first > 500 items. Is there a way to retrieve more than 500 state items? > > -- > I know what it is to be in need, and I know what it is to have plenty. I > have learned the secret of being content in any and every situation, > whether well fed or hungry, whether living in plenty or in want. I can > do all this through him who gives me strength. *-Philippians 4:12-13* > -- I know what it is to be in need, and I know what it is to have plenty. I have learned the secret of being content in any and every situation, whether well fed or hungry, whether living in plenty or in want. I can do all this through him who gives me strength. *-Philippians 4:12-13*
