anaylor commented on pull request #4641:
URL: https://github.com/apache/nifi/pull/4641#issuecomment-732376543
Our use case would be for tracking specific files throughout the system.
Sometimes we get asked about where a specific file is on our system, with a
queue limit of 100 we don't
anaylor commented on pull request #4641:
URL: https://github.com/apache/nifi/pull/4641#issuecomment-731356318
I did not realize flowfiles could have arbitrarily large attributes, I only
tested with default flow file attributes. If you had arbitrarily large
attributes there would be a huge
anaylor commented on pull request #4641:
URL: https://github.com/apache/nifi/pull/4641#issuecomment-731329752
@joewitt @markobean @taftster
It does not seem like any swap events are kicked off directly from
requesting a listing of the active queue. When a listing is created (for
anaylor commented on pull request #4641:
URL: https://github.com/apache/nifi/pull/4641#issuecomment-728278173
@joewitt Ok I see where you are coming from. I will take a deeper dive into
the mechanisms of how active and swap queues are managed to see if there are
ramifications to pulling
anaylor commented on pull request #4641:
URL: https://github.com/apache/nifi/pull/4641#issuecomment-726189727
@joewitt Looking at your comments on
[4221](https://github.com/apache/nifi/pull/4221). The limit of 100 is safe but
not particularly useful for examining a queue of flow files.
anaylor commented on pull request #4641:
URL: https://github.com/apache/nifi/pull/4641#issuecomment-726070577
Good call, I missed the second "View All" on the bottom
As for the limitation of the View All, I included a tooltip message that the
number of messages is limited by
