Auto Detection Issue with Wildcard Field for Single Array Value
TLDR Aljosa consulted Jason and Kishore Nallan about an issue with auto-detection related to wildcard fields. It was clarified that a string can be coerced into a single-element array. Kishore Nallan confirmed it's a known issue and soon to be addressed on GitHub.
Oct 01, 2021 (28 months ago)
I have documents for which 99% of a particular wildcard field will be a string array, but sometimes there is only a single value in the array. It seems like it's not perhaps not possible to have an array field with a single value right now, is that right ?
I am actually sending it inside a single value array, so normally you're saying that single value arrays would still be automatically detected as arrays and not be auto detected as just string?
I'll fix and if it still doesn't work, I'll open a bug 🙂
Really love your product ❤️
Does it make sense that it should be possible to coerce a string into a single element array ?
The opposite not being possible makes sense, coercing an array into a string is nonsensical
Yup! This is what I thought you meant originally. We don't do this currently, and I think it makes sense to attempt this coercion
Oct 02, 2021 (28 months ago)
Kishore Nallan01:07 AM
Indexed 3015 threads (79% resolved)
Troubleshooting Invalid Field Error in Firestore Document Indexing
Darren receives an error when indexing Firestore documents with empty array in "_grades" field. Jason suggests submitting a bug report and manually setting the schema. The user still experiences issues. Kishore Nallan reproduces the bug, but suggests a solution might exist with an explicit 'string' type definition. Further investigation is needed.
Cold Start Problem with Dynamic Collections
Adrian reported cold start issues with dynamic collections. Jason suggested using wildcard `*` for query_by parameters, upgrading to `0.25.0.rc34`, and clarified conventions. Adrian's issues were resolved but they reported a limitation that will potentially be addressed.
Discussions on Typesense, Collections, and Dynamic Fields
Tugay shares plans to use Typesense for their SaaS platform and asks about collection sizes and sharding. Jason clarifies Typesense's capabilities and shares a beta feature. They discuss using unique collections per customer and new improvements. Kishore Nallan and Gabe comment on threading and data protection respectively.
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.
Resolving Typesense Result Issue in Document Collection Queries
Mike was encountering errors when searching for specific query in their Typesense document collection. Jason suggested it may be due to the `drop_tokens_threshold` setting. There was a misunderstanding but after further explanation from Jason, Mike understood and decided to continue the conversation via email.