# Pulling Data in response to a Query in ELK

**URL:** <https://discuss.elastic.co/t/pulling-data-in-response-to-a-query-in-elk/192863>\
**Category:** Elasticsearch\
**Created:** [July 30, 2019, 9:48am UTC](https://discuss.elastic.co/t/pulling-data-in-response-to-a-query-in-elk/192863 "2019-07-30T09:48:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nik\_Gupta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik_gupta/32/49025_2.png) [@Nik\_Gupta](https://discuss.elastic.co/u/Nik_Gupta)\
**Post date:** [July 30, 2019, 9:48am UTC](https://discuss.elastic.co/t/pulling-data-in-response-to-a-query-in-elk/192863/1 "2019-07-30T09:48:04Z")

</div>

Is it possible to operate ELK in way that it pulls data in response to a query and 'drops' it after some period of time? For context, I have an extremely large amount of data in which I'd like to examine specific small slices of time. Feeding the whole data set in is infeasible and unnecessary; I'd just like to load in what's necessary and 'drop it' when it's no longer being used. Are there any features that support this flow natively?

Edit: I should also mention that the data being examined already lives in a persistent store and is partitioned into files based on time.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 27, 2019, 9:48am UTC](https://discuss.elastic.co/t/pulling-data-in-response-to-a-query-in-elk/192863/2 "2019-08-27T09:48:08Z")

</div>

Closed on August 27, 2019, 9:48am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.