[
https://issues.apache.org/jira/browse/NIFI-9863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17516993#comment-17516993
]
David Handermann commented on NIFI-9863:
----------------------------------------
Thanks for the clarification and additional details [~otto]. It sounds like
there is some opportunity to straight out terminology in existing NiFi
documentation.
As far as the feature itself, could you describe what the Controller Service
interface would look like? If the primary goal is simply to make custom Grok
Patterns sharable across component instances, it seems like this could be
accomplished through a combination of implementing NIFI-3964 using Resource
References, and building a configuration based on Parameter Contexts. In other
words, it would accomplish the same goal as implementing a Controller Service
that looked something like the following:
{noformat}
interface GrokPatternService {
List<String> getGrokPatterns();
}
{noformat}
If there is more that a Controller Service could do, then I could see more
development in this current issue.
I will take another look at NIFI-3964 and perhaps implementing an improvement
there would help move the discussion forward as well.
> 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)
