This message was deleted.
# community-help
s
This message was deleted.
j
Could you try this on 0.25.2.rc11?
s
Yes, of course I can try, and thanks for the prompt reply! However, I only see 0.25.2.rc10 & 0.25.2.rc12 on Typesense Cloud. Would any of those work instead?
j
Yeah letโ€™s try rc12
s
Nope, still getting the same inconsistency
j
Could you create a GitHub issue with a set of curl commands like this that replicates the issue: https://gist.github.com/jasonbosco/7c3432713216c378472f13e72246f46b#file-typesense-repro-steps-sh
s
Yes, just created the issue on GitHub
j
Looks like you closed the issue. Did you find a solution for it?
s
No, I accidentally published it in the Typsesense github for javascript so I re-opened it in the main Typesense Github page and closed the in the Javascript page. Sorry for the confusion :s
๐Ÿ‘ 1
k
I wasn't able to reproduce, please see my comment here: https://github.com/typesense/typesense/issues/1422#issuecomment-1848196257
s
@Kishore Nallan Thank you, just saw it. Is there a way for me to provide you private access to our Typesense Cloud server? Or a way for me to privately help you replicate the collection? The collection this query is running on has 104 entries
k
If you can give me a verbal permission we can load the data in a debug cluster to investigate. Please DM me the cluster id, collection name and the query used.
s
Yes, I give you permission to load data in debug mode to investigate this issue. I'll share with you the details through private message
k
Thanks for the access. I figured out what's going wrong. When you search for a parent field like
members
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:
Copy code
{
  "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.
๐Ÿ™Œ 1
s
Got it, thanks so much for this!! I didn't know that there was a limit of fields to search in.
๐Ÿ‘ 1