dosubot[bot] commented on issue #33691:
URL: https://github.com/apache/superset/issues/33691#issuecomment-2940584591

   <!-- Answer -->
   If the Trino connector still does not appear in the Superset UI after 
installing it with the recommended method, here are the most likely causes and 
next steps:
   
   1. **Backend Denylist Configuration**: Superset controls which database 
engines appear in the UI using the `DBS_AVAILABLE_DENYLIST` configuration in 
the backend. If Trino is listed here, it will not show up as an option, 
regardless of whether the driver is installed. Check your Superset 
configuration (typically in `superset_config.py` or environment variables) and 
ensure that Trino is not present in the denylist. The frontend simply reflects 
what the backend exposesβ€”there are no Trino-specific feature flags or UI 
toggles. For reference, see how engine visibility is managed in the backend 
[source](https://github.com/apache/superset/blob/20519158d2ab6325f7564b16615a99fe0ebe7a38/superset/db_engine_specs/__init__.py).
   
   2. **Driver Installation**: The Trino connector is an optional dependency. 
If the Python package is not installed in the correct environment, Superset 
cannot register the engine. Double-check that `/app/.venv/bin/pip install 
.[trino]` (or `pip install trino sqlalchemy-trino`) completes successfully in 
your running container. You can verify this by running `/app/.venv/bin/pip 
list` inside the pod and confirming that `trino` and `sqlalchemy-trino` are 
present. If not, the installation step may have failed or run in the wrong 
environment [source](https://github.com/apache/superset/issues/32186).
   
   3. **Pod Restart and Script Execution**: If the `~/bootstrap` file is 
missing, the bootstrap script may not have run or may have failed. Check the 
pod logs for errors during startup, especially around the time the bootstrap 
script should execute. Ensure the script has execute permissions and that the 
container user has the necessary rights to install Python packages and write to 
the home directory.
   
   4. **Custom Images for Production**: For production deployments, it is 
recommended to build a custom Docker image with all required drivers 
pre-installed, rather than relying on runtime installation via bootstrap 
scripts. This avoids issues with missing dependencies and ensures consistent 
environments across pods.
   
   5. **Database Engine Registration**: The Trino engine spec is implemented in 
Superset and should be auto-registered if the driver is present 
[source](https://github.com/apache/superset/blob/20519158d2ab6325f7564b16615a99fe0ebe7a38/superset/db_engine_specs/trino.py).
 There are no extra steps required to "enable" it in the UI beyond having the 
driver installed and not being denied by config.
   
   If you have confirmed all of the above and Trino still does not appear, 
please share the output of `/app/.venv/bin/pip list` from your running Superset 
container and any relevant log messages from pod startup. This will help 
pinpoint whether the issue is with package installation, configuration, or 
something else.
   
   
   <!-- Dosu Comment Footer -->
   *To reply, just mention my name [@dosu](https://go.dosu.dev/dosubot).*
   
   ---
   <sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/02915738-2e74-4c3d-9f83-e8a858d1b8a4?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/02915738-2e74-4c3d-9f83-e8a858d1b8a4?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/02915738-2e74-4c3d-9f83-e8a858d1b8a4?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/02915738-2e74-4c3d-9f83-e8a858d1b8a4?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/02915738-2e74-4c3d-9f83-e8a858d1b8a4?feedback_type=hallucination)
 | [Report 
πŸ›](https://app.dosu.dev/response-feedback/02915738-2e74-4c3d-9f83-e8a858d1b8a4?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/02915738-2e74-4c3d-9f83-e8a858d1b8a4?feedback_type=other)</sup>&nbsp;&nbsp;[![Join
 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[!
 [Share on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/33691)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to