You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Shane Ardell (Jira)" <ji...@apache.org> on 2019/11/04 16:40:00 UTC

[jira] [Assigned] (METRON-2306) [UI] Grok parsers' have duplicate timestampField

     [ https://issues.apache.org/jira/browse/METRON-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shane Ardell reassigned METRON-2306:
------------------------------------

    Assignee: Shane Ardell

> [UI] Grok parsers' have duplicate timestampField
> ------------------------------------------------
>
>                 Key: METRON-2306
>                 URL: https://issues.apache.org/jira/browse/METRON-2306
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Shane Ardell
>            Assignee: Shane Ardell
>            Priority: Major
>         Attachments: Screen Shot 2019-10-30 at 4.41.14 PM.png, Screen Shot 2019-10-30 at 4.41.21 PM.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Right now, existing Grok parsers in the UI have two timestamp name fields. One is a field is used to force a user to add a name in the case of creating a grok parser, and the other allows the user to edit the existing name (or delete it altogether!). See the attached image for reference.
> A simple fix would be to hide the first mentioned instance if the parser isn't new. Another possibility is just removing the first field altogether and requiring the parser config object to have the timestampField property if it's a Grok parser. We also might want to remove the capability to delete the timestampField in the second instance since that's a required field for Grok parsers.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)