[
https://issues.apache.org/jira/browse/NIFI-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16548038#comment-16548038
]
ASF GitHub Bot commented on NIFI-3964:
--------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/nifi/pull/1925
I don't think adding groks, one at a time is very feasible. Also, since
groks can be compound and build on other groks, possibly from other files etc,
having to load every grok in every instance of the controller as a dynamic
property is going to be very tough for the user. Many times you don't just
need one grok, you need many to build up to that one. Thinking of groks as
atomic vs. sets I think is awkward.
If the ui could load one or more files containing groks, and add the
properties from each file for you, that would work... but that still seems
wrong.
The groks should be in the registry, as named grok files possibly
> Grok processors - Allow custom patterns without contiguration file
> ------------------------------------------------------------------
>
> 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 provide a way of customizing the Grok patterns without the
> need of deploying files over the nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
