metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From merrimanr <...@git.apache.org>
Subject [GitHub] metron issue #636: METRON-1022: Elasticsearch REST endpoint
Date Mon, 10 Jul 2017 19:33:33 GMT
Github user merrimanr commented on the issue:

    https://github.com/apache/metron/pull/636
  
    @ottobackwards just created a discuss thread on the general approach here.
    
    @cestella you're absolutely correct.  We need a way for solr and ES to coexist.  A precedent
has already been set in our indexing module but just want to throw another suggestion out
there.  The downside of having separate modules that extend a common module is that automated
deployment through Ambari MPack is more complex.  In fact, the current MPack doesn't support
this right now.  
    
    Ideally we could leverage Spring to easily swap out the implementation at runtime but
we would need both Solr and ES classes available on the classpath.  Would it be possible to
add lucene classes (and possibly others) to the list of shaded classes in the elasticsearch-shaded
module and create a similar module for Solr?  Or are there challenges I'm not thinking of
and/or would it make things more confusing having different strategies in different parts
of Metron?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message