-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Error in Query: Input to aggregation-name does not match schema #14080
Comments
Hi @etoulas Can you post the output of the following |
This is probably the same bug as #14076 fixes |
This comment has been minimized.
This comment has been minimized.
Good job! I just found other queries that are structured the exact same way (for different customer IDs) and they work. Last modification of a particular query was 2 months ago... |
Yes, you are right, this is spot on! The difference is that the implicit join was missing. I tried to add it to the example that was still working and boom. Is this indeed the same issue that is solved in #14076 ? The description is very brief there. |
Yes, that PR solves this issue. It's currently set to go into the upcoming 0.38.0 release, but I don't know if it can easily be changed to the next 0.37.x patch release. Until then, I would recommend that you downgrade to 0.37.0.2, since that's the last working version. |
Thank a lot @flamber! Downgrading is safe in that case? |
@etoulas There's no such thing as "safe", but I would say safe-ish, since there's fairly few changes between 0.37.0 and 0.37.3. Always make backups before upgrading, downgrading or any other big operations, so you have something to revert back to. |
Ok, that makes sense. We do daily backups, so I will go for the downgrade and keep an eye on the upcoming versions. |
The implicit "source" table alias should be a string instead of a keyword, as the schema requires strings there. This will allow a custom expression to work with an aggregation again. Resolves #14080
Describe the bug
We upgraded from 0.36.3 to 0.37.3 and suddenly a lot of "custom queries" show the following error message where usually a result/chart is shown.
What actually fixes the issue is removing the custom expression "Bestellwert" which multiplies 3 fields from the first table in the join.
I don't quite understand what the problem is based on the error message. Metabase created some aliases for the joined tables, one which is "List". There is also a field with the name "source" in one of the tables.
Logs
Stacktrace of "Input to aggregation-name does not match schema:"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Existing custom expressions on joined tables should continue to work with the new Metabase version.
Information about your Metabase Installation:
You can get this information by going to Admin -> Troubleshooting.
Severity
This is blocking some users, especially as the broken queries are spread all over the place.
Obviously, I don't want to go through 2000+ queries to check for that error and redo them manually...
The text was updated successfully, but these errors were encountered: