[
https://issues.apache.org/jira/browse/METRON-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475663#comment-16475663
]
ASF GitHub Bot commented on METRON-1548:
----------------------------------------
Github user sardell commented on the issue:
https://github.com/apache/metron/pull/1010
@justinleet I've changed the property to be `source.type.field` and added
the property to the documentation at
https://github.com/apache/metron/tree/master/metron-platform/metron-common#global-configuration.
I was slightly confused about the subset field, but I took an educated guess
and entered `UI` as the value. Let me know if this is not correct and I'll
update it.
> Alerts UI: Remove hardcoded source:type and other fields that may vary
> ----------------------------------------------------------------------
>
> Key: METRON-1548
> URL: https://issues.apache.org/jira/browse/METRON-1548
> Project: Metron
> Issue Type: Sub-task
> Reporter: Justin Leet
> Priority: Major
>
> In Solr, we use source.type instead of source:type (which was originally due
> to ES limitations, we'd prefer it to be common across both). However, it's
> hardcoded in the alerts UI to be source:type, so nothing in the UI has a
> source type and it breaks other things like metaalerts (which rely on source
> type for being able to pull the data together).
> Any other configs / queries that would cause similar problems should be
> updated appropriately.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
