Solving Typesense Cloud Interface Issue in Python
TLDR Orion had an issue querying from Python in the Typesense Cloud interface. Kishore Nallan identified the problem within the array declaration. They then discussed improving error messages and Orion offered to make a PR.



Oct 14, 2022 (11 months ago)
Orion
10:38 AMquery_by: ['title', 'text']
I’ll get hits from both titles and text fields, but the same query from Python only gets me matches with 'text'
(or 'title'
if I switch the order).Any idea what could be causing this?
Kishore Nallan
10:39 AMOrion
10:40 AMOrion
10:44 AM> One or more
string / string[]
fields that should be queried against. Separate multiple fields with a comma: company_name, country
I think I got thrown by the
string / string[]
part and made a wrong assumption.Is it expected behaviour to treat an array as a valid input?

Kishore Nallan
10:51 AMKishore Nallan
10:52 AMOrion
10:53 AMKishore Nallan
10:54 AMOrion
10:54 AMKishore Nallan
10:54 AMOrion
10:54 AMKishore Nallan
10:54 AMOrion
10:58 AMKishore Nallan
10:59 AMKishore Nallan
10:59 AM
Orion
11:06 AMRequestMalformed
but that doesn’t seem quite right… Looking around I don’t see anywhere doing query validation. Maybe I should create a dirt simple validation step for search_parameters
?Kishore Nallan
11:16 AMInvalidParameter
error or something here: https://github.com/typesense/typesense-python/blob/master/typesense/exceptions.pyOrion
11:16 AM
Orion
11:32 AMKishore Nallan
11:45 AMOrion
11:45 AMOrion
11:46 AMOrion
11:50 AMKishore Nallan
11:51 AMKishore Nallan
11:51 AMOrion
11:53 AMOrion
12:00 PMOrion
12:10 PMI don’t think this PR interferes with any existing behaviour like that right?
Maybe a separate PR for basic casting would be nice, could improve ergonomics and match more peoples expectations?
Kishore Nallan
12:32 PMOrion
12:44 PM"pre_segmented_query": True
-> "pre_segmented_query":"true"
Orion
01:14 PMKishore Nallan
01:17 PMKishore Nallan
01:17 PMOrion
01:19 PMOrion
01:20 PMKishore Nallan
01:26 PMOrion
01:43 PMKishore Nallan
01:52 PM
Oct 15, 2022 (11 months ago)
Kishore Nallan
01:43 PM
Orion
01:58 PMKishore Nallan
02:01 PMNone
field values as null
(I think) : https://github.com/typesense/typesense-python/issues/14Orion
02:10 PMOrion
02:11 PMOrion
02:12 PMKishore Nallan
02:12 PM
Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
Sorting Results in Typesense and Handling Errors
Ramees asks about sorting results by distance in Typesense, entering a list of strings as a field, and resolving an error with `fields` format. Kishore Nallan assists with these issues and advises on storing timestamps and proper authentication.

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.



Understanding and Implementing Typesense Dart Library with Flutter
Alexandro sought help with the Typesense Dart library. Jason explained that the library is in progress, discussed utilizing other HTTP libraries, and provided detailed instructions on utilizing Typesense with Flutter. Alexandro provided feedback on the Typesense UI and expressed interest in creating a tutorial video.



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.

Issue with Typesense Schema and Ruby Client
Mateo faces issues while creating a schema and using Ruby client for Typesense. Jason suggests using a new field instead of 'id' and provides assistance for Ruby client errors.