Validity of Schema in Documentation
TLDR Harpreet raised doubt about a certain schema in the documentation. Kishore Nallan confirmed the error, and Harpreet planned to open a pull request to correct it.
1
May 26, 2021 (32 months ago)
Harpreet
05:42 AMdefault_sorting_field which is not present in fields? Is this schema valid?{
"num_documents": 1250,
"name": "ceos",
"fields": [
{"name": "company_name", "type": "string"},
{"name": "full_name", "type": "string"},
{"name": "from_year", "type": "int32"}
],
"default_sorting_field": "num_employees"
}
Kishore Nallan
05:42 AMHarpreet
05:43 AMhttps://typesense.org/docs/0.20.0/api/collections.html#list-all-collections
Kishore Nallan
05:43 AMHarpreet
05:44 AMHarpreet
05:45 AMfrom_year should be the value of default_sorting_field ?Kishore Nallan
05:45 AMHarpreet
05:46 AMKishore Nallan
05:46 AM1
Typesense
Indexed 3015 threads (79% resolved)
Similar Threads
Issues with Schema Creation and Nested Fields
Sean encountered a problem with schema creation involving auto nested fields. Kishore Nallan suggested checking the API response for errors and adding problematic fields to the schema as optional. Sean confirmed the advice.
Troubleshooting Typesense API Sorting Error in Item Collections
Nikhil encountered a sorting error when using Typesense API due to an optional reference field in the items collection schema. Harpreet and Jason helped debug and identified a bug with sorting in general for 2 fields with the first one being the join field, promising a fix in a forthcoming build.
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.
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.