maicnaatz opened a new issue, #45347:
URL: https://github.com/apache/superset/issues/45347
CSV_EXPORT settings are not applied consistently across CSV export
implementations.
With the following configuration in superset_config.py:
CSV_EXPORT_ = {"encoding": "utf-8-sig", "sep": ";",}
Only ZIP-based CSV exports correctly generate:
UTF-8 with BOM
Semicolon-delimited CSV
However, direct/streaming CSV chart downloads ignore these settings and
generate:
UTF-8 without BOM
Comma-separated CSV
This leads to inconsistent export behavior and causes interoperability
issues with Microsoft Excel.
Expected Behavior
All CSV export methods should respect the configured values
Actual Behavior
ZIP Export
Produces:
UTF-8 BOM
Semicolon delimiter
Excel opens the file correctly via double-click.
Direct CSV Download (Streaming Export)
Produces:
UTF-8 (without BOM)
Comma delimiter
Excel does not correctly interpret the file when opened via double-click:
Umlauts appear corrupted (e.g. Müller)
Columns may not be split correctly depending on regional settings
Test A: ZIP Export
Export data using a ZIP-based export path.
Result:
delimiter = ;
file encoding = UTF-8-BOM
Excel opens correctly via double-click
umlauts displayed correctly
Test B: Direct CSV Download
Export the same data using the direct CSV download functionality (streaming
export).
Result:
delimiter = ,
file encoding = UTF-8 (without BOM)
Excel opens incorrectly via double-click
umlauts appear corrupted (e.g. Müller)
Environment
OS: Ubuntu 24.04
Python: 3.12
Metadata DB: MySQL
Browser: Edge / Chrome
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
