what issue are you running into? 9 times out of 10, I’ve seen that people run into 1 of the following issues: • Networking: Superset can’t physically connect to Pinot. This is a hard one to give general advice on, b/c people run all types of different networking configurations but I’d recommend the usual steps with your debugging hat on! If you’re using Docker, fire up the shell for the backend container and try connecting directly using the database driver (Superset just wraps / sits on top of the driver anyway). Dive deeper into the error. Use ping / wget / etc to test your networking setup, and iterate. • Database driver not found: The database driver needs to be installed in the same python context that Superset is running in. Sometimes people will add the driver and do docker-compose down then up and Superset still hasn’t found the driver. So doing a

pip freeze | grep 'pinot'

when you’re in the shell environment for the backend (if you’re using docker compose this is called

superset_app

) will confirm if the pinot driver actually got installed or not 😄

let me know what additional context you can provide @User

Docker works well for containerizing your dependencies and environment but isn’t a necessity to use either Pinot or Superset

but first, are you running Superset “natively” (e.g. by running the python backend server + the node frontend server) or within Docker? Within Kubernetes? How about Pinot?

Superset’s backend is written in Python, so you just need to make sure that the pinot driver (https://pypi.org/project/pinotdb/) is installed in the same python / virtual environment context as Superset is in. Does that make sense? If you see “Pinot” listed in the add database modal in Superset, then Superset can find this driver // installation worked. The next step is to figure out how to connect Pinot to Superset