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

Backport #6027 to 4.5 - Pass Transport object as the context when callWithRequest is asked to use a transport method #6483

Merged
merged 1 commit into from
Mar 9, 2016

Conversation

spalger
Copy link
Contributor

@spalger spalger commented Mar 9, 2016

#6027 fixes the way that callWithRequest handles alternate context's (like transport) and is needed in 4.5.

… when called normally instead of assuming client is the context for everything
@Bargs
Copy link
Contributor

Bargs commented Mar 9, 2016

Pending tests passing, LGTM

@Bargs
Copy link
Contributor

Bargs commented Mar 9, 2016

Er, wait a sec. @spalger the description says this is supposed to backport to 4.5, but the pull actually targets 4.x which is 4.6. Does this need to be backported to 4.5, 4.6, or both?

@spalger
Copy link
Contributor Author

spalger commented Mar 9, 2016

Ah, good catch.

@spalger spalger added the v4.6.0 label Mar 9, 2016
spalger added a commit that referenced this pull request Mar 9, 2016
@spalger spalger merged commit 924386e into elastic:4.x Mar 9, 2016
@epixa epixa added the backport label Mar 9, 2016
@elasticsearch-bot
Copy link

Spencer Alger merged this into the following branches!

Branch Commits
4.5 335a276

elasticsearch-bot pushed a commit that referenced this pull request Mar 9, 2016
… when called normally instead of assuming client is the context for everything

Fixes #6483
@epixa
Copy link
Contributor

epixa commented Mar 9, 2016

Can we try to get into the habit of adding the backport label to these types of PRs? It'll help with PR verification to be able to check the commits or code in the backport PR itself, whereas the original PR is more useful when creating things like release notes. The backport label allows for filtering out these PRs in the latter case.

@spalger
Copy link
Contributor Author

spalger commented Mar 9, 2016

👍

@epixa epixa changed the title Backport #6027 to 4.5 Backport #6027 to 4.5 - Pass Transport object as the context when callWithRequest is asked to use a transport method Aug 26, 2016
@spalger spalger deleted the backport/6027 branch April 5, 2018 03:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants