-
Notifications
You must be signed in to change notification settings - Fork 500
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
Backend - Point in Time Search #674
Labels
2 - In progress
Issue/PR: The issue or PR is in progress.
v2.4.0
'Issues and PRs related to version v2.4.0'
Comments
hdhalter
added
1 - Backlog
Issue: The issue is unassigned or assigned but not started
v2.2.0
2 - In progress
Issue/PR: The issue or PR is in progress.
and removed
enhancement
New feature or request
untriaged
1 - Backlog
Issue: The issue is unassigned or assigned but not started
labels
Jun 15, 2022
47 tasks
5 tasks
3 tasks
This issue is to track the backend changes for Point in Time |
Waiting for a testing environment from the developer. |
Naarcha-AWS
changed the title
New feature - Point in Time Search
Backend - Point in Time Search
Aug 31, 2022
As discussed offline, github issue and postman collection will be used for the documentation. |
Naarcha-AWS
added
v2.4.0
'Issues and PRs related to version v2.4.0'
and removed
v2.3.0
labels
Sep 8, 2022
@kolchfa-aws Please close this issue after closing the PR |
@dhruv16dhr It should be closed automatically when the PR is merged, but I'll make sure. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
2 - In progress
Issue/PR: The issue or PR is in progress.
v2.4.0
'Issues and PRs related to version v2.4.0'
What do you want to do?
Request a change to existing documentation
Add new documentation
Report a technical problem with the documentation
Other
Give a brief description of your request.
This is a new feature: Point in Time allows users to run different queries against the same fixed data set in time. Point in time only takes data into account up until the moment it is created. Hence, none of the resources that are required to return the data from the initial request are modified or deleted. Segments are retained, even though the segment might already have been merged away and is not needed for the live data set. In short, Point in Time Search allows user to maintain a state which can be re-used by different queries in order to achieve consistent results.
Which versions are affected?
2.2 or later
Which pages or URLs are affected?
Dashboards
What resources are available (for example, links to a related issue, PR, design doc, or feature brief)?
opensearch-project/OpenSearch#1147
opensearch-project/OpenSearch-Dashboards#1612
Who should we contact with technical questions?
ramaran
Is there anything else you’d like us to know about your requested change?
The text was updated successfully, but these errors were encountered: