Seeking Advice for Report Engine Build on Top of TS
TLDR Dan was seeking advice to build a reporting engine for their specific use case on TS but was facing difficulties. Kishore Nallan recommended using Clickhouse, which has features conducive to Dan's needs.
1
Sep 08, 2022 (13 months ago)
Dan
08:29 PMFor example, if I want to see two years+ of data, it would be >730 searches in a multi_search (not even sure that’s doable..). On top of that, each search has to be filtered by a list of facet values, potentially in the 100s of thousands of values… This is clearly not going to work, but was a fun exercise to see if it could be done 🙂
The kind of data we have looks like this:
{
"activityKind_facet": "activity.platform/reaction",
"channelId_facet": "d1541dde-47b6-444c-b2ce-52668dd8d3cd",
"channelKind_facet": "chat",
"communityId_facet": "8e914cd4-a155-40cb-84e7-f476d3429d5c",
"date_facet": 1656028800,
"personaId_facet": "62f13402-1393-4963-a0c0-89d10e1237f3",
"primaryLabel": "Added an emoji: :airplane:",
"timestamp": 1656087039
}
..and what I’d like to be able to do is group by
date_facet
, and have counts of other facets by that group, filtered by (potentially) a large number of personaId_facet
, as I mentioned above.I can see how we can manually build rollup tables of all this data, but it feels annoying that we have to define what we can get out ahead of time - any advice on tech that can tackle this kind of problem without too much hassle, from flat documents, with consistent performance?
Sep 09, 2022 (13 months ago)
Kishore Nallan
03:18 AM1
Typesense
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.
Improving System Performance and Typesense Query Efficiency
SamHendley was experiencing performance issues with Typesense's large-scale system testing and proposed several improvements. Both Jason and Kishore Nallan addressed the suggestions and corrected some misconceptions. They provided further clarification and recommended upgrades for better performance.
Merging Results of Multi-Search Queries: Workarounds and Future Features
Julian wanted to merge results from two similar collections. Kishore Nallan confirmed it's a feature that might be implemented but hasn't been prioritised. Both Julian and robert plan to use client-side solutions for now.