Peter Kimberley

At this stage, basic [terms-based Elasticsearch suggestions](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-suggesters.html#term-suggester) have been implemented, as these do not require any special index mappings. A future extension point could be to allow per-field customisation of...

Attempted `mvn -Pcontrib-check clean install`, however current `main` branch is failing with errors about unapproved licenses: ``` NIFI-10646 Handle failed GeoIP lookups in `GeoEnrichIPRecord` processor ``` License failures are related...

Awaiting review by @mattyb149 into current handling of non-existent parent record nodes. Will revisit this PR once that is completed.

I think sticking to a common initial sequence would be more intuitive, with some exceptions made for commonly-used combinations in other web apps. Ctrl+Alt seems to be generally unused in...

Search "pause" functionality poses a problem for Elasticsearch searches. If a search is paused, the Elasticsearch query scroll context will expire after a pre-defined period of inactivity, causing the context...

+1 for this - highly desirable for our use case

Hi @nabokihms could you please review this when you get a chance? This is a blocker for our application and we'd appreciate if this PR could be assessed.

Consider using user-defined node attributes to be entered as a processor filter condition. A node to its attributes should be a one-to-many relationship.

Another idea is to allow the user to define a _weight_ for a processor filter. This would add nuance to the existing `priority` setting and allow users to further prioritise...

Some more suggestions: 4. Select one/multiple/all tasks in the view and terminate them (effectively to stop tasks by node or pipeline). Related to #2276. Consider using shift-click shortcut to select...