Error 505 when exporting pivoted .csv with custom CSV_EXPORT configuration

[Jockxtar]

Bug description

I'm trying to make the "Export to pivoted .CSV" option work for a (relatively) convoluted pivot table and I found some issues. I will create a bug report for each of them.

Description

Throws "Error 505" if configuration file has CSV_EXPORT = {"encoding": "utf-8", "sep": ";", "decimal": ","}.
Since this configuration doesn't work anyways for the normal csv export, I'm okay with just removing it for now, but a fix would be neat.

Steps to reproduce:

1. Modify 'CSV_EXPORT' in 'config.py' to "CSV_EXPORT = {"encoding": "utf-8", "sep": ";", "decimal": ","}".
2. Save changes.
3. Restart Superset.
4. Create a "pivot table" graph.
5. Select a numeric metric
6. Click on 'Download' -> 'Export to pivoted .CSV'

Screenshots/recordings

No response

Superset version

4.1.1

Python version

3.10

Node version

I don't know

Browser

Firefox

Additional context

Source code:

I'm using version 4.1.1, but I tried updating 'post_processing.py' to match what's in the master branch's 'client_processing.py' since I needed PR #29898 (which doesn't seem to affect this issue).

Feature flags:

"DASHBOARD_RBAC": True,
"ENABLE_TEMPLATE_PROCESSING": True,
"CACHE_QUERY_BY_USER": True,
"CACHE_IMPERSONATION": True

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]

The "Error 505" you're encountering when exporting a pivoted CSV with the custom CSV_EXPORT configuration might be related to how Superset handles different encodings, separators, and decimal formats during CSV export. Unfortunately, specific details on how Superset manages these configurations or any error handling mechanisms for them are not available in the current knowledge base.

However, the issue might be due to the custom separator (sep: ";") and decimal (decimal: ",") settings conflicting with the expected format during the export process. Since you mentioned that this configuration doesn't work for normal CSV export either, it might be worth testing with default settings or different combinations to identify the root cause.

Additionally, since you have already tried updating post_processing.py to match the master branch's client_processing.py, it seems that PR #29898 does not address this specific issue. You might want to check if there are any recent updates or patches related to CSV export in the Superset repository that could resolve this problem.

For now, reverting to default CSV export settings or experimenting with different configurations might help as a temporary workaround.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}