[
https://issues.apache.org/jira/browse/NIFI-9863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518201#comment-17518201
]
David Handermann commented on NIFI-9863:
----------------------------------------
Thanks for summarizing the ideal Controller Service methods. In order to make
use of those various methods, it seems like the GrokReader would also require
additional refinements. For example, how would the GrokReader know which
Expressions or Patterns to use from the Controller Service?
At a glance, not all of the proposed methods seem necessary, but it is helpful
as a way to consider the types of features you described.
It might make sense to create a new Grok-based Reader that is capable of more
configurable handling of which Expressions and Patterns to select, versus
attempting to fit it in with the current implementation. It depends on how
well it would fit with the current design.
With that background on the Controller Service, how do you anticipate
configuring and selecting these values in the context of a Grok-based Reader?
> Controller Service for managing custom Grok patterns
> ----------------------------------------------------
>
> Key: NIFI-9863
> URL: https://issues.apache.org/jira/browse/NIFI-9863
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Otto Fowler
> Priority: Major
>
> Managing custom Grok expressions in properties for the Grok processors or
> Record readers is cumbersome and not ideal.
> Having a service that managed these expressions in a centralized and reusable
> way would be a benefit to those using Grok patterns.
> This service would allow the configuration of some number custom Grok
> patterns as the service configuration. The MVP would be manual entry, but
> loading patterns from File ( upload to configuration? ) or from some external
> location could be allowed as well down the line.
> In use, it could be argued that the patterns should be loaded from something
> like the schema registry.
> consumers of the service should then be able select the specific service
> instance and then using dependent properties select which patterns provided
> by the service to consume.
> To this end, it may be nice to have the service support pattern 'groups',
> such that you can select all patterns for a group at once. This would be the
> easy button version of the linked multiple expressions to grok reader issue.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
