-
Notifications
You must be signed in to change notification settings - Fork 113
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
Search Rollup and Live Data Feature: Base case (No overlapping data) #898
Search Rollup and Live Data Feature: Base case (No overlapping data) #898
Conversation
src/main/kotlin/org/opensearch/indexmanagement/IndexManagementPlugin.kt
Outdated
Show resolved
Hide resolved
src/main/kotlin/org/opensearch/indexmanagement/rollup/interceptor/ResponseInterceptor.kt
Outdated
Show resolved
Hide resolved
what do you mean by "Ignore exception being thrown by not calling validate indices in live data indices" in description? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for making these changes, @ronnaksaxena
Added a few comments.
src/main/kotlin/org/opensearch/indexmanagement/rollup/interceptor/RollupInterceptor.kt
Outdated
Show resolved
Hide resolved
src/main/kotlin/org/opensearch/indexmanagement/rollup/interceptor/RollupInterceptor.kt
Outdated
Show resolved
Hide resolved
Signed-off-by: Ronnak Saxena <[email protected]>
Signed-off-by: Ronnak Saxena <[email protected]>
Signed-off-by: Ronnak Saxena <[email protected]>
deleted response interceptor init from indexManagementPlugin Signed-off-by: Ronnak Saxena <[email protected]>
deleted resonse interceptor from helper method Signed-off-by: Ronnak Saxena <[email protected]>
Will add response interceptor logic in next PR Signed-off-by: Ronnak Saxena <[email protected]>
uncommeneted rollup size check Signed-off-by: Ronnak Saxena <[email protected]>
Signed-off-by: Ronnak Saxena <[email protected]>
val concreteRolledUpIndexNames = mutableListOf<String>() | ||
for (indexName in concreteIndices) { | ||
if (isRollupIndex(indexName, clusterService.state())) { | ||
concreteRolledUpIndexNames.add(indexName) | ||
} | ||
} | ||
val filteredConcreteIndices = concreteRolledUpIndexNames.toTypedArray() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the shard is a rollup index, you do a filtering and keep only the rollup indexes in the request. What about the other path, when the shard is a live index, do you also need a filtering?
var deleteResponse = client().makeRequest( | ||
"POST", | ||
"source_rollup_search/_delete_by_query", | ||
mapOf("refresh" to "true"), | ||
StringEntity("""{"query": {"match_all": {}}}""", ContentType.APPLICATION_JSON) | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If all the data from source index gets deleted, then it seems to me you are just search the rollup index later instead of both indexes
Handles the use case of of searching rollup indices and live indices that have no overlapping data between them
Base Case: No data overlap between rollup indices and live data indices
Changes:
CheckList:
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.