ALLOW_FULL_CSV_EXPORT flag doesn't work

[slemos-cmyk]

Bug description

In version 5.0.0 the ALLOW_FULL_CSV_EXPORT flag does not work, we have it configured with True but it ignores it

CSV file exports only have what is filtered in the search, only the 13 records of the query

Screenshots/recordings

No response

Superset version

5.0.0

Python version

3.10

Node version

16

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot]

Hi @slemos-cmyk! I'm Dosu and I’m helping the superset team.

The ALLOW_FULL_CSV_EXPORT flag is defined in Superset 5.0.0, but it isn't functionally implemented in the CSV export logic—setting it to True does not actually bypass row limits or change export behavior. CSV exports are still governed by row limits like ROW_LIMIT, DISPLAY_MAX_ROW, SQL_MAX_ROW, DEFAULT_SQLLAB_LIMIT, and QUERY_SEARCH_LIMIT. To export more rows, you need to increase these settings in your superset_config.py and restart the server or rebuild the frontend for changes to take effect [source].

The feature flag is listed as "In Testing" and may not be fully implemented or bug-free [source]. There is no explicit "Export full CSV/Excel" option in the UI for 5.0.0, and the backend code does not actively check this flag during export [source].

If you need to export large datasets, consider using SQL Lab or direct database queries as a workaround. Keep an eye on future releases and pull requests for improvements to CSV export functionality [source].

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[rusackas]

Let us know if the bot helped (or not) so we can take next steps accordingly.

[slemos-cmyk]

Hello, yes, the bot's response helped us. Thank you

…

On Mon, Dec 1, 2025 at 3:10 PM Evan Rusackas ***@***.***> wrote: *rusackas* left a comment (apache/superset#36291) <#36291 (comment)> Let us know if the bot helped (or not) so we can take next steps accordingly. — Reply to this email directly, view it on GitHub <#36291 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B2XELYE2UCKGHIGD3RHK6RT37R77TAVCNFSM6AAAAACNIPNTC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKOJYGEYTGNJXGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[rusackas]

Awesome, closing!