Clearing a cache created in terms lookup by key
See original GitHub issueNEST version: 1.7.2 ES version: 1.7.2
In using terms lookup, I’m having it create a named cache for the terms. Periodically, when I detect that the source of those terms has changed, I want to invalidate that cache. I’ve discovered the endpoint and syntax for a raw request, for example: POST posts,comments/_cache/clear?filter_keys=members_123 if the members list in the 123 document changes.
I cannot see how I can generate that request using NEST. What I see in
public IIndicesResponse ClearCache(List<string> indices, ClearCacheOptions options)
is close, but it doesn’t support filter_keys
nor a way to pass those keys in. Is there a way to accomplish this that I’m missing?
Thanks, Tom Doman
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Clear cache API | Elasticsearch Guide [8.9]
By default, the clear cache API clears all caches. You can clear only specific caches by setting the following query parameters to true...
Read more >Clear cache API | Elasticsearch Guide [8.9]
Evicts users from the user cache. You can completely clear the cache or evict specific users. Requestedit. POST /_security/realm/ ...
Read more >Cache: delete() method - Web APIs | MDN
The delete() method of the Cache interface finds the Cache entry whose key is the request, and if found, deletes the Cache entry...
Read more >Clear Index or Data Stream Cache
The clear cache API operation clears the caches of one or more indexes. For data streams, the API clears the caches of the...
Read more >Do I need to explicitly clear the index cache after ...
I have a program that indexes multiple documents into OpenSearch every second. I make these documents available to query on a dashboard with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@russcam awesome! Thanks, I tried that out this morning and it works great! I really appreciate the support, it was very timely as we’re about to push and I really needed to be able to cache larger lists that may exist in our system. Thanks again!
This is now in release 1.9.1. Thanks again for raising, @tdoman 👍