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

alias in rollup target_index field #445

Merged
merged 20 commits into from
Nov 3, 2022

Conversation

petardz
Copy link
Contributor

@petardz petardz commented Aug 5, 2022

Signed-off-by: Petar Dzepina petar.dzepina@gmail.com

Issue #, if available: #61

Description of changes:

Added support for using alias in rollup's target_index field

CheckList:

  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@petardz petardz requested a review from a team August 5, 2022 20:29
@petardz petardz force-pushed the alias_in_target_index branch 4 times, most recently from fad78ae to ad231f9 Compare August 5, 2022 20:42
@petardz petardz changed the title initial commit alias in target_index field Aug 5, 2022
@petardz petardz changed the title alias in target_index field alias in rollup target_index field Aug 5, 2022
@petardz petardz force-pushed the alias_in_target_index branch 2 times, most recently from 7a6bade to 89031ce Compare August 10, 2022 18:40
Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
…ensearch-project#435)

* tests
* small refactor/improvements
* added wildcard check when creating rollup job; removed resolving targetIndex on Rollup init; added test for wildcards
* lint fixes
* moved target_index validation in getRollup resp handler
* removed catch block
* exception fix
* linter fix
* fixed IT fail
* added Exception catch block

Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
* reverted old error messages
* reverted checking for matching jobs on whole set instead of job by job; Added picking rollup job deterministic
* fixed sorting

Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
* fixed failing rollupInterceptorIT  test
* reverted old error messages
* reverted checking for matching jobs on whole set instead of job by job; Added picking rollup job deterministic
* fixed sorting
* added ITs for multi rollup index search
* added ITs for multi rollup index search#2
* detekt fixes
* changed index names and rollup job
* detekt fix
* empty commit to trigger test pipeline

Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
* defekt fixes
* tests
* small refactor/improvements
* added wildcard check when creating rollup job; removed resolving targetIndex on Rollup init; added test for wildcards
* lint fixes
* moved target_index validation in getRollup resp handler
* added using toMap()
* exception fix
* linter fix
* fixed IT fail
* added Exception catch block

Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
@codecov-commenter
Copy link

codecov-commenter commented Aug 10, 2022

Codecov Report

Merging #445 (efead8e) into main (63984b2) will decrease coverage by 0.02%.
The diff coverage is 64.04%.

@@             Coverage Diff              @@
##               main     #445      +/-   ##
============================================
- Coverage     75.84%   75.82%   -0.03%     
- Complexity     2482     2514      +32     
============================================
  Files           316      316              
  Lines         14551    14633      +82     
  Branches       2250     2276      +26     
============================================
+ Hits          11036    11095      +59     
- Misses         2251     2271      +20     
- Partials       1264     1267       +3     
Impacted Files Coverage Δ
.../rollup/util/RollupFieldValueExpressionResolver.kt 65.38% <50.00%> (-24.62%) ⬇️
...arch/indexmanagement/rollup/RollupMapperService.kt 59.68% <66.17%> (+3.33%) ⬆️
...pensearch/indexmanagement/IndexManagementPlugin.kt 90.00% <100.00%> (ø)
.../indexmanagement/rollup/settings/RollupSettings.kt 95.74% <100.00%> (ø)
...nsearch/indexmanagement/rollup/util/RollupUtils.kt 80.91% <100.00%> (+0.07%) ⬆️
...statemanagement/model/destination/CustomWebhook.kt 67.14% <0.00%> (-28.58%) ⬇️
...ent/indexstatemanagement/util/ManagedIndexUtils.kt 76.10% <0.00%> (-1.77%) ⬇️
...nsform/action/stop/TransportStopTransformAction.kt 77.77% <0.00%> (ø)
.../opensearch/indexmanagement/rollup/model/Rollup.kt 86.51% <0.00%> (+0.46%) ⬆️
...nt/indexstatemanagement/ManagedIndexCoordinator.kt 69.88% <0.00%> (+0.58%) ⬆️
... and 9 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@praveensameneni praveensameneni added the v2.4.0 'Issues and PRs related to version v2.4.0' label Oct 3, 2022
Petar Dzepina added 2 commits October 25, 2022 20:38
Signed-off-by: Petar Dzepina <petar.dzepina@vroom.com>
Signed-off-by: Petar Dzepina <petar.dzepina@vroom.com>
Petar Dzepina added 4 commits October 26, 2022 18:40
Signed-off-by: Petar Dzepina <petar.dzepina@vroom.com>
Signed-off-by: Petar Dzepina <petar.dzepina@vroom.com>
Signed-off-by: Petar Dzepina <petar.dzepina@vroom.com>
Signed-off-by: Petar Dzepina <petar.dzepina@vroom.com>
Angie-Zhang
Angie-Zhang previously approved these changes Oct 31, 2022
Comment on lines +62 to +63
rollup: Rollup,
targetIndexResolvedName: String,
Copy link
Contributor

@khushbr khushbr Oct 31, 2022

Choose a reason for hiding this comment

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

A couple of documentation chages:

  1. Let us add KDoc for description of parameters and return values. Explain the various terminology and any assumptions we are making with their operation.
  2. rename rollup to rollupJob
  3. rename targetIndexResolvedName

Copy link
Contributor Author

@petardz petardz Nov 2, 2022

Choose a reason for hiding this comment

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

  1. done
  2. "rollup" is used throughout all Rollup related files. We should probably rename all or none.
  3. What do you suggest? This is called "resolved name" since it can be resolved to concrete index name from mustache script or from alias

Copy link
Contributor

Choose a reason for hiding this comment

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

  1. I was thinking of calling it plainly as concreteIndex ?

if (rollup.isTargetIndexAlias()) {
if (aliasValidationResult !is RollupJobValidationResult.Valid) {
return aliasValidationResult
} else if (!isRollupIndex(targetIndexResolvedName, clusterService.state())) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you elaborate more on this if condition? From what I gather:
If Target Index is an alias and the alias is not valid and the target index isn't a Rollup Index, then => Prepare Target Index.

These conditions seem orthogonal and don't make a coherent sense of what we are trying to do here. Are we saying this function will validate and update and create a Target index? It seems too many responsibilities present within a single function.

Copy link
Contributor Author

@petardz petardz Nov 1, 2022

Choose a reason for hiding this comment

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

If Target Index is an alias and the alias IS valid and the target index isn't a Rollup Index

Only then we would "prepare target_index"

isRollupIndex would check for existence of rollup setting in index. This will be false if we're at first job run, because in case of alias, user setup index and not us.

Copy link
Contributor

Choose a reason for hiding this comment

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

Thank you for adding the context.
Can we add all these cases to validateAndAttemptToUpdateTargetIndex() documentation? We are appending new alias feature on top of the existing functionality in `validateAndAttemptToUpdateTargetIndex(), so let us update the KDoc for this function.

@@ -96,6 +163,52 @@ class RollupMapperService(
}
}

suspend fun addRollupSettingToIndex(targetIndexResolvedName: String, hasLegacyPlugin: Boolean): Boolean {
val settings = if (hasLegacyPlugin) {
Settings.builder().put(LegacyOpenDistroRollupSettings.ROLLUP_INDEX.key, true).build()
Copy link
Contributor

Choose a reason for hiding this comment

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

Does the builder have the retries built it ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You mean on updateSettings call on client? If yes, then exception would be thrown and job would fail. We don't have any retry in place for these kind of errors.

Copy link
Contributor

Choose a reason for hiding this comment

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

This is a conversation outside this PR, but I am assuming we do not retry the updateSettings call as we expect the next cycle of ISM execution to take care of any transient errors ?

Comment on lines 186 to 194
// 2. Put rollup mappings
val putMappingRequest: PutMappingRequest =
PutMappingRequest(targetIndexResolvedName).source(IndexManagementIndices.rollupTargetMappings, XContentType.JSON)
val respMappings: AcknowledgedResponse = client.admin().indices().suspendUntil {
putMapping(putMappingRequest, it)
}
if (!respMappings.isAcknowledged) {
return RollupJobValidationResult.Invalid("Failed to put initial rollup mappings for target index [$targetIndexResolvedName]")
}
Copy link
Contributor

Choose a reason for hiding this comment

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

This code has been repeated multiple times in repo (refer this), can we instead re-use the checkAndUpdateIndexMapping() helper function in IndexUtils.kt

Copy link
Contributor Author

Choose a reason for hiding this comment

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

checkAndUpdateIndexMapping() wouldn't work because of shouldUpdate call

Copy link
Contributor

Choose a reason for hiding this comment

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

shouldUpdateIndex() will fail because at this point there are no Index mapping. Would it make sense to add a mappingCheck as param, default value as true to checkAndUpdateIndexMapping() and then re-use it ?

Signed-off-by: Petar Dzepina <petar.dzepina@vroom.com>
@khushbr khushbr merged commit 70cf4ea into opensearch-project:main Nov 3, 2022
opensearch-trigger-bot bot pushed a commit that referenced this pull request Nov 3, 2022
* added support for mustache scripting of rollup.target_index field (#435)
* tests
* small refactor/improvements
* added wildcard check when creating rollup job; removed resolving targetIndex on Rollup init; added test for wildcards
* lint fixes
* moved target_index validation in getRollup resp handler
* removed catch block
* fixed IT fail
* added Exception catch block

Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
(cherry picked from commit 70cf4ea)
opensearch-trigger-bot bot pushed a commit that referenced this pull request Nov 3, 2022
* added support for mustache scripting of rollup.target_index field (#435)
* tests
* small refactor/improvements
* added wildcard check when creating rollup job; removed resolving targetIndex on Rollup init; added test for wildcards
* lint fixes
* moved target_index validation in getRollup resp handler
* removed catch block
* fixed IT fail
* added Exception catch block

Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
(cherry picked from commit 70cf4ea)
khushbr pushed a commit that referenced this pull request Nov 3, 2022
* added support for mustache scripting of rollup.target_index field (#435)
* tests
* small refactor/improvements
* added wildcard check when creating rollup job; removed resolving targetIndex on Rollup init; added test for wildcards
* lint fixes
* moved target_index validation in getRollup resp handler
* removed catch block
* fixed IT fail
* added Exception catch block

Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
(cherry picked from commit 70cf4ea)

Co-authored-by: Petar Dzepina <petar.dzepina@gmail.com>
khushbr pushed a commit that referenced this pull request Nov 3, 2022
* added support for mustache scripting of rollup.target_index field (#435)
* tests
* small refactor/improvements
* added wildcard check when creating rollup job; removed resolving targetIndex on Rollup init; added test for wildcards
* lint fixes
* moved target_index validation in getRollup resp handler
* removed catch block
* fixed IT fail
* added Exception catch block

Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
(cherry picked from commit 70cf4ea)

Co-authored-by: Petar Dzepina <petar.dzepina@gmail.com>
if (rollupJobs != null &&
(rollupJobs.size > 1 || rollupJobs[0].id != rollup.id)
) {
errorMessage = "More than one rollup job present on the backing index, cannot add alias for target index: [$targetIndexResolvedName]"
Copy link
Member

Choose a reason for hiding this comment

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

Do we really add alias to target index at any point?
Or we should say More than one rollup job present on the backing index of the target alias, cannot perform rollup to this target alias.

wuychn pushed a commit to ochprince/index-management that referenced this pull request Mar 16, 2023
…ch-project#586)

* added support for mustache scripting of rollup.target_index field (opensearch-project#435)
* tests
* small refactor/improvements
* added wildcard check when creating rollup job; removed resolving targetIndex on Rollup init; added test for wildcards
* lint fixes
* moved target_index validation in getRollup resp handler
* removed catch block
* fixed IT fail
* added Exception catch block

Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
(cherry picked from commit 70cf4ea)

Co-authored-by: Petar Dzepina <petar.dzepina@gmail.com>
ronnaksaxena pushed a commit to ronnaksaxena/index-management that referenced this pull request Jul 19, 2023
…ch-project#586)

* added support for mustache scripting of rollup.target_index field (opensearch-project#435)
* tests
* small refactor/improvements
* added wildcard check when creating rollup job; removed resolving targetIndex on Rollup init; added test for wildcards
* lint fixes
* moved target_index validation in getRollup resp handler
* removed catch block
* fixed IT fail
* added Exception catch block

Signed-off-by: Petar Dzepina <petar.dzepina@gmail.com>
(cherry picked from commit 70cf4ea)

Co-authored-by: Petar Dzepina <petar.dzepina@gmail.com>
Signed-off-by: Ronnak Saxena <ronsax@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 2.x backport 2.4 v2.4.0 'Issues and PRs related to version v2.4.0'
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants