Apache Superset is a Data Visualization and Data Exploration Platform
Go to file
Daniel Vaz Gaspar 74cb82e1ad
fix: humanised changed on UTC on dashboards and charts (#10321)
* fix: API marshmallow3 drop utc for naive datetime fields

* fix: API marshmallow3 drop utc for naive datetime fields

* fix, tests

* isort and test

* black

* add and fix test

* fix comment
2020-07-15 19:09:32 +01:00
.github build: enable Cypress tests for visualizations (#10206) 2020-06-30 17:10:17 -07:00
RELEASING chore: improve release documentation (#10292) 2020-07-11 19:00:02 +03:00
docker build: Add python 3.8 to the build matrix (#9827) 2020-05-17 14:49:51 -07:00
docs docs(fix): /swaggerview/v1 has moved to /swagger/v1 (#10276) 2020-07-09 15:16:52 -07:00
helm/superset fix: Fix for updated cache dependency (#9850) 2020-05-20 09:42:43 -07:00
scripts chore: remove unused files from root (#10318) 2020-07-14 22:40:34 -07:00
superset fix: humanised changed on UTC on dashboards and charts (#10321) 2020-07-15 19:09:32 +01:00
superset-frontend fix: humanised changed on UTC on dashboards and charts (#10321) 2020-07-15 19:09:32 +01:00
tests fix: humanised changed on UTC on dashboards and charts (#10321) 2020-07-15 19:09:32 +01:00
.codecov.yml Adding codecov targets and thresholds (#7433) 2019-06-03 15:26:42 -07:00
.dockerignore SIP-32: Moving frontend code to the base of the repo (#9098) 2020-02-09 17:53:56 -08:00
.flaskenv Flask App factory PR #1 (#8418) 2019-11-20 15:47:06 +00:00
.fossa.yml SIP-32: Moving frontend code to the base of the repo (#9098) 2020-02-09 17:53:56 -08:00
.gitignore feat: Add owners and physical/virtual status to Datasets API list endpoint (#10025) 2020-06-10 22:04:40 +03:00
.pre-commit-config.yaml chore: bump black to 19.10b0 and mypy to 0.770 (#9378) 2020-04-04 13:23:18 -07:00
.pylintrc chore: Upgrade pylint to 2.5.3 and fix most new rules (#10101) 2020-06-18 14:03:42 -07:00
.rat-excludes [docker] fix, Dockerfile for frontend builds (#9114) 2020-02-12 15:48:24 +00:00
CHANGELOG.md doc: Add changelog for 0.36.0 (#9570) 2020-04-17 19:55:51 +03:00
CODE_OF_CONDUCT.md Copying in Markdown formatted Apache Code of Conduct. (#8615) 2019-11-20 14:42:53 -08:00
CONTRIBUTING.md chore: bump python dependencies (#9786) 2020-05-13 18:49:34 +03:00
DISCLAIMER Add disclaimer and remove counter (#6738) 2019-01-22 14:18:16 -08:00
Dockerfile fix: issue with duplicated dependencies (#9837) 2020-05-19 08:46:52 -07:00
Dockerfile-dev fix: issue with duplicated dependencies (#9837) 2020-05-19 08:46:52 -07:00
INSTALL.md Improvements related to ASF release process (#7539) 2019-07-03 22:33:14 -07:00
INTHEWILD.md docs: create INTHEWILD.md (#10212) 2020-07-12 18:56:02 -07:00
LICENSE.txt Introducing Inter UI & Fira typefaces (#9207) 2020-03-04 17:32:08 -08:00
MANIFEST.in Update MANIFEST.in (#9261) 2020-03-25 22:00:41 -07:00
NOTICE Add release refinements from 0.35.2 release (#8925) 2020-02-18 07:14:31 +02:00
README.md docs(readme): license info in README is redundant (#10314) 2020-07-14 13:27:02 -07:00
UPDATING.md chore: prefer allow/deny terminology (#10320) 2020-07-15 19:22:46 +03:00
docker-compose.yml Removing node_modules volume in docker-compose.yml (#10236) 2020-07-03 08:00:09 -07:00
pytest.ini feat: support nulls in the csv uploads (#10208) 2020-07-06 13:26:43 -07:00
requirements-dev.txt feat: Switch from nosetest to pytest (#10177) 2020-06-29 15:36:06 -07:00
requirements.txt fix: Bump FAB to 3.0.1 fix superset init (#10310) 2020-07-14 15:16:45 +01:00
setup.cfg docs(fix): /swaggerview/v1 has moved to /swagger/v1 (#10276) 2020-07-09 15:16:52 -07:00
setup.py fix: Bump FAB to 3.0.1 fix superset init (#10310) 2020-07-14 15:16:45 +01:00
tox.ini feat: Switch from nosetest to pytest (#10177) 2020-06-29 15:36:06 -07:00

README.md

Superset

Build Status PyPI version Coverage Status PyPI Get on Slack Documentation dependencies Status

Superset

A modern, enterprise-ready business intelligence web application.

Why Superset | Database Support | Installation and Configuration | Get Help | Contributor Guide | Resources | Superset Users

Screenshots & Gifs

View Dashboards


Slice & dice your data


Query and visualize your data with SQL Lab


Visualize geospatial data with deck.gl


Choose from a wide array of visualizations


Why Superset

Superset provides:

  • An intuitive interface to explore and visualize datasets, and create interactive dashboards.
  • A wide array of beautiful visualizations to showcase your data.
  • Easy, code-free, user flows to drill down and slice and dice the data underlying exposed dashboards. The dashboards and charts act as a starting point for deeper analysis.
  • A state of the art SQL editor/IDE exposing a rich metadata browser, and an easy workflow to create visualizations out of any result set.
  • An extensible, high granularity security model allowing intricate rules on who can access which product features and datasets. Integration with major authentication backends (database, OpenID, LDAP, OAuth, REMOTE_USER, ...)
  • A lightweight semantic layer, allowing to control how data sources are exposed to the user by defining dimensions and metrics
  • Out of the box support for most SQL-speaking databases
  • Deep integration with Druid allows for Superset to stay blazing fast while slicing and dicing large, realtime datasets
  • Fast loading dashboards with configurable caching

Database Support

Superset speaks many SQL dialects through SQLAlchemy - a Python SQL toolkit that is compatible with most databases. A list of supported databases can be found here.

Installation and Configuration

See in the documentation

Get Help

Slack Community Guidelines

If you decide to join the Community Slack, please adhere to the following rules:

1. Treat everyone in the community with respect.

  • We strive to make this community a warm place for people from all industries, use cases, geographies, and backgrounds. Harassment of any kind is not acceptable and wont be tolerated.
  • Please follow the guidelines as outlined in the Superset Community code of conduct here.

2. Use the right channel.

  • Channels are an effective way to organize and focus discussions while also empowering members to opt-in to the types of content theyre interested in. When questions are posted or discussions are started in the wrong channel, it dilutes the trust of the members in the channel and, more practically, makes it harder for your questions to be answered.

3. Ask thoughtful questions.

  • Were all here to help each other out. The best way to get help is by investing effort into your questions. First check and see if your question is answered in the Superset documentation or on Stack Overflow. You can also check Github issues to see if your question or feature request has been submitted before. Then, use Slack search to see if your question has already been asked and answered in the past. If you still feel the need to ask a question, make sure you include:

  • The steps youve already taken

  • Relevant details presented cleanly (text stacktraces, formatted markdown, or screenshots. Please dont paste large blocks of code unformatted or post photos of your screen from your phone)

  • The specific question you have or the specific type of help you're seeking

4. Avoid double posting

  • This Slack community is not a customer support channel and all members are here voluntarily. If you arent getting a response to a question you have, make sure you look at rules 1, 2, and 3. Its also worth remembering that there may not be someone in the community who has the context to help you out.

5. Communicate openly

  • Unless you have explicit permission from the person, please avoid sending direct messages to individuals. Communicating in public channels ensures that were all respecting each others attentions and we can scalably moderate our communication to mitigate harassment or discrimination. Do not use direct messages to pitch products and services. If you are receiving unwelcome direct messages, please notify an admin.

6. Practice good Slack hygiene by using threads for discussions and emojis for light reactions.

  • The medium is the message. Slack can foster a warm, collaborative, and organized community when used effectively. We want to respect peoples attentions (thread notifications > channel notifications > DM notifications) and we want to improve information density (a member should be able to browse and explore many convo threads, not just see one thread discussed in a top level channel).

Contributor Guide

Interested in contributing? Check out Contributing.MD to learn how to contribute and best practices.

Resources