Skip to content

Add missing ignore_unavailable query param for open PIT request #1557

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Mar 22, 2022
Merged

Add missing ignore_unavailable query param for open PIT request #1557

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 19 additions & 2 deletions output/schema/schema.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 0 additions & 1 deletion output/schema/validation-errors.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions output/typescript/types.ts
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

8 changes: 8 additions & 0 deletions specification/_global/open_point_in_time/OpenPointInTimeRequest.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,16 +22,24 @@ import { Indices } from '@_types/common'
import { Time } from '@_types/Time'

/**
* A search request by default executes against the most recent visible data of the target indices,
* which is called point in time. Elasticsearch pit (point in time) is a lightweight view into the
* state of the data as it existed when initiated. In some cases, it’s preferred to perform multiple
* search requests using the same point in time. For example, if refreshes happen between
* `search_after` requests, then the results of those requests might not be consistent as changes happening
* between searches are only visible to the more recent point in time.
* @rest_spec_name open_point_in_time
* @since 7.10.0
* @stability stable
* @doc_id point-in-time-api
* @index_privileges read
*/
export interface Request extends RequestBase {
path_parts: {
index: Indices
}
query_parameters: {
keep_alive: Time
ignore_unavailable?: boolean
}
}