Implementing Directory-Specific Search with Typesense
TLDR M inquired about doing directory-specific searches using Typesense. Dima suggested storing all path combinations and using it in array filter. Kishore Nallan provided additional Typesense configuration advice to index special characters. M found these solutions helpful.
Aug 12, 2023 (1 month ago)
M
11:06 AMDima
04:04 PM/
, /path
, /path/to
) in a field and then use it in array filter_by: https://typesense.org/docs/0.24.1/api/search.html#filter-parametersDima
04:05 PMDima
04:06 PM/
, however it shows the proof of conceptAug 13, 2023 (1 month ago)
Kishore Nallan
08:11 AMsymbols_to_index
configuration during collection creation.curl -k "" -X POST -H "Content-Type: application/json" \
-H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" -d '{
"name": "docs",
"fields": [
{"name": "title", "type": "string" },
{"name": "points", "type": "int32" }
], "symbols_to_index": ["/"]
}'
Aug 19, 2023 (1 month ago)
M
10:06 AMTypesense
Indexed 2764 threads (79% resolved)
Similar Threads
Switching from Elastic to Typesense on k8s Cluster
Nicolo needed to know capabilities and features of Typesense. Jason and William provided explanations and shared experiences using it along with documentation links. Nicolo appreciated the insights.


Revisiting Typesense for Efficient DB Indexing and Querying
kopach experienced slow indexing and crashes with Typesense. The community suggested to use batch import and check the server's resources. Improvements were made but additional support was needed for special characters and multi-search queries.

Issue with Typesense Search and Special Characters
gab faced an issue with Typesense when searching with special characters. Jason and Kishore Nallan provided support and identified the issue as a bug. The problem was resolved after upgrading to `0.25.0.rc44`.


