[ 
https://issues.apache.org/jira/browse/METRON-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16375110#comment-16375110
 ] 

ASF GitHub Bot commented on METRON-1462:
----------------------------------------

Github user ottobackwards commented on the issue:

    https://github.com/apache/metron/pull/943
  
    I think I mentioned contrib.  They don't have to go in contrib, I think at 
the time someone mentioned not wanting to maintain them.. If we don't then I 
thought contrib would make sense.
    We can keep them normal.
    
    Metron installation artifacts ( templates, schemas, kibana objects, 
queries, and dashboards ) should be managed separate from the kibana / es / 
solr /  packs.
    They are artifacts of metron and we need to support installing them on 
existing installations.
    If they need to be installed in a different phase, or as their own 
component, then fine.
    we need to break that down more anyway ( like package the 'demo' system + 
parser configs as optional ) maybe.
    
    
    



> Separate ES and Kibana from Metron Mpack
> ----------------------------------------
>
>                 Key: METRON-1462
>                 URL: https://issues.apache.org/jira/browse/METRON-1462
>             Project: Metron
>          Issue Type: Sub-task
>            Reporter: Michael Miklavcic
>            Assignee: Michael Miklavcic
>            Priority: Major
>
> Need this to enable our ability to provide pluggable Solr support.



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

Reply via email to