Excluding a Facet Issue in Typesense
TLDR Stefan had an issue excluding a facet in Typesense v0.21.0. Kishore Nallan clarified that the :!=
syntax replaced the old :-
syntax. The solution was upgrading to the latest version. Jason added there's no easy downgrading from v0.22.0 to v0.21.0.
Nov 02, 2021 (24 months ago)
Stefan
04:31 PMAs far as I understand the docs the code below should exclude "Cleansers" from the facet, but it returns the same results as
:=
. I am running v0.21.0. image id: 2d94fc7c161bfilter_by: category_functional:!=Cleansers
Kishore Nallan
04:35 PM/debug
end-point?Kishore Nallan
04:36 PM:-
syntax. It eventually became :!=
Stefan
04:37 PMStefan
04:53 PMI upgraded the version in my staging env: Works
Locally it doesn't start anymore when I try to go back from the latest rc to v0.21.0
Stefan
04:53 PMStefan
04:54 PME20211102 16:49:59.600389 204 store.h:157] Error while fetching the key: $KN - status is: Corruption: Unknown Footer version. Maybe this file was created with newer version of RocksDB?
E20211102 16:49:59.600395 204 collection_manager.cpp:102] Auth manager init failed, error=Error while fetching the next API key id from the store.
E20211102 16:49:59.600419 204 store.h:157] Error while fetching the key: $CI - status is: Corruption: Unknown Footer version. Maybe this file was created with newer version of RocksDB?
E20211102 16:49:59.600423 204 raft_server.cpp:519] Typesense failed to start. Could not load collections from disk: Error while fetching the next collection id from the disk.
I20211102 16:49:59.600445 204 snapshot_executor.cpp:264] node default_group:172.20.0.5:8107:8108 snapshot_load_done, last_included_index: 39647 last_included_term: 221 peers: "172.20.0.2:8107:8108"
E20211102 16:49:59.600454 204 raft_server.h:249] Met peering error {type=StateMachineError, error_code=1, error_text=`StateMachine on_snapshot_load failed'}
W20211102 16:49:59.600458 204 node.cpp:1264] node default_group:172.20.0.5:8107:8108 got error={type=StateMachineError, error_code=1, error_text=`StateMachine on_snapshot_load failed'}
E20211102 16:49:59.600469 196 snapshot_executor.cpp:393] Fail to load snapshot from local:///data/state/snapshot
E20211102 16:49:59.600478 196 node.cpp:530] node default_group:172.20.0.5:8107:8108 init_snapshot_storage failed
E20211102 16:49:59.600483 196 raft_server.cpp:118] Fail to init peering node
I20211102 16:49:59.600486 196 node.cpp:929] node default_group:172.20.0.5:8107:8108 shutdown, current_term 221 state UNINITIALIZED
I20211102 16:49:59.600533 201 raft_server.h:245] This node is down
E20211102 16:49:59.600579 196 typesense_server_utils.cpp:256] Failed to start peering state
Jason
04:59 PMTypesense
Indexed 2779 threads (79% resolved)
Similar Threads
Large JSONL Documents Import Issue & Resolution
Suraj was having trouble loading large JSONL documents into Typesense server. After several discussions and attempts, it was discovered that the issue was due to data quality. Once the team extracted the data again, the upload process worked smoothly.
Resolving Multilingual Search Function in Typesense Software
Bill is having difficulty with multilingual search functionality in Typesense software. Developer Kishore Nallan suggested setting a language locale and provided a demo build. The build solution had some issues, and after multiple rounds of software updates and troubleshooting, the problem still persists.
Troubleshooting Issues with DocSearch Hits and Scraper Configuration
Rubai encountered issues with search result priorities and ellipsis. Jason helped debug the issue and suggested using different versions of typesense-docsearch.js, updating initialization parameters, and running the scraper on a Linux-based environment. The issues related to hits structure and scraper configuration were resolved.
Fixing Corrupted Documents and Upgrading Typesense Cloud Version
gab had issues with corrupted documents in Typesense Cloud. Jason suggested upgrading to version 0.24.1.rc, which resolved the issue. They also discussed CORS domain management.
Troubleshooting 400 Error When Upgrading Typesense Firestore Extension
Orion experienced a `400` error after updating the Typesense Firestore extension, causing issues with cloud functions. They traced the issue back to a data type conflict in their Typesense collection schema after updating. With help from Jason and Kishore Nallan, they resolved the issue by recreating the collection.