metron-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Allen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (METRON-1609) Elasticsearch settings in Ambari should not be required if Solr is the indexer
Date Tue, 04 Sep 2018 17:13:00 GMT

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

Nick Allen updated METRON-1609:
-------------------------------
    Fix Version/s:     (was: Next + 1)
                   0.6.0

> Elasticsearch settings in Ambari should not be required if Solr is the indexer
> ------------------------------------------------------------------------------
>
>                 Key: METRON-1609
>                 URL: https://issues.apache.org/jira/browse/METRON-1609
>             Project: Metron
>          Issue Type: Sub-task
>            Reporter: Nick Allen
>            Assignee: Nick Allen
>            Priority: Major
>             Fix For: 0.6.0
>
>         Attachments: Screen Shot 2018-06-06 at 12.34.13 PM.png, Screen Shot 2018-06-06
at 12.37.08 PM.png
>
>
> When a user deploys Metron with Solr, the Mpack requires that the user populate the Index
Settings > Elasticsearch Hosts field to continue, even when deploying a Metron cluster
that indexes to Solr.
> The other Elasticsearch specific fields on the Index Settings page are also required,
although defaults are provided and thus the user is not required to enter anything here. If
you remove the provided defaults, you can see that each of the fields are required, even when
Elasticsearch will not be used.
> * The Elasticsearch related properties under the Ambari 'Index settings' tab should only
be required if Elasticsearch is chosen as the indexer.
> * The Solr related properties under the 'Index Settings' tab should only be required
if Solr is chosen as the indexer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message