-
Notifications
You must be signed in to change notification settings - Fork 80
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
Fix for point in time #207
Fix for point in time #207
Conversation
"search", | ||
"paginated-search", |
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.
Where it the code for this ?
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.
The code for paginated-search functionality is already present in the code base, though the paginated-search was not enabled for CompositeContext
.
Hi @achitojha, @engechas , please take a look at this PR. |
|
||
|
||
class ClosePointInTime(Runner): | ||
class DeletePointInTime(Runner): |
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.
I remember us discussing to have deleteAllPointInTime outside composite context - lets see if we can add that as well to code repository.
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.
Have we tested this with a test workload? I'd recommend having a quick test workload to verify that this is working before we close it
register_runner(workload.OperationType.OpenPointInTime, OpenPointInTime(), async_runner=True) | ||
register_runner(workload.OperationType.ClosePointInTime, ClosePointInTime(), async_runner=True) |
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.
Can we confirm none of the workloads here do not use these operations
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.
Yes, I have checked and verified that these operations are not called in the workloads repo as of now
opensearch.list_all_point_in_time.return_value = as_future({ | ||
"pits": [ | ||
{ | ||
"pitId": pit_id, |
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.
this i think will be changed to "pit_id" as that is followed everywhere. Lets wait for rest PRs to go in.
@@ -4403,9 +4403,9 @@ async def test_creates_point_in_time(self, opensearch): | |||
"index": "test-index" | |||
} | |||
|
|||
opensearch.open_point_in_time.return_value = as_future({"id": pit_id}) | |||
opensearch.create_point_in_time.return_value = as_future({"id": pit_id}) |
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.
same here , this might become "pit_id" - lets wait for rest prs to merge.
eb5fde6
to
850ba65
Compare
Signed-off-by: Arpit Bandejiya <[email protected]>
Signed-off-by: Arpit Bandejiya <[email protected]>
Signed-off-by: Arpit Bandejiya <[email protected]>
Signed-off-by: Arpit Bandejiya <[email protected]>
Signed-off-by: Arpit Bandejiya <[email protected]>
Signed-off-by: Arpit Bandejiya <[email protected]>
08a58ad
to
ab08098
Compare
Signed-off-by: Arpit Bandejiya <[email protected]>
Signed-off-by: Arpit Bandejiya <[email protected]>
Just to follow up on Achit's comment, has this been tested on a test workload? Given that the integration tests are failing (but due to a separate cause), it'd be worth testing this on a test workload and supply the results. |
|
Thanks @IanHoang for the feedback, have uploaded the test results. Also the |
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.
Just to reiterate, OSB results report does not include create-point-in-time
, delete-point-in-time
, and list-all-point-in-time
because they are not present in any current public OSB workloads.
Signed-off-by: Arpit Bandejiya <[email protected]>
Signed-off-by: Arpit Bandejiya <[email protected]>
Description
fixes the point in time functionality
[Describe what this change achieves]
Fix Issue
#4187
Testing
[Describe how this change was tested]
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.