@cubejs-client/core load / drilldown load method requires supports for pagination like `page`, `per_page`, to improve performance · cube-js/cube#1434

(3 comments) (1 reaction) (0 assignees)Rust (19,563 stars) (1,965 forks)batch import

client:corehelp wanted

説明

Is your feature request related to a problem? Please describe. When using a drilldown load query, the number of records returned from db can be in the order or thousands or millions of records depending on the implementation and use-case. This can affect the performance of database server and can momentarily cause huge performance issues the database server.

Describe the solution you'd like drilldown query should ideally support page, per_page, other than limit .

Describe alternatives you've considered No alternatives found as of now

Additional context

records recieved in the order of thousands or millions can be pginated at front-end side, but the performance is affected very badly at the db side. This is a huge concern for the product team. Not able to go for deployment.
offset is not enough to build a pagination ui, it gives a very bad UX

コントリビューターガイド

技術スタック: javascripttypescriptnodejs
領域: performancebackendanalytics
Issue 種別: feature
難度: 3
推定時間: 3-5 days
活動状況: stale
明確さ: clear
前提条件: Understanding of Cube.js client load methodFamiliarity with pagination patterns
初心者向け度: 35
調査方針: Examine the existing 'load' method in '@cubejs client/core' (likely in 'packages/cubejs client core/src' directory). The issue requests adding 'page' and 'per page' parameters alongside existing 'limit'. Review any related discussions in comments; no linked PRs exist. Investigate how 'limit' is currently passed to the API and consider extending the query builder to support offset/pagination without degrading performance. Look for existing tests for the load method to understand expected behavior.