Issues with Nested Coordinate Fields in Typesense
TLDR Jainil faced issues with nested coordinate fields causing errors, which were fixed in Typesense 0.24.1.rc12
and 0.25.0.rc21
versions.
3
1
1
Mar 29, 2023 (8 months ago)
Jainil
06:51 PMMy field is:
{"name": "interested_cities.coordinates", "type": "geopoint[]", "optional": True}
And the error I'm getting is:
"error": "Field `interested_cities.coordinates` must contain 2 element arrays: [ [lat, lng],... ].",
Jainil
06:52 PM "interested_cities": [
{
"geoname_id": "2332459",
"region_geoname_id": "2332453",
"country_geoname_id": "2328926",
"coordinates": [
6.45407,
3.39467
]
},
{
"geoname_id": "1814087",
"region_geoname_id": "2036115",
"country_geoname_id": "1814991",
"coordinates": [
38.91222,
121.60222
]
}
]
Jainil
06:52 PMDima
07:23 PMgeopoint[]
(array type) for only one coordinate. Maybe you want geopoint
instead?Jainil
07:24 PMgeopoint
?Dima
07:25 PMJainil
07:25 PMJainil
07:29 PMField `interested_cities.coordinates` must be a 2 element array: [lat, lng].
Jainil
07:35 PMhttps://github.com/typesense/typesense/issues/888
Jainil
11:33 PMFWIW, seems like it has something to do with the
{"name": ".*", "type": "auto"},
Jainil
11:33 PMJason
11:40 PMCC: Kishore Nallan this is on
0.24.0.rc11
^Jainil
11:41 PM0.24.0
I run into the following, for the same scripts)Field `interested_cities.coordinates` has an incorrect type.
Mar 30, 2023 (8 months ago)
Kishore Nallan
08:01 AM1
Mar 31, 2023 (8 months ago)
Kishore Nallan
09:27 AM0.24.1.rc12
-- can you please verify?1
Jainil
06:17 PMJainil
06:24 PMApr 01, 2023 (8 months ago)
Jason
03:16 AMApr 02, 2023 (8 months ago)
Jainil
07:28 PM1
Apr 04, 2023 (8 months ago)
Jainil
08:26 PMApr 05, 2023 (8 months ago)
Kishore Nallan
01:25 AM1
Jainil
11:31 PMgeopoint
as opposed to geopoint[]
See gist (running on v0.24.1)
https://gist.github.com/jsutaria/4a91640a3449d7dd84bef3ec029783e2
Jainil
11:32 PM"Field `current_city.coordinates` has an incorrect type."
Jainil
11:36 PMgeopoint[]
Apr 06, 2023 (8 months ago)
Kishore Nallan
01:56 AMApr 10, 2023 (8 months ago)
Kishore Nallan
09:14 AMtypesense/typesense:0.25.0.rc21
1
Jainil
02:22 PMTypesense
Indexed 3015 threads (79% resolved)
Similar Threads
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.
Troubleshooting Typesense Search in Nested Fields
Vadali couldn't search within nested artist.name field. Kishore Nallan helped diagnose and fix, which involved updating their cloud cluster to a later version. Jason provided advice on using the correct Docker image.
Issue with `included_fields` Command in Typesense
SamHendley encountered an issue with the `included_fields` command in Typesense versions 0.23.0 and 0.24.0.rc17. Jason helped identify it as a bug in the 0.24.X version, which was later addressed in release 0.24.0.rcn19.
Setting `facet` as `true` in DB fields through Airbyte
Jamshid had an issue setting `facet` as `true` in DB fields through Airbyte. Jason shared the equivalent API endpoint and recommended upgrading Typesense to resolve an unusual bug.
Handling Kinesis Stream Event Batching with Typesense
Dui had questions about how to handle Kinesis stream events with Typesense. Kishore Nallan suggested using upsert mode for creation/update and differentiating with logical deletion. After various discussions including identifying and resolving a bug, they finalized to introduce an `emplace` action in Typesense v0.23.