incubator-superset | Apache Superset is a Data Visualization | Data Visualization library
kandi X-RAY | incubator-superset Summary
kandi X-RAY | incubator-superset Summary
Apache Superset is a Data Visualization and Data Exploration Platform
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of incubator-superset
incubator-superset Key Features
incubator-superset Examples and Code Snippets
Lines of Code : 137License : Non-SPDX (Apache License 2.0)
Copy/**
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
/**
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
/**
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
Community Discussions
Trending Discussions on incubator-superset
QUESTION
(superset) cwj0@ubuntu:~/anaconda3/envs/superset/lib/python3.7/site-packages/incubator-superset$ superset init
Traceback (most recent call last):
File "/home/cwj0/anaconda3/envs/superset/bin/superset", line 33, in
sys.exit(load_entry_point('apache-superset', 'console_scripts', 'superset')())
File "/home/cwj0/anaconda3/envs/superset/bin/superset", line 22, in importlib_load_entry_point
for entry_point in distribution(dist_name).entry_points
File "/home/cwj0/anaconda3/envs/superset/lib/python3.7/site-packages/importlib_metadata/__init__.py", line 951, in distribution
return Distribution.from_name(distribution_name)
File "/home/cwj0/anaconda3/envs/superset/lib/python3.7/site-packages/importlib_metadata/__init__.py", line 542, in from_name
raise PackageNotFoundError(name)
importlib_metadata.PackageNotFoundError: No package metadata was found for apache-superset
ANSWER
Answered 2022-Jan-14 at 00:53Solved. Because this is the need to refresh the permissions after I add a new page, I don't know why the dependencies are missing, and the installation is solved.
pip install -r requirements/local.txt，pip install -e .
QUESTION
I pulled the official superset image:
...ANSWER
Answered 2020-Dec-08 at 18:54I don't have a lot of experience with Docker, but I don't think you should use 8088 as the host for your MySQL database.
Try using mysql://user:password@172.19.0.8:6603/database-name as the URI.
QUESTION
So I have followed: https://preset.io/blog/2020-07-02-hello-world/ for creating a simple hello-world plugin and also followed this video: https://www.youtube.com/watch?v=f6up5x_iRbI&t=936s
It worked really smooth in there but when I try it at my end, I run into a lot of issues. I tried running it on docker as well, still it didn't work. Pypi version seems to be outdated. Here's the error i get when I try to run npm run prod:
ERROR in ./src/visualizations/presets/MainPreset.js Module not found: Error: Can't resolve '@superset-ui/plugin-chart-hello-world' in '/home/spidey/apache_superset/superset-dev/incubator-superset/superset-frontend/src/visualizations/presets'
When I open the MainPreset.js file:
Here is how it looks: And the bottom configuration:
Going back to superset-frontend/node-modules/@superset-ui/
I have:
When I run npm run dev-server:
But since I am running it on Virtual Instance so I can't open up the browser and check, whereas when I try npm run prod the error still persists:
ANSWER
Answered 2020-Jul-29 at 16:17I have a suspicion of what's happening here. Is it possible that your plugin is not in superset-frontend/package.json?
Note that if you put your hello-world plugin in package.json, and THEN do npm install, the npm install won't work. It's frustrating, but you need to do these things in the correct order:
npm install(this nukes any npm links)- add the plugin to your package.json (version number doesn't really matter)
- do the
npm link ../../......routine npm run dev-server
Hope that helps, but I'll continue to try to help wherever I'm able.
QUESTION
I am running Superset via Docker. I enabled the Email Report feature and tried it:
However, I only receive the test email report. I don't receive any emails after.
This is my CeleryConfig in superset_config.py:
...ANSWER
Answered 2020-Apr-21 at 14:06I believe Celery needs to run inside your superset container - so you'll need to modify your dockerfile and entrypoint.
BUT you should really first daemonize celery so you don't have to monitor and restart celery [see how to detect failure and auto restart celery worker and http://docs.celeryproject.org/en/latest/userguide/daemonizing.html].
See an example here for how to run a daemonized celery process in docker: Docker - Celery as a daemon - no pidfiles found
QUESTION
I use an open-source server application running on Docker Compose. It has a few services, including PostgreSQL DB and Redis.
How can I best deploy this application to AWS in full IaC with Terraform?
ecs-cli
ecs-cli now supports sending docker compose configs in Amazon ECS.
However, I do not think it could be integrated with the Terraform workflow (which is maybe not a big fuss). What I know for sure is that ecs-cli is not supported in CloudFormation, as per this issue, still open at this time. So I assume it cannot easily be added to Terraform either.
- Take your
docker-compose.ymlfile, translate it tokubectlYAML. - (Prepare to doing so every time the package upgrades).
- Deploy using Terraform's + EKS APIs (minimal example).
But that is not fully IaC yet. And you have to retranslate your config each time the docker-compose changes in the source repository. And it sounds like a lot of work.
3. Using a Helm chart- Write a Helm chart for the application.
- Run Terraform to start a cluster.
- Still run Terraform with a
helmprovider to install the application with Helm on the cluster.
I read Kompose can automagically translate a Docker Compose configuration to a k8s configuration, but they don't appear to be ported on AWS, not to talk about Terraform.
5. [Not OK] The dirty AMI solution- Build a custom EC2 AMI with Packer.
- Using Terraform, set up the DB, Redis and all permissions / network / etc.
- Start an EC2 instance with the custom AMI.
- The AMI contains (customized) application code, especially the
docker-compose.yml. And the Docker images. - The AMI starts a Docker Compose
systemctlservice.
That would kind of hurt: long builds, difficult monitoring, no scaling.
Side notes- I mentioned I need full IaC. What I mean by it is:
- The written config (and it only) on
mastertells you what is deployed. - The deploy will complete without my team having to run any other command. It basically works either on CI/CD or on single-push'n'go.
- Monitoring and alerting are easily configured in the IaC.
- The written config (and it only) on
- I wish to replace some services with AWS components (namely, the PostgreSQL service by an RDS, and the Redis service with an ElastiCache).
- The application happens to be Apache Superset. However I am also wondering what is considered the best general approach to this Docker Compose problem.
ANSWER
Answered 2020-Apr-20 at 14:22Who knows, ecs-cli-v2 might be better integrated with CloudFormation and/or Terraform.
As mentioned in the question. Probably the best solution, albeit requiring a (little) effort to parametrize Helm.
See also: Getting started with Helm.
3. Docker Swarm + CloudFormation + TerraformDocker Swarm now accepts inputs from a docker-compose.yml file. The template can be found and configured here. Once configured, it may be integrated to a Terraform infrastructure.
This (3-year old) tutorial explains how to use Docker Swarm mode on AWS.
To launch the container, if necessary (not fully investigated, feedback is welcome), you could use Terraform's local-exec. This way you can SSH into the master node and run docker stack deploy and other similar commands, while still having all written down in IaC style.
QUESTION
I have searched a lot about this question, there are no concrete answers to this. I have a AWS Redshift DB, has around 6-7 schema' with 10-12 tables in each. and dashboards are made within schema level as well as across schema.
here's the use case:
- I have some users who needs to see only dashboards related to "schema 1" but not "schema 2"
- I have some other users who are looking at dashboards which are connected to "schema 1" and as well as "schema 2", but m not able to find any workaround to this.
I have seen a thread saying that it's possible to give access to schema but they haven't mentioned that How.
https://github.com/apache/incubator-superset/issues/5483#issuecomment-494227986
...ANSWER
Answered 2020-Jan-29 at 11:12As per the Superset documentation, you can not create access level on the schema but you can create access on data source level. Or you can create custom data sources and can create desired roles as per your need.
Refer: https://superset.incubator.apache.org/security.html#managing-gamma-per-data-source-access
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install incubator-superset
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
