[
https://issues.apache.org/jira/browse/METRON-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480617#comment-16480617
]
ASF GitHub Bot commented on METRON-1548:
----------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/1010
@justinleet I agree with you that it's not a serious problem. I think it
can be solved more easily with documentation and some manual steps from the
user. There is some logic we need to fix, specifically around substituting the
source.type.field value for "source:type" (I added comments for those). Other
than that, I'm good with documenting how to switch to Solr in the Solr feature
branch.
There is also the case of upgrading ES and using "source.type" since that
name is allowed in later versions. Is that something we need to think about
and document?
> 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)
