Skip to content

Conversation

@jasontedor
Copy link
Member

We accidentally switched to using the relative time provider here. This commit fixes this by switching to the appropriate absolute clock.

Closes #45254

We accidentally switched to using the relative time provider here. This
commit fixes this by switching to the appropriate absolute clock.
@jasontedor jasontedor added >bug :Distributed Indexing/Distributed A catch all label for anything in the Distributed Indexing Area. Please avoid if you can. v8.0.0 v7.4.0 v7.3.1 labels Aug 6, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

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

@jasontedor jasontedor merged commit 5508aba into elastic:master Aug 7, 2019
jasontedor added a commit that referenced this pull request Aug 7, 2019
We accidentally switched to using the relative time provider here. This
commit fixes this by switching to the appropriate absolute clock.
jasontedor added a commit that referenced this pull request Aug 7, 2019
We accidentally switched to using the relative time provider here. This
commit fixes this by switching to the appropriate absolute clock.
@jasontedor jasontedor deleted the absolute-clock-bulk-update branch August 7, 2019 01:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>bug :Distributed Indexing/Distributed A catch all label for anything in the Distributed Indexing Area. Please avoid if you can. v7.3.1 v7.4.0 v8.0.0-alpha1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Scripting: ctx._now is different when using Bulk API compared to Update API

4 participants