[GitHub] metron issue #941: METRON-1355: Convert metron-elasticsearch to new infrastr...

[justinleet <gi...@git.apache.org>]

Github user justinleet commented on the issue:

    https://github.com/apache/metron/pull/941
  
    I'm unable to get the integration tests running locally.  I've been able to get the docker containers up and running, but ES isn't exposed at localhost, only through the explicit docker-machine ip.  This causes the integration tests to fail, as they are unable to successfully query against ES.
    Any idea why this is happening? Am I missing an env config or something?
    
    Also, is it worthwhile to wrap most of the setup in a script? There's enough steps that have to be taken that I'd really like a script that's just "setup_integration_env.sh".  Extra credit if it can be rolled into the maven build such that it just automagically takes care of it when we run the maven integration test target (or it's run by install or whatever).  It would be super nice if we didn't have to worry about anything other than just running the maven target.
    
    Regardless of what wrapping we do, it would be really nice to clean some stuff up so the integration test instructions become a one-shot "Here's the step by step". Right now, I had to look at the Travis run to figure out (remember) the semi-odd way we split unit and integration test calls in maven, etc.


---