[
https://issues.apache.org/jira/browse/NIFI-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16548086#comment-16548086
]
ASF GitHub Bot commented on NIFI-3964:
--------------------------------------
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/1925
I'm certainly not a grok expert and probably using it in simplest cases,
but in all the log ingestion use cases I'm working on, I'm usually fine with
the default patterns file (already loaded from classpath with the
processor/reader CS) and a few additional patterns for the log sources I'm
dealing with.
I'm not sure to see why composite groks would be an issue here? (I updated
the unit test to use one)
Do you have an example in mind? (again not a Grok expert :))
> 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)
