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

Search API: Scroll #77

Closed
kimchy opened this issue Mar 20, 2010 · 1 comment
Closed

Search API: Scroll #77

kimchy opened this issue Mar 20, 2010 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Mar 20, 2010

When executing a search, a scroll parameter can be passed with a timeout value. When passed, a scrollId will be returned as part of the response. The scrollId can then be used to continue to scroll the results of the query. Each scroll request accepts (the same) scroll parameter with a timeout value to allow to continue scrolling.

For example:

curl -XGET localhost:9200/_search?q=content:something&scroll=5m

Will execute a search with a scroll timeout of 5 minutes. The result _scrollId can be used to execute a scroll request:

curl -XGET localhost:9200/_search/scroll?scroll=5m&scrollId=cXV...

The scroll operation is a point in time "snapshot" search. Any changes applied to the index, even after a refresh, will not be taken into account when scrolling.

Note, scrolling takes resources from each node they run on, since a state needs to be stored to continue scrolling.

@kimchy
Copy link
Member Author

kimchy commented Mar 20, 2010

Search API: Scroll, closed by 1e45578.

dadoonet pushed a commit that referenced this issue Jun 5, 2015
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
Closes elastic#77.

(cherry picked from commit c58516f)
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
Related to elastic#77.

(cherry picked from commit 7e65cfb)
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
Related to elastic#77

(cherry picked from commit ad1742a)
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
With this commit we expose two additional meta-data fields (`dashboard`
and `window_length`) for the `index-and-query-logs-fixed-daily-volume`
challenge. Meta-data are also propagated to Rally's results index and
can be thus used for creating more useful charts.
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
…3.16 (pull request elastic#77)

* Use AWS Secrets Manager to manage EMS shared secrets

Updated terraform scripts:

* Generate stream and auth token secrets
* New IAM role to grant EMS instance access to these secrets
* Split dequeue IAM role to "merger" and "recorder" for better permission granularity
* Add secret IDs to engageli, merger and EMS instance

Update engageli, dequeue and ems rc.local to use the new tags when configuring the
service. Modified tag access to save time: read all tags at once and store them
in an "env" file.

https://engageli.atlassian.net/browse/MPC-1476

Approved-by: Rich Nessel
Approved-by: Alan Nuchnoi
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
With this commit we remove the parameter "default-combination" and
replace it with a "charts" array. Previously, "default-combination"
indicated that we want to generate all charts whereas if it was not
present, we only created indexing charts. With the "charts" array it is
now clear which charts will be generated by Rally.

We also rename the "combinations" array to "configurations" because this
name is more appropriate.

Relates elastic#77
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant