Slackbot
12/08/2023, 9:23 PMJason Bosco
12/08/2023, 9:37 PMSGM
12/08/2023, 9:44 PMJason Bosco
12/08/2023, 9:47 PMSGM
12/08/2023, 10:03 PMJason Bosco
12/08/2023, 10:09 PMSGM
12/08/2023, 10:49 PMJason Bosco
12/08/2023, 11:08 PMSGM
12/08/2023, 11:10 PMKishore Nallan
12/09/2023, 3:11 AMSGM
12/09/2023, 4:08 AMKishore Nallan
12/09/2023, 4:22 AMSGM
12/09/2023, 5:04 AMKishore Nallan
12/09/2023, 9:53 AMmembers Typesense expands that object field into the underlying child fields that are then searched on. This has an upper limit of 100 fields. So we end up searching on only the first 100 members.X fields here. However, since there are 230+ unique fields that are children of the members object in the collection some fields are not searched.
While you can have as many unique fields you want in the collection, for query_by and other search parameters, we limit searching to 100 underlying fields.
You will have to redesign your collection schema by either:
a) having the members as an array of objects like this:
{
"members": [
{
"n": "100",
"u": "user3949498",
"uid": "abc"
},
{
"n": "104",
"u": "user3749462",
"uid": "xyz"
}
]
}
This way, the members.n and members.u are just represented as an array under the hood so you won't run into this limitation. Or,
b) breaking each member into a separate document in the collection.SGM
12/09/2023, 8:17 PM