You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Otto Fowler (Jira)" <ji...@apache.org> on 2022/04/02 17:39:00 UTC
[jira] [Updated] (NIFI-9863) Controller Service for managing custom Grok patterns
[ https://issues.apache.org/jira/browse/NIFI-9863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Otto Fowler updated NIFI-9863:
------------------------------
Description:
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.
> 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)