Resolving Regression Issue in Typesense
TLDR John reported a regression issue related to Typesense versions. Kishore Nallan identified a change in the API that was causing this, and provided a solution, which solved the issue for John.
1
Nov 24, 2022 (13 months ago)
John
12:51 PMtypesense/typesense:0.24.0.rc19
but not on typesense/typesense:0.24.0.rcn34
for me. Or is rcn34 not a successor to rc19?Kishore Nallan
12:54 PM0.24.0.rcn34
(yes its the successor) and I even have a test case for this now. I will check shortly.Kishore Nallan
01:13 PMcurl "" -X PUT \
-H "Content-Type: application/json" \
-H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" -d '{
"synonyms": ["+", "plus"],
"symbols_to_index": ["+"]
}'
John
01:14 PM1
Typesense
Indexed 3015 threads (79% resolved)
Similar Threads
Phrase Match Problem in Typesense Version 0.24.0rcn25
Robert was unsure about correct phrase match usage in Typesense. After providing Kishore Nallan with necessary data, Kishore Nallan was able to replicate the issue. Robert shared a Github link for further tracking, where Kishore Nallan responded later.
Troubleshooting Prefix Search and Exact Match Results in Typesense v0.22.0.rcs24
JinW has trouble with typesense search, notably with prefix search and exact matches. Jason clarified some things while Kishore Nallan requested more examples and suggested using a different software version. Harisaran also recommended a solution.
Announcement: General Availability of Typesense v0.25.0
Jason announces release of Typesense v0.25.0, listing new features. Users express excitement and ask pertinent questions. Gorkem, Manuel, and Daniel commend the team for the new functionalities. Manish and Tugay share their positive experiences with Typesense. Jason and Kishore Nallan answer questions and thank users for their feedback.