Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1242
@ottobackwards @nickwallen - just to shed some additional light on the
choices made here, take a look at the DAO classes. The new
`ElasticsearchClient` Metron client class lays some foundation towards wrapping
the ES API. What this PR explicitly does *not* do is completely abstract away
the ES dependencies. I believe that's a task that we should perform, but I do
not believe it makes sense to couple it with the task of swapping out the
client.
---
