Filtering Data Based on Routes for Job Application
TLDR KARTHICK asked how to filter jobs based on routes. Jason suggested adding a
strings attribute for saved jobs and using filters for different routes.
Apr 07, 2023 (8 months ago)
1. Population of created job
2. Population of saved job
How to filter these data based on the routes.
When user saved the job that need to be removed from normal job routes and it should be populate only in saved job route.
SAVED JOB Route should contain on the saved jobes by specific users. I need some help from anyone to solve this useCase using ts. Kishore Nallan Jason
stringsattribute in the document called say
Then to render the saved jobs for a user, you filter by that user’s ID. And to render the normal jobs route, you would apply a filter of
exclude_fieldsand exclude this field from being returned in the API response, to make sure users can’t see each other’s saved jobs
Indexed 3015 threads (79% resolved)
Usage and Modification of Dynamic Routes in Typesense Documents
Ethan needed a way to perform exact queries through two fields in Typesense documents. Kishore Nallan demonstrated its possibility using the "filter_by". An issue was resolved via recommending that fields in 'query by' should be a string type.
Performance Characteristics of Filtering Search Results
Oskar queries the performance difference in filtering search results. Jason clarifies how filters work and provides performance improvement suggestions like increasing vCPUs and sharding the collection. Kishore Nallan explains filter IDs and document ID matching. The thread concludes with discussions on performance tradeoffs in filter implementation.
Resolving Document Export & Batch Deletion Issues
Dui had trouble exporting a document and wanted batch deletion assistance. Kishore Nallan fixed the export issue, upgraded their cluster manually and suggested using `delete by query`.