[ILM] reduce time restriction on IndexLifecycleExplainResponse#35954
Merged
talevy merged 1 commit intoelastic:masterfrom Nov 27, 2018
Merged
[ILM] reduce time restriction on IndexLifecycleExplainResponse#35954talevy merged 1 commit intoelastic:masterfrom
talevy merged 1 commit intoelastic:masterfrom
Conversation
step times were set. The assumption was that these are always set. Tests passed, which led me to believe this was true. There is a time when shrunk indices have their step phase/action/step details set, but with no time information (in the CopyExecutionStateStep). Explain API fails for these
talevy
added
>bug
blocker
:Data Management/ILM+SLM
Collaborator
|
Pinging @elastic/es-core-features |
Contributor
Author
|
I've opened this to discuss an alternative solution that the original commit in the PR does not address. That is to have CopyExecutionStateStep set phase_time,action_time,step_time. To be on the safe side, since this is very cosmetic, I went with just making the constructor more lenient |
colings86
approved these changes
Nov 27, 2018
Contributor
|
CopyExecutionStateStep should probably copy the times as well - the whole idea is to have the shrunken index completely replace the original, so it should take the times with it. |
Contributor
Author
|
@gwbrown I agree. I also think a part of that change should add validation of null values for these relevant fields in the LifecycleExecutionState constructor. I am also not sure what the correct step_time. the best estimate is the time of the step from the original index. |
Contributor
Author
|
test this please |
talevy
added a commit
that referenced
this pull request
Nov 27, 2018
step times were set. The assumption was that these are always set. Tests passed, which led me to believe this was true. There is a time when shrunk indices have their step phase/action/step details set, but with no time information (in the CopyExecutionStateStep). Explain API fails for these
jasontedor
added a commit
to jasontedor/elasticsearch
that referenced
this pull request
Nov 28, 2018
* master: DOCS Audit event attributes in new format (elastic#35510) Scripting: Actually add joda time back to whitelist (elastic#35965) [DOCS] fix HLRC ILM doc misreferenced tag Add realm information for Authenticate API (elastic#35648) [ILM] add HLRC docs to remove-policy-from-index (elastic#35759) [Rollup] Update serialization version after backport [Rollup] Add more diagnostic stats to job (elastic#35471) Build: Fix gradle build for Mac OS (elastic#35968) Adds deprecation logging to ScriptDocValues#getValues. (elastic#34279) [Monitoring] Make Exporters Async (elastic#35765) [ILM] reduce time restriction on IndexLifecycleExplainResponse (elastic#35954) Remove use of AbstractComponent in xpack (elastic#35394) Deprecate types in search and multi search templates. (elastic#35669) Remove fromXContent from IndexUpgradeInfoResponse (elastic#35934)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
step times were set. The assumption was that these are always set.
Tests passed, which led me to believe this was true. There is a time
when shrunk indices have their step phase/action/step details set,
but with no time information (in the CopyExecutionStateStep).
Explain API fails for these