Resolving Issue with Empty Arrays in the Filter
TLDR Rushil faced an issue with a filter not dismissing empty arrays. Kishore Nallan assisted them. The resolution was to input [] not [""] for an empty array.
Jul 17, 2023 (4 months ago)
Rushil
05:26 AMKishore Nallan
06:55 AMRushil
06:56 AMRushil
06:57 AMKishore Nallan
06:57 AMRushil
06:58 AMKishore Nallan
06:58 AMRushil
06:59 AMRushil
07:00 AMRushil
07:00 AM'fields': [
{'name': 'id', 'type': 'string','facet':false },
{'name': 'company_name', 'type': 'string',"optional": true,'facet':false },
{'name': 'url_slug', 'type': 'string',"optional": true,'facet':false },
{'name': 'number_of_investments', 'type': 'string',"optional": true,'facet':false },
{'name': 'number_of_exits', 'type': 'string',"optional": true,'facet':false },
{'name': 'location', 'type': 'string',"optional": true,'facet':false },
{'name': 'investor_type', 'type': 'string[]',"optional": true,'facet':true },
{'name': 'description', 'type': 'string',"optional": true,'facet':false },
{'name': 'company_url', 'type': 'string',"optional": true,'facet':false },
{'name': 'domain', 'type': 'string',"optional": true,'facet':false },
{'name': 'facebook', 'type': 'string',"optional": true,'facet':false },
{'name': 'instagram', 'type': 'string',"optional": true,'facet':false },
{'name': 'linkedin', 'type': 'string',"optional": true,'facet':false },
{'name': 'twitter', 'type': 'string',"optional": true,'facet':false },
{'name': 'contact_email', 'type': 'string',"optional": true,'facet':false },
{'name': 'contact_email_verified?', 'type': 'string',"optional": true,'facet':false },
{'name': 'phone_number', 'type': 'string',"optional": true,'facet':false },
{'name': 'industries', 'type': 'string[]',"optional": true ,'facet':true },
{'name': 'country', 'type': 'string',"optional": true,'facet':true },
{'name': 'has_email', 'type': 'bool',"optional": true,'facet':true },
{'name': 'has_social', 'type': 'bool',"optional": true,'facet':true },
{'name': 'has_phone', 'type': 'bool',"optional": true,'facet':true },
{'name': 'ranking', 'type': 'int32',"optional": false,'facet':true, "sort":true },
{'name': 'city', 'type': 'string',"optional": true,'facet':true },
{'name': 'stage', 'type': 'string[]',"optional": true ,'facet':true },
],
'default_sorting_field': ''
Kishore Nallan
07:01 AMRushil
07:02 AMRushil
07:03 AMKishore Nallan
07:04 AMRushil
07:04 AMRushil
07:04 AMRushil
07:04 AMKishore Nallan
07:05 AMRushil
07:15 AMRushil
07:15 AMRushil
07:16 AMRushil
07:16 AMTypesense
Indexed 3015 threads (79% resolved)
Similar Threads
Issue with Embedding Error in Version 0.25.0.rc63
Bill reported a bug in version 0.25.0.rc63 regarding a problem with updating or emplacing a document and receiving an embedding error. This was resolved in version 0.25.0.rc65, but further discussion ensued regarding the function of 'index' in the update feature.
Trouble in Implementing Deeply Nested Search
Anirudh is struggling to implement a two-level nested search. Jason asked for some specific examples to study the issue. Anirudh provided some material, realizing that adding top fields helped but might over-index. Jason then suggested reporting this issue on GitHub.
Querying with Typesense-Js and Handling Null Values
michtio was querying using typesense-js and receiving fewer results than expected. Kishore Nallan suggested using different query parameters. Further discussion led to the handling of 'null' values and filtering syntax in the search queries. The thread ended with Jason offering migration support from Algolia to Typesense.
Issue with Document Upserting and 404 Responses
Ivy faced 404 errors during document upserting due to a nested string array field. Jason recommended parsing error messages, and a GitHub issue was created.
Large JSONL Documents Import Issue & Resolution
Suraj was having trouble loading large JSONL documents into Typesense server. After several discussions and attempts, it was discovered that the issue was due to data quality. Once the team extracted the data again, the upload process worked smoothly.