Handling nil Value in Geopoint Type in Typesense
TLDR Bhola was encountering a problem with storing a nil value in Geopoint type in Typesense. Jason suggested setting the field as optional: true in the schema and then omitting the field entirely in the document.
1
Nov 11, 2022 (13 months ago)
Bhola
03:40 AMi facing issue with the geopoint type in typesense
just i have one doubt we can not store nil value in the geopoint ?
when i am trying to store nil value like :- geo_data=>[nil, nil]
it give me error Typesense::Error::RequestMalformed: Field geo_data must be a geopoint
Jason
03:50 AMoptional: true in the schema, and then leave the field out of the document completely1
Typesense
Indexed 3011 threads (79% resolved)
Similar Threads
Handling Firestore Geocode Type with Typesense Collection
Loic asked how to manage Firestore Geocode type in Typesense, Jason suggested using the geopoint data type and provided a useful resource.
Resolving NULL Values Issue in Typesense Project
andy thanked Kishore for helping with their typesense project. They shared a problem regarding NULL values that they resolved. Kishore Nallan suggested marking the field as optional for addressing such issues.
Restricting Data Storage in Typesense to Defined Schema Fields
Ashwin asks if Typesense can save only fields in their schema. Kishore Nallan advises removing unwanted fields pre-indexing, and using include_fields param to return desired fields.