[
https://issues.apache.org/jira/browse/METRON-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305926#comment-15305926
]
ASF GitHub Bot commented on METRON-189:
---------------------------------------
Github user cestella commented on the pull request:
https://github.com/apache/incubator-metron/pull/138#issuecomment-222363626
Yeah, the documentation situation is a bit incorrect. Documentation for
configuration started to be placed where the configuration objects existed,
rather than where they were used. Since we put the configuration in commons,
then the documentation went in commons. I suggest strongly that we do a
follow-on after we flush the PR queue to move docs around.
> Add the ability to do global validations on messages passing through the
> parser.
> --------------------------------------------------------------------------------
>
> Key: METRON-189
> URL: https://issues.apache.org/jira/browse/METRON-189
> Project: Metron
> Issue Type: New Feature
> Reporter: Casey Stella
> Assignee: Casey Stella
>
> Allow the user to specify field level or message level validations to ensure
> messages coming from the parser are valid. For instance, allow the ability
> ensure that a field is an IPv4 address.
> If a field is invalid, send to a separate stream from the parser bolt.
> Follow-on work should be done to send this stream to the index for
> after-the-fact inspection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
