# Elasticsearch Node Cache

**URL:** <https://discuss.elastic.co/t/elasticsearch-node-cache/120202>\
**Category:** Elasticsearch\
**Created:** [February 16, 2018, 2:51pm UTC](https://discuss.elastic.co/t/elasticsearch-node-cache/120202 "2018-02-16T14:51:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![varundbest](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/varundbest/32/48066_2.png) [@varundbest](https://discuss.elastic.co/u/varundbest)\
**Post date:** [February 16, 2018, 2:51pm UTC](https://discuss.elastic.co/t/elasticsearch-node-cache/120202/1 "2018-02-16T14:51:29Z")

</div>

So I have developed ES + Kibana plugins for Access Control,etc. We have read-only access, index, document, field level security, etc.  
Instead of turning off Elasticsearch Node Cache, I want to extend/wrap it via a plugin so i can prevent returning of restricted document via cache. Mainly what I want to do is restrict matching with cached results based on user roles. Eg: if query AND roles match, then only return via cache.

**Could someone please enlighten me on the implementation of Node Cache and whether I can alter it's behavior via a plugin?**

Regards,  
Varun

---

<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:** [March 16, 2018, 2:51pm UTC](https://discuss.elastic.co/t/elasticsearch-node-cache/120202/2 "2018-03-16T14:51:30Z")

</div>

Closed on March 16, 2018, 2:51pm UTC

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