[
https://issues.apache.org/jira/browse/METRON-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505071#comment-16505071
]
ASF GitHub Bot commented on METRON-1608:
----------------------------------------
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1055
FYI - There is also another `source.type.field` reference that would be an
easy update
[here](https://github.com/apache/metron/blob/71a015fabc47b23ea0c5400fa239fee9f5c0d194/metron-interface/metron-rest/src/test/java/org/apache/metron/rest/service/impl/SearchServiceImplTest.java#L186)
> Add configuration for threat.triage.field name
> ----------------------------------------------
>
> Key: METRON-1608
> URL: https://issues.apache.org/jira/browse/METRON-1608
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
> Priority: Major
>
> Currently there is an option for replacing '.'s with ':'s in Elasticsearch
> field names. This is the default behavior. However our current version of
> Elasticsearch (5.6.2) now allows '.'s so it's possible for users to use '.'s
> instead. In the DAO implementation (metaalerts specifically), the
> threat.triage.field is hardcoded with ':'s and will not work properly if a
> user switches to using '.'s.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
