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.

Sign up for GitHub

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

Jump to bottom

Make sure that update internal requests share the same original headers and request context #7766

Merged
merged 2 commits into from Sep 18, 2014
Merged

Make sure that update internal requests share the same original headers and request context #7766

merged 2 commits into from Sep 18, 2014

Commits on Sep 18, 2014

  1. Internal: make sure that all delete mapping internal requests share t… 

    …he same original headers and context

Delete mapping executes flush, delete by query and refresh operations internally. Those internal requests are now initialized by passing in the original delete mapping request so that its headers and request context are kept around.

Closes elastic#7736
    @javanna
    javanna committed Sep 18, 2014
    Copy the full SHA
    b9b5842 View commit details
    Browse the repository at this point in the history

  2. Internal: make sure that update internal requests share the same orig… 

    …inal headers and request context

Update request internally executes index and delete operations. We need to make sure that those internal operations hold the same headers and context as the original update request. Achieved via copy constructors that accept the current request and the original request.

Closes elastic#7766
    @javanna
    javanna committed Sep 18, 2014
    Copy the full SHA
    6717de9 View commit details
    Browse the repository at this point in the history