# LRU cache in the Jdbc streaming filter plugin

**URL:** <https://discuss.elastic.co/t/lru-cache-in-the-jdbc-streaming-filter-plugin/328538>\
**Category:** Logstash\
**Tags:** jdbc\
**Created:** [March 26, 2023, 7:05am UTC](https://discuss.elastic.co/t/lru-cache-in-the-jdbc-streaming-filter-plugin/328538 "2023-03-26T07:05:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![m3bgwad](https://avatars.discourse-cdn.com/v4/letter/m/a183cd/32.png) [@m3bgwad](https://discuss.elastic.co/u/m3bgwad)\
**Post date:** [March 26, 2023, 7:05am UTC](https://discuss.elastic.co/t/lru-cache-in-the-jdbc-streaming-filter-plugin/328538/1 "2023-03-26T07:05:08Z")

</div>

Hi All,

when I parse the value to Jdbc streaming filter plugin to run the query for extract the results in the target, this values existing in the other input plugin, but the amount of values more than the time of query running so I know that there is Jdbc streaming uses LRU cache but my question Is this cache supported in the long term or once the cache is full the values are stored will remove, if this is correct, how I can overcome this?

---

<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:** [April 23, 2023, 7:05am UTC](https://discuss.elastic.co/t/lru-cache-in-the-jdbc-streaming-filter-plugin/328538/2 "2023-04-23T07:05:11Z")

</div>

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