Hi pinot community,
Does pinot is a good case for exporting detailed data report use case?
The report would have some level of aggreation but the granularity of dimensions is still high?
Does this kind of use case still fit with pinot?
Thanks
k
Kishore G
06/03/2022, 7:14 AM
if thats the primary use case, then Pinot is probably not the right solution. But if you have other use cases and exporting detailed report is infrequent, it should be ok
➕ 1
f
Fritz
06/03/2022, 7:20 AM
Thanks @Kishore G for responding.
The frequency maybe upto 5% of the total request that would do the export use case.
But, it potentially would exporting quite range of data period (upto 1 year) for each client data
Fritz
06/03/2022, 7:20 AM
Does this kind of workload still good fit?
k
Kishore G
06/03/2022, 7:29 AM
how many rows do you think it will need to export?
f
Fritz
06/03/2022, 7:38 AM
Couple hundreds thousands records
m
Mayank
06/03/2022, 1:04 PM
If the other 95% is analyrical workload and for few hundreds of thousands of records you can definitely use Pinot
Mayank
06/03/2022, 1:05 PM
Even if the number of records in report grow you ca still use Pinot, but you might then want to split the query over different time ranges
f
Fritz
06/03/2022, 2:02 PM
Thanks @Mayank. That is great news for me.
What do you mean by split the query by different time range?
m
Mayank
06/03/2022, 2:05 PM
For example instead of getting millions of rows across a big time range in a single query, break the query into multiple queries in smaller time ranges and concat the results on client. It is pattern I have seen in production for reporting cases. But may or may not apply to you
f
Fritz
06/03/2022, 2:08 PM
I see. Thanks for explanation.
But, would it be help if implementing pagination when query the data?
How the "reporting workload" would be affecting the "analytics workload"? Does it necessary to separate the broker/server?