When server pagination is enabled, only those records are seen in .csv/excel file, which are currently shown, not all pages and data are there in downloaded files

[devysh1907]

When server pagination is enabled, only those records are seen in .csv/excel file, which are currently shown, not all pages and data are there in downloaded files

[dosubot[bot]]

I found a similar discussion regarding the issue of CSV export with server pagination enabled. The discussion titled "ALLOW_FULL_CSV_EXPORT not working" is still open and might provide some insights ^[1].

To address this issue, you can enable the ALLOW_FULL_CSV_EXPORT configuration setting in Apache Superset. This setting allows users to export the full CSV of a table visualization type. However, be cautious as enabling this can lead to high memory or compute usage, potentially impacting server performance ^[2].

To continue talking to Dosu, mention @dosu.

---

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

[dosubot[bot]]

To enable the ALLOW_FULL_CSV_EXPORT feature in a Helm chart deployment of Apache Superset, you can configure it in the superset_config.py file or set it as an environment variable.

1. Using superset_config.py: You can override the feature flag in the superset_config.py file by adding the following entry:

   FEATURE_FLAGS = {
       "ALLOW_FULL_CSV_EXPORT": True,
   }

   This can be done using the configOverrides in your values.yaml file:

   configOverrides:
     feature_flags: |
       FEATURE_FLAGS = {
           "ALLOW_FULL_CSV_EXPORT": True
       }

2. Using Environment Variables: Alternatively, you can set the environment variable SUPERSET_FEATURE_ALLOW_FULL_CSV_EXPORT to true using the extraEnv configuration in your values.yaml file:

   extraEnv:
     SUPERSET_FEATURE_ALLOW_FULL_CSV_EXPORT: "true"

These configurations will enable the full CSV export feature in your Helm deployment of Apache Superset ^[1][2].

To continue talking to Dosu, mention @dosu.

---

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

[devysh1907]

@dosu

After enabling this flag, not able to download the paginated reports with all data

[dosubot[bot]]

Enabling the ALLOW_FULL_CSV_EXPORT flag should allow you to export the full dataset, not just the paginated view. If it's not working as expected, there might be other configurations or limitations affecting the export process.

Here are a few things to check:

1. Server Resources: Ensure that your server has enough memory and compute resources, as exporting large datasets can be resource-intensive and might fail if the server runs out of resources.

2. Superset Version: Make sure you are using a version of Apache Superset that supports this feature correctly. Sometimes, bugs in specific versions can affect functionality.

3. Logs and Errors: Check the server logs for any error messages or warnings that might indicate why the export is not working as expected.

4. Feature Flag Configuration: Double-check that the feature flag is correctly set in your configuration. If using environment variables, ensure they are correctly applied and recognized by the application.

If these steps don't resolve the issue, it might be helpful to look into any recent discussions or issues in the Superset repository that might address similar problems.

To continue talking to Dosu, mention @dosu.

---

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

[devysh1907]

@dosu
tell me minimum requirement of Server Resources for this functionality to work.

[dosubot[bot]]

The minimum server resource requirements for enabling full CSV export in Apache Superset can vary based on the size of the dataset and the complexity of the queries. However, here are some general guidelines:

1. Memory (RAM): At least 4GB of RAM is recommended for small to medium datasets. Larger datasets may require significantly more memory to handle the export process efficiently.

2. CPU: A multi-core processor (e.g., 2-4 cores) is advisable to ensure smooth operation, especially when handling concurrent requests or complex queries.

3. Disk Space: Ensure you have enough disk space to accommodate the exported files, especially if dealing with large datasets.

4. Network Bandwidth: Adequate network bandwidth is necessary if the server is accessed remotely, as large file downloads can consume significant bandwidth.

These are general recommendations, and you may need to adjust based on your specific use case and dataset size. Monitoring your server's performance during export operations can help determine if additional resources are needed.

To continue talking to Dosu, mention @dosu.

---

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