-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Not able to switch between databases after a question is created #38354
Comments
I think this might be a frontend bug rather than a Cljs/MLv2 bug. What should be happening here is
I'm guessing some or all of these steps aren't happening correctly. The error that comes back from the Query Processor is maybe not the most helpful error (we can fix this separately) but it's basically saying you're trying to run a query with a Table that either doesn't exist or belongs to a different Database. So that would point to the theory the the FE is not properly clearing things out and using Tables from the old DB in combination with the new one |
I'm reassigning to the Query Components team since I'm like 90% sure this is a FE bug, if it turns out to be a backend/MLv2 bug after all please ping me. I'll open a separate backend issue to improve that error message. |
Opened #38381 to track improving QP error message |
@camsaul Thanks for the detailed explanation! Sorry for tagging the wrong team |
Cannot reproduce in |
In |
Describe the bug
After you create a question you are not able to switch between databases
To Reproduce
Make sure you have 2 Databases Connected. In my case I have the App DB and Sample Database
Expected behavior
The GUI is able to identify changes in the Datasource
Logs
Information about your Metabase installation
Not able to replicate on master but able to hit it on 1.48.4 (and older 48 versions)
Severity
A customer is currently blocked in trying to replace Datasources
Additional context
I need to test but there is the possibility that if this action was already performed on the 47 and you upgraded to 48 things would still break
The text was updated successfully, but these errors were encountered: