ROW_LIMIT and SQL_MAX_ROW set to 10M but charts/tables still capped at 500k rows after full rebuild

[FrancescoCastaldi]

Despite setting all row-related configuration values to 10,000,000 in the superset_config.py file, charts and table visualizations are still being capped at approximately 500,000 rows, even after a full rebuild of the application.

ROW_LIMIT = 10000000
SQL_MAX_ROW = 10000000
TABLE_VIZ_MAX_ROW_SERVER = 10000000
DEFAULT_SQLLAB_LIMIT = 10000000

SQLLAB_ASYNC_TIME_LIMIT_SEC = 800
SQLLAB_TIMEOUT = 800
SUPERSET_WEBSERVER_TIMEOUT = 800
SQLLAB_CTAS_NO_LIMIT = True

Is there an additional limit enforced at the visualization layer (per chart type or dataset level) that overrides these global settings?
I'm using v6.0.0
thanks

[dosubot[bot]]

@FrancescoCastaldi The 500k cap you're hitting is almost certainly coming from TABLE_VIZ_MAX_ROW_SERVER, which defaults to 500000 and controls the maximum rows for server-paginated table visualizations [1]. I notice you already have it in your config — but the key detail is how the limit is enforced.

Superset's apply_max_row_limit() function uses min(configured_max, user_limit) to cap row counts [2]. When server pagination is enabled on a table chart, it reads TABLE_VIZ_MAX_ROW_SERVER; when disabled, it reads SQL_MAX_ROW. So even with your global settings at 10M, the effective limit depends on which path is taken.

A few things to check:

1. Verify your config is actually loaded. Confirm TABLE_VIZ_MAX_ROW_SERVER is picked up at runtime (e.g., via the /api/v1/ endpoints or by checking logs). Sometimes config files aren't loaded due to path issues.

2. Check individual chart-level row limits. Each chart can have its own row_limit saved in its form data, which takes precedence over global config [3]. Open the chart in Explore, check the "Row limit" setting in the Data/Options section, and update it to your desired value.

3. Frontend constant. The frontend also has a DEFAULT_MAX_ROW_TABLE_SERVER = 500000 constant [4]. If you're on a custom build, you may need to verify this was updated as well (though normally the backend config is what matters for actual query execution).

4. Version note: The latest official release in the repo is 5.0.0 — if you're on a fork or pre-release labeled as v6.0.0, the behavior should be similar, but worth double-checking.

Your config looks correct on paper. The most likely culprit is either the config not being loaded properly or individual charts still having the old row limit saved in their form data.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.