Superset feature gaps and questions to the community

[Bhav2308]

Hi All.

We're in the process of implementing superset while it provides many powerful features out of the box, but there are few areas where deeper understanding is required.

Below are some of the questions as per requirements:

1. How can we integrate custom cron based reporting in Superset?
   We’re looking to schedule automated report generation using cron jobs and want users to be able to download or view these reports directly from the Superset UI. Is there a recommended approach for integrating this functionality, or are there existing community efforts or plugins that support this use case?

2. What is the recommended approach to enable fully asynchronous downloads (e.g. CSV, PDF) for large datasets in Apache Superset?
   We want to enable users to export large datasets without causing performance issues. Superset supports async queries, but exports (especially PDFs) are still synchronous. Is there a scalable method to handle this?

3. What strategies does the Superset community recommend for handling extremely large data exports (e.g. more than 10 million rows)?
   Exports of large data volumes can crash Superset or take too long. Are there known solutions such as batch exports or worker based processing to support such large datasets?

4. Can Superset dashboards dynamically create hyperlinks or buttons?
   Is there a native or plugin based way to embed dynamic hyperlinks in dashboards that respond to POST requests using a button with parameterized data?

5. Is there a recommended method to build a native or plugin based interface in Superset to view already generated reports or scheduled (cron) outputs?
   We want users to be able to view past generated reports from within Superset. Are there tools or APIs that support this kind of archival and access interface?

6. How can we configure Superset to auto send emails (e.g. reports or alerts) directly from the UI, without relying solely on backend configurations?
   We’re interested in letting users configure email scheduling and delivery directly from the UI. Is this currently supported or on the roadmap?

7. What is the best practice for setting up scheduled report generation and delivery (email) within Superset?
   Superset has Alerts & Reports, but documentation is sparse. What are the best practices for automating report scheduling via email?

8. Does Superset support or plan to support FTP report delivery?
   Many enterprise environments require reports to be uploaded to secure FTP servers. Is there native support or a recommended integration path for this?

9. Are there any plans to introduce advanced search (full text or semantic) across dashboards, charts, and datasets in Superset?
   Current search is limited to exact matches on names. Will Superset add support for full text or metadata based search across objects?

10. What are the best practices for implementing project specific customizations in Superset, such as applying themes, custom filters, or access control rules per project/client?
    For multitenant or client specific implementations, how can one manage separate themes, filters, and data restrictions effectively?

11. Is there any way to enable password protection or encryption for PDF reports generated from Superset dashboards?
    Can Superset secure exported PDFs by adding password protection or encryption, either natively or via a plugin or post processing script?

12. Does Superset plan to support TTL (Time to Live) or auto deletion for generated reports?
    Superset supports TTL for cached queries, but can it automatically expire or delete generated reports after a configurable duration?

13. How well does Superset support multi language (e.g. Spanish, French) reporting and UI translations, especially in a reporting context?
    Flask-Babel partially translates the UI, but we need full report translation. Is this fully supported or being improved?

14. Can Superset support exporting individual slices or specific sections of a dashboard to PDF instead of only exporting the full dashboard?
    We often need to export only one chart or a specific part of a dashboard. Is selective or custom export supported or planned?

15. Are there any tools or plugins available for monitoring and auditing within Superset, such as tracking user actions, dashboard access logs, or download history?
    For enterprise governance, we need to monitor superset (crashes, cpu, memory, usage). Are there any existing tools or plans for native support?

[dosubot[bot]]

1. Custom Cron-Based Reporting: There isn't a specific plugin mentioned for integrating custom cron-based reporting in Superset. However, you can use the existing Alerts & Reports feature, which allows scheduling using cron expressions. This feature requires configuration in superset_config.py and enabling the "ALERT_REPORTS" feature flag ^[1].

2. Asynchronous Downloads: Superset supports asynchronous operations for queries using the GlobalAsyncQueries feature flag, but specific plugins for fully asynchronous exports like CSV or PDF are not mentioned. You might need to implement a custom solution or explore community contributions for this functionality ^[2].

3. Handling Large Data Exports: For extremely large data exports, consider using batch processing or worker-based solutions. Superset's current export functionality may not handle very large datasets efficiently, so external processing might be necessary.

4. Dynamic Hyperlinks or Buttons: Superset allows for dynamic hyperlinks in dashboards using the AnchorLink component, which can create links and buttons within dashboards ^[3].

5. Viewing Generated Reports: There isn't a specific method mentioned for viewing past generated reports directly in Superset. You might need to develop a custom interface or use external tools to manage report archives.

6. Email Configuration from UI: Superset's Alerts & Reports feature allows email scheduling and delivery, but it requires backend configuration. Direct UI-based configuration isn't fully supported yet ^[1].

7. Scheduled Report Generation and Delivery: Best practices include configuring the Alerts & Reports feature with proper cron expressions and ensuring email settings are correctly set up in the configuration files ^[1].

8. FTP Report Delivery: There is no native support for FTP report delivery mentioned. You might need to implement a custom solution or use external scripts to handle FTP uploads.

9. Advanced Search: Current search functionality is limited, and there are no specific plans mentioned for full-text or semantic search enhancements.

10. Project-Specific Customizations: Superset supports customizations through environment tag configurations and extra related query filters, which can help manage themes, filters, and access control for multi-tenant implementations ^[4].

11. PDF Encryption: There is no mention of native support for password protection or encryption of PDF reports. You might need to use external tools or scripts for post-processing.

12. TTL for Reports: Superset does not currently support TTL for generated reports. This feature is available for cached queries but not for reports.

13. Multi-Language Support: Superset uses Flask-Babel for UI translations, but full report translation support is not fully detailed. Improvements may be needed for comprehensive multi-language reporting.

14. Selective Export of Dashboard Sections: There is no specific mention of support for exporting individual slices or sections of a dashboard. This might require custom development.

15. Monitoring and Auditing: Superset logs user actions and supports auditing through its logging system, which tracks various user activities and interactions ^[5][6][7].

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}

[sfirke]

I'm glad Dosu bot answered, it would take an hour to reply to all of these. (1) and (6) and (7) look the same to me. Did you end up deploying Superset?