Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wildfly tests use rest high level client #42186

Merged
merged 1 commit into from
May 17, 2019

Conversation

jaymode
Copy link
Member

@jaymode jaymode commented May 16, 2019

This change updates the Wildfly qa tests to make use of the
RestHighLevelClient in place of the transport client to pave the way
for the future removal of the transport client.

This change updates the Wildfly qa tests to make use of the
RestHighLevelClient in place of the transport client to pave the way
for the future removal of the transport client.
@jaymode jaymode added >test Issues or PRs that are addressing/adding tests :Core/Infra/Core Core issues without another label v8.0.0 labels May 16, 2019
@jaymode jaymode requested review from rjernst and jasontedor May 16, 2019 20:14
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

Copy link
Member

@rjernst rjernst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jaymode jaymode merged commit 6cea318 into elastic:master May 17, 2019
@jaymode jaymode deleted the wildfly_rest_client branch May 17, 2019 01:24
gurkankaymak pushed a commit to gurkankaymak/elasticsearch that referenced this pull request May 27, 2019
This change updates the Wildfly qa tests to make use of the
RestHighLevelClient in place of the transport client to pave the way
for the future removal of the transport client.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label >test Issues or PRs that are addressing/adding tests v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants