[
https://issues.apache.org/jira/browse/METRON-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667680#comment-16667680
]
ASF GitHub Bot commented on METRON-1834:
----------------------------------------
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.
> Migrate Elasticsearch from TransportClient to new Java REST API
> ---------------------------------------------------------------
>
> Key: METRON-1834
> URL: https://issues.apache.org/jira/browse/METRON-1834
> Project: Metron
> Issue Type: Improvement
> Reporter: Michael Miklavcic
> Assignee: Michael Miklavcic
> Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
