Tooltip for Map Deck.gl Polygon

[ginorossivn-eng]

I have tried version 4.00, 4.1.1 but none provide the tooltip for map deck.gl polygon. So, which version of superset has the Tooltip for Map Deck.gl Polygon?
Many thanks

[dosubot[bot]]

Hi @ginorossivn-eng! I'm Dosu and I’m helping the superset team.

Tooltip support for Deck.gl Polygon maps was added after Superset 4.1.1. In Superset 6.0 and newer, tooltips for Deck.gl Polygon charts are supported, but there are some limitations: there isn't a dedicated tooltip field selector; instead, the tooltip content is based on the fields you select in the chart's Query section (polygon column, metric, and dimensions). If you want custom tooltip text, you can create a concatenated field in your dataset, but it can't be used as a metric or polygon column due to data type requirements. Also, HTML formatting in tooltips is not rendered for security reasons, and advanced JavaScript tooltip customization is not recommended for production use due to security risks. For more details, see this discussion.

If you upgrade to Superset 6.0 or later, you should see tooltip support for Deck.gl Polygon maps.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[ginorossivn-eng]

@dosu can I install the superset 6.0 on Docker?

[dosubot[bot]]

Yes, Superset 6.0 can be installed using Docker and Docker Compose. You can use the official Docker image apache/superset:6.0.0 and follow the quickstart instructions. For example, you can set the TAG environment variable to 6.0.0 and run:

docker compose -f docker-compose-image-tag.yaml up

Or, if you cloned the Superset repository, check out the 6.0.0 tag and run:

git checkout tags/6.0.0
docker compose -f docker-compose-image-tag.yml up

This will start Superset 6.0 with all required services. For production, you may need to extend the Docker image to add database drivers or other dependencies. More details and troubleshooting tips are available in the official documentation and Docker build guide.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[ginorossivn-eng]

@dosu, I have already installed 4.1.1, I want to totally uninstall and then install 6.0, how to do it correctly?

[dosubot[bot]]

To fully uninstall Superset 4.1.1 and install 6.0 using Docker, follow these steps for a clean setup:

1. Stop and remove all Superset containers and volumes to clear out the metadata database and persistent data:

   docker compose down -v

   This deletes all persistent data, including charts, dashboards, and users. If you want to keep your data, back up your metadata database before running this command source.

2. Clean up any residual Docker volumes and files:

   docker system prune --volumes

   This ensures no leftover volumes cause migration errors source.

3. Check out the Superset 6.0 tag or set the TAG environment variable to 6.0.0, then start the new containers:

   git checkout tags/6.0.0
   docker compose -f docker-compose-image-tag.yml up

   Or use the official image:

   docker compose -f docker-compose-image-tag.yaml up

   source

4. Once the containers are running, initialize Superset inside the container:

   docker exec -it <superset_container_name> superset db upgrade
   docker exec -it <superset_container_name> superset init

   This applies database migrations and sets up permissions source.

5. If you have custom configuration, place your config file at docker/pythonpath_dev/superset_config_docker.py and restart the containers to apply changes source.

Best practices: always back up your metadata database before removing volumes or running migrations, make sure your Docker image and local code are both at the same version tag, and check the release notes for breaking changes source.

Let me know if you need details on backing up or restoring your metadata database, or if you have custom plugins/configurations to migrate.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[ginorossivn-eng]

@dosu Plz give me the code for this file: docker-compose-image-tag.yml

[dosubot[bot]]

Here’s the code for the official docker-compose-image-tag.yml used to run Superset 6.0+ with Docker Compose. This file defines all the required services (Superset app, Postgres, Redis, Celery workers, etc.) and uses the TAG environment variable to select the Superset version. Make sure you have a docker/.env file with your own secure passwords and SECRET_KEY before running this in production. To use Superset 6.0, set TAG=6.0.0 before starting.

# -----------------------------------------------------------------------
# We don't support docker compose for production environments.
# If you choose to use this type of deployment make sure to
# create your own docker environment file (docker/.env) with your own
# unique random secure passwords and SECRET_KEY.
# -----------------------------------------------------------------------

version: "3.7"

x-superset-image: &superset-image apachesuperset.docker.scarf.sh/apache/superset:${TAG:-latest-dev}
x-superset-volumes: &superset-volumes
  - ./docker:/app/docker
  - superset_home:/app/superset_home

services:
  redis:
    image: redis:7
    container_name: superset_cache
    restart: unless-stopped
    volumes:
      - redis:/data

  db:
    env_file:
      - path: docker/.env # default
        required: true
      - path: docker/.env-local # optional override
        required: false
    image: postgres:16
    container_name: superset_db
    restart: unless-stopped
    volumes:
      - db_home:/var/lib/postgresql/data
      - ./docker/docker-entrypoint-initdb.d:/docker-entrypoint-initdb.d

  superset:
    env_file:
      - path: docker/.env # default
        required: true
      - path: docker/.env-local # optional override
        required: false
    image: *superset-image
    container_name: superset_app
    command: ["/app/docker/docker-bootstrap.sh", "app-gunicorn"]
    user: "root"
    restart: unless-stopped
    ports:
      - 8088:8088
    depends_on:
      superset-init:
        condition: service_completed_successfully
    volumes: *superset-volumes

  superset-init:
    image: *superset-image
    container_name: superset_init
    command: ["/app/docker/docker-init.sh"]
    env_file:
      - path: docker/.env # default
        required: true
      - path: docker/.env-local # optional override
        required: false
    depends_on:
      db:
        condition: service_started
      redis:
        condition: service_started
    user: "root"
    volumes: *superset-volumes
    healthcheck:
      disable: true

  superset-worker:
    image: *superset-image
    container_name: superset_worker
    command: ["/app/docker/docker-bootstrap.sh", "worker"]
    env_file:
      - path: docker/.env # default
        required: true
      - path: docker/.env-local # optional override
        required: false
    restart: unless-stopped
    depends_on:
      superset-init:
        condition: service_completed_successfully
    user: "root"
    volumes: *superset-volumes
    healthcheck:
      test:
        [
          "CMD-SHELL",
          "celery -A superset.tasks.celery_app:app inspect ping -d celery@$$HOSTNAME",
        ]

  superset-worker-beat:
    image: *superset-image
    container_name: superset_worker_beat
    command: ["/app/docker/docker-bootstrap.sh", "beat"]
    env_file:
      - path: docker/.env # default
        required: true
      - path: docker/.env-local # optional override
        required: false
    restart: unless-stopped
    depends_on:
      superset-init:
        condition: service_completed_successfully
    user: "root"
    volumes: *superset-volumes
    healthcheck:
      disable: true

volumes:
  superset_home:
    external: false
  db_home:
    external: false
  redis:
    external: false

To run Superset 6.0, use:

export TAG=6.0.0
docker compose -f docker-compose-image-tag.yml up

You can find more details and the latest version of this file in the official Superset repository.
For production, always customize your docker/.env file and consider extending the image for extra drivers or configuration as needed.
Source

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}