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.
Feb 21, 2023 (7 months ago)
alex
04:09 AMcurrently using : https://github.com/typesense/typesense-instantsearch-adapter#with-react-instantsearch
Jason
04:10 AMJason
04:11 AMclearCache
method: https://github.com/typesense/typesense-instantsearch-adapter/blob/69b000bbe55a9dfa04e3d546480e9955b73e9cf9/src/TypesenseInstantsearchAdapter.js#L72Jason
04:12 AMJason
04:13 AMalex
04:40 AMTypesense
Indexed 2764 threads (79% resolved)
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.
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.


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.

