# Enriching Docs with Cached Elasticsearch Data

**URL:** <https://discuss.elastic.co/t/enriching-docs-with-cached-elasticsearch-data/224325>\
**Category:** Logstash\
**Created:** [March 19, 2020, 11:06pm UTC](https://discuss.elastic.co/t/enriching-docs-with-cached-elasticsearch-data/224325 "2020-03-19T23:06:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![scottdfedorov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scottdfedorov/32/64699_2.png) [@scottdfedorov](https://discuss.elastic.co/u/scottdfedorov)\
**Post date:** [March 19, 2020, 11:06pm UTC](https://discuss.elastic.co/t/enriching-docs-with-cached-elasticsearch-data/224325/1 "2020-03-19T23:06:35Z")

</div>

Howdy,

I am curious if anyone has used the `jdbc_static` (or streaming) filter plugin to query and cache Elasticsearch data?

I am aware of the `elasticsearch` filter plugin, but that plugin does not cache data. We store some (mostly) static data in Elastic for lookups, but don't want to have to query for each and every document. The `jdbc_static` plugin caches the results, but requires a jdbc connection string.

I know Elastic supports SQL queries at the REST endpoint, but the jdbc jars require a Platinum license?  
Seems real strange that you need a platinum license to utilize a feature built-in on the basic license if you just hit a different endpoint...

We are trying to stay away from Translate and file-based dictionaries. Any other ideas?

---

<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 16, 2020, 11:06pm UTC](https://discuss.elastic.co/t/enriching-docs-with-cached-elasticsearch-data/224325/2 "2020-04-16T23:06:36Z")

</div>

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