GitHub user dosubot[bot] added a comment to the discussion: Superset db upgrade 
is not triggering upgrade

<!-- Answer -->
Migration logs for `superset db upgrade` are output to the console 
(stdout/stderr) by default, using the `alembic.env` logger. If you're only 
seeing minimal output, it's likely because the logging level is set to WARN in 
the Alembic logging config, which suppresses INFO-level migration logs—even 
though migration scripts do log progress and warnings to `alembic.env` 
([source](https://github.com/apache/superset/blob/master/superset/migrations/alembic.ini),
 
[env.py](https://github.com/apache/superset/blob/master/superset/migrations/env.py),
 [PR #34521](https://github.com/apache/superset/pull/34521)).

To see more detailed migration logs, edit 
`/app/superset/migrations/alembic.ini` and set both `[logger_root]` and 
`[logger_alembic]` to `INFO` (or `DEBUG` for even more detail), and make sure 
the `[handler_console]` is set to output to the console. For example:

```ini
[logger_root]
level = INFO
handlers = console

[logger_alembic]
level = INFO
handlers = console
qualname = alembic.env
```

Then re-run the upgrade. If you're running Superset in Docker or Kubernetes, 
also check that your container or orchestration logs aren't filtering or 
redirecting stdout/stderr elsewhere.

Keep in mind, not all migration scripts print detailed progress—some are silent 
by design, so even with increased verbosity, you may only see start/end 
messages for certain steps.


<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*

---
<sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/9782ef8f-4047-4b5f-8841-eaa4aae02f79?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/9782ef8f-4047-4b5f-8841-eaa4aae02f79?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/9782ef8f-4047-4b5f-8841-eaa4aae02f79?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/9782ef8f-4047-4b5f-8841-eaa4aae02f79?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/9782ef8f-4047-4b5f-8841-eaa4aae02f79?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/9782ef8f-4047-4b5f-8841-eaa4aae02f79?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/9782ef8f-4047-4b5f-8841-eaa4aae02f79?feedback_type=other)</sup>

[![Chat with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&nbsp;[![Open
 in 
Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Migration%20logs%20for%20%60superset%20db%20upgrade%60%20are%20output%20to%20the%20console%20%28stdout/stderr%29%20by%20default%2C%20using%20the%20%60alembic.env%60%20logger.%20If%20you%27re%20only%20seeing%20minimal%20output%2C%20it%27s%20likely%20because%20the%20logging%20level%20is%20set%20to%20WARN%20in%20the%20Alembic%20logging%20config%2C%20which%20suppresses%20INFO-level%20migration%20logs%E2%80%94even%20though%20migration%20scripts%20do%20log%20progress%20and%20warnings%20to%20%60alembic.env%60%C2%A0%28%5Bsource%5D%28https%3A//github.com/apache/superset/blob/master/superset/migrations/alembic.ini%29%2C%C2%A0%5Benv.py%5D%28https%3A//github.com/apache/superset/blob/master/superset/migrations/env.py%29%2C%C2%A0%5BPR%20%2334521%5D%28https%3A//gith
 
ub.com/apache/superset/pull/34521%29%29.%0A%0ATo%20see%20more%20detailed%20migration%20logs%2C%20edit%20%60/app/superset/migrations/alembic.ini%60%20and%20set%20both%20%60%5Blogger_root%5D%60%20and%20%60%5Blogger_alembic%5D%60%20to%20%60INFO%60%20%28or%20%60DEBUG%60%20for%20even%20more%20detail%29%2C%20and%20make%20sure%20the%20%60%5Bhandler_console%5D%60%20is%20set%20to%20output%20to%20the%20console.%20For%20example%3A%0A%0A%60%60%60ini%0A%5Blogger_root%5D%0Alevel%20%3D%20INFO%0Ahandlers%20%3D%20console%0A%0A%5Blogger_alembic%5D%0Alevel%20%3D%20INFO%0Ahandlers%20%3D%20console%0Aqualname%20%3D%20alembic.env%0A%60%60%60%0A%0AThen%20re-run%20the%20upgrade.%20If%20you%27re%20running%20Superset%20in%20Docker%20or%20Kubernetes%2C%20also%20check%20that%20your%20container%20or%20orchestration%20logs%20aren%27t%20filtering%20or%20redirecting%20stdout/stderr%20elsewhere.%0A%0AKeep%20in%20mind%2C%20not%20all%20migration%20scripts%20print%20detailed%20progress%E2%80%94some%20are%20silent%20by%
 
20design%2C%20so%20even%20with%20increased%20verbosity%2C%20you%20may%20only%20see%20start/end%20messages%20for%20certain%20steps.)&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/discussions/37261)

GitHub link: 
https://github.com/apache/superset/discussions/37261#discussioncomment-15545150

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


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

Reply via email to