[
https://issues.apache.org/jira/browse/NIFI-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023351#comment-16023351
]
Pierre Villard commented on NIFI-3964:
--------------------------------------
Hey [~joewitt], I agree that we should avoid the need to deploy files over the
NiFi nodes. I'm not sure to understand the Lookup Service approach though. All
the defined patterns need to be loaded in the Grok instance when the processor
is scheduled. Can't see how the lookup api can provide a "get all" patterns
that would be defined in the controller service. Did you have in mind to add a
method in the lookup service interface to get all key/value pairs defined in
the controller service and add a controller service where key/value pairs are
defined using dynamic properties?
> Grok processors - Allow multiple pattern configuration files
> ------------------------------------------------------------
>
> Key: NIFI-3964
> URL: https://issues.apache.org/jira/browse/NIFI-3964
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Trivial
>
> When using a lot of grok processors with different teams and use cases, it
> would be useful to be able to split the pattern file in different files that
> can be individually managed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
