mirror of
https://github.com/apache/superset.git
synced 2026-05-08 09:25:56 +00:00
752ebd47cb
- Snapshot all four versioned docs sections at v6.1.0; master continues to serve as "Next" (lastVersion: current, banner: unreleased) so editing master keeps updating the canonical URLs - Enable the previously-disabled components plugin and version it - Rename stale "developer_portal" references to "developer_docs" across package.json scripts, manage-versions.mjs, theme files (DocVersionBadge, DocVersionBanner), DOCS_CLAUDE.md, and README.md (URL backward-compat redirect /developer_portal/* preserved) - Add admin_docs version scripts; drop dead "tutorials" plugin id from the version badge - Generalize fixVersionedImports in manage-versions.mjs to walk every section's snapshot and rewrite ../../src/ and ../../data/ imports, catching admin_docs and components files that previous version cuts would have broken - Remove orphan files: developer_portal_versions.json, tutorials_versions.json, and stray empty versions.json files inside components/ and developer_docs/ content directories
8.0 KiB
8.0 KiB
title, sidebar_position
| title | sidebar_position |
|---|---|
| Community Extensions | 11 |
Community Extensions
This page serves as a registry of community-created Superset extensions. These extensions are developed and maintained by community members and are not officially supported or vetted by the Apache Superset project. Before installing any community extension, administrators are responsible for evaluating the extension's source code for security vulnerabilities, performance impact, UI/UX quality, and compatibility with their Superset deployment.
Extensions
| Name | Description | Author | Preview |
|---|---|---|---|
| Extensions API Explorer | A SQL Lab panel that demonstrates the Extensions API by providing an interactive explorer for testing commands like getTabs, getCurrentTab, and getDatabases. Useful for extension developers to understand and experiment with the available APIs. | Michael S. Molina |  |
| SQL Query Flow Visualizer | A SQL Lab panel that transforms SQL queries into interactive flow diagrams, helping developers and analysts understand query execution paths and data relationships. | Mehmet Salih Yavuz |  |
| SQL Lab Export to Google Sheets | A Superset extension that allows users to export SQL Lab query results directly to Google Sheets. | Michael S. Molina |  |
| SQL Lab Export to Parquet | Export SQL Lab query results directly to Apache Parquet format with Snappy compression. | Evan Rusackas |  |
| SQL Lab Query Comparison | A SQL Lab extension that enables side-by-side comparison of query results across different tabs, with GitHub-style diff visualization showing added/removed rows and columns. | Michael S. Molina |  |
| SQL Lab Result Stats | A SQL Lab extension that automatically computes statistics for query results, providing type-aware analysis including numeric metrics (min, max, mean, median, std dev), string analysis (length, empty counts), and date range information. | Michael S. Molina |  |
| Editor Snippets | A SQL Lab extension for managing and inserting reusable code snippets into the editor, with server-side persistence per user. | Michael S. Molina |  |
| SQL Lab Query Estimator | A SQL Lab panel that analyzes query execution plans to estimate resource impact, detect performance issues like Cartesian products and high-cost operations, and visualize the query plan tree. | Michael S. Molina |  |
| Editors Bundle | A Superset extension that demonstrates how to provide custom code editors for different languages. This extension showcases the editor contribution system by registering alternative editors that can replace Superset's default Ace editor. | Michael S. Molina |  |
How to Add Your Extension
To add your extension to this registry, submit a pull request to the Apache Superset repository with the following changes:
- Add a row to the Extensions table above using this format:
| [Your Extension](https://github.com/your-username/your-repo) | A brief description of your extension. | Your Name | <a href="/img/extensions/your-screenshot.png" target="_blank"><img src="/img/extensions/your-screenshot.png" alt="Your Extension" width="120" /></a> |
-
Add a screenshot to
docs/static/img/extensions/(recommended size: 800x450px, PNG or JPG format) -
Submit your PR with a title like "docs: Add [Extension Name] to community extensions registry"