Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shouldn't run migration when there's no initial schema #5043

Closed
ManiMozaffar opened this issue May 21, 2024 · 1 comment
Closed

Shouldn't run migration when there's no initial schema #5043

ManiMozaffar opened this issue May 21, 2024 · 1 comment

Comments

@ManiMozaffar
Copy link

Bug description

If there's no schema out there, why would we run the migration?
I don't care about my old telemetry data, I can just delete the clickhouse's db and run the new version, it should create models and stamp the latest version identifier of migration, without trying to run all the migration, for smoother experience.

Expected behavior

Should skip running migration, if there's no previous schema setup.

How to reproduce

  1. Delete clickhouse
  2. Try to run the service again

Version information

  • Signoz version: 0.44
  • Browser version: Not related
  • Your OS and version: Mac OS
  • Your CPU Architecture(ARM/Intel): ARM

Additional context

Thank you for your bug report – we love squashing them!

@srikanthccv
Copy link
Member

The final version of the latest schema doesn't exist as a standalone statement. It has to be via migration. This step is quick and already smooth.

@srikanthccv srikanthccv closed this as not planned Won't fix, can't repro, duplicate, stale May 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants