-
Type:
Task
-
Resolution: Done
-
Priority:
L3 - Default
-
Affects Version/s: None
-
Component/s: backend
AT:
- Optimize uses the new java high level rest client instead of the transport client
Background:
- The new rest-client is more flexible as it is not bound to a specific version in contrast to the transport client. Especially, if a client uses its own Elasticsearch this might become a problem.
- The performance is close to the transport client
- the new rest client does not ship with all the dependencies as the Transport client
- the transport client is going to become deprecated in Elasticsearch 6.x
Java high level rest client: https://www.elastic.co/guide/en/elasticsearch/client/java-rest/current/java-rest-high.html
1.
|
Use rest client to initialize Elasticsearch schema on startup |
|
Done | Unassigned |
2.
|
Log all elasticsearch queries when debug level is trace |
|
Done | Unassigned |
3.
|
Replace existing Elasticsearch request in the reader classes with the new rest client |
|
Done | Unassigned |
4.
|
Use the new rest client to write data to Elasticsearch |
|
Done | Unassigned |
5.
|
Remove the transport client from Optimize |
|
Done | Unassigned |
6.
|
Remove manual x-pack library affix from secure elasticsearch section in documenation |
|
Done | Unassigned |
7.
|
Replace Elasticsearch low levelclient builder with high level client builder |
|
Done | Unassigned |