#community-help

Accessing Cached Data in Typesense InstantSearch Adapter

TLDR alex asked how to access cached data in Typesense InstantSearch adapter. Jason explained the difficulty in accessing cache entries due to the cache key being a hash of request parameters.

7mo

Join the chat

Feb 21, 2023 (7 months ago)

Photo of md5-0dc7ffd31fe74c8940f4a6976fc32045

alex

04:09 AM

Whenever we navigate to different pages, the data got from server gets cached in instant search. So when we visit the already visited page again, the data is not pulled from server but it gets loaded from the cache for that page. Is there any way we could access this cached data or hits?

currently using : https://github.com/typesense/typesense-instantsearch-adapter#with-react-instantsearch

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

04:10 AM

If you re-instantiate the instant-search-adapter on page navigation, that should clear cache

04:11

Jason

04:11 AM

Alternatively, there’s also the clearCache method: https://github.com/typesense/typesense-instantsearch-adapter/blob/69b000bbe55a9dfa04e3d546480e9955b73e9cf9/src/TypesenseInstantsearchAdapter.js#L72

04:12

Jason

04:12 AM

Oh wait, your question is how to access the cached data…

04:13

Jason

04:13 AM

The cache key is a hash of the request parameters… so you would have to know all the request parameters to access the correct cache entry, which is not an easy thing to do

alex

04:40 AM

I see, thanks for the quick reply, will check them out 😄

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Debugging Search Issue with Typesense Server Caching

Jameshwart reported experiencing caching issues with typesense server, despite the server's default setting of not caching. Through troubleshooting steps with Kishore Nallan, they were able to confirm an issue with the Typesense Javascript client and resolved it by adding `cacheSearchResultsForSeconds: 0` after `apiKey` in the initialisation. Laura also participated in discussion, learning about server and client level caching.

2mo

Discussing `use_cache` and `cacheSearchResultsForSeconds` Options

Aljosa wanted a confirmation for a technical issue and Jason suggested to use `use_cache` for both. Proposed updates were given to check if their issue resolves. Aljosa agreed to test out the proposed solution.

19mo

Issues with Typesense Frontend Search Integration

Akash experienced issues integrating Typesense into their frontend search, particularly with their search box. Jason guided them to troubleshoot, eventually identifying the issue to be with react-instantsearch-dom and suggesting a downgrade to react 17, which resolved the issue.

11mo