Kasper Sørensen created METAMODEL-214:
-----------------------------------------
Summary: Provide a JEST-independent way of interacting with
ElasticSearch-rest
Key: METAMODEL-214
URL: https://issues.apache.org/jira/browse/METAMODEL-214
Project: Apache MetaModel
Issue Type: New Feature
Reporter: Kasper Sørensen
As of METAMODEL-212 we have now a REST-client based ElasticSearch module. This
is built on top of the JEST library.
The fact that we use JEST is more of a technical detail though and I think we
should rather be able to remove that from our interface so that consumers of
our API does not need to worry about JEST at all. It will also enable us to
replace JEST in the future if we need to.
I see JEST "leaking" in our interface in two ways: In the constructor of
ElasticSearchRestDataContext and in the method "JestClient
getElasticSearchClient()". The latter is probably fine to keep since it is
anyways not a interface-method of DataContext. But it would also be good to
have some methods for the consumers to fire e.g. a search request and get a
search response (using the JEST client, but that would be encapsulated). I
think using the HTTP client classes here would be fine since HTTP client is a
bit more general and well-known.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
