-
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
"Expected native source query to be a string, got: clojure.lang.PersistentArrayMap" on nested queries #32121
Comments
Underlying problem is, that after #31111 POST request to Possible solution could be either 1. using collection key only with mongo queries on the frontend, or 2. modify I wanted to write that I'd like to try to implement the fix, but in a meantime @kulyk got assigned the issue :) |
Hey there @lbrdnk. Thank you for sharing your spot-on analysis of the problem :) As the bug is a high-priority blocker for the next release, we'll take care of this one in-house. |
Status: I have a fix for this that seems to work without breaking anything else. I'm having trouble getting the |
Previously this was done by checking if the FE had included `:collection "some_table"` on the native query, but that's been included for SQL queries lately, and broke "Explore Results". Includes new e2e tests: one for this issue itself, and another that the fix doesn't break real Mongo native queries. Fixes #32121.
Previously this was done by checking if the FE had included `:collection "some_table"` on the native query, but that's been included for SQL queries lately, and broke "Explore Results". Includes new e2e tests: one for this issue itself, and another that the fix doesn't break real Mongo native queries. Fixes #32121.
Previously this was done by checking if the FE had included `:collection "some_table"` on the native query, but that's been included for SQL queries lately, and broke "Explore Results". Includes new e2e tests: one for this issue itself, and another that the fix doesn't break real Mongo native queries. Fixes #32121.
Previously this was done by checking if the FE had included `:collection "some_table"` on the native query, but that's been included for SQL queries lately, and broke "Explore Results". Includes new e2e tests: one for this issue itself, and another that the fix doesn't break real Mongo native queries. Fixes #32121. Co-authored-by: Braden Shepherdson <braden@metabase.com>
Previously this was done by checking if the FE had included `:collection "some_table"` on the native query, but that's been included for SQL queries lately, and broke "Explore Results". Includes new e2e tests: one for this issue itself, and another that the fix doesn't break real Mongo native queries. Fixes #32121.
Previously this was done by checking if the FE had included `:collection "some_table"` on the native query, but that's been included for SQL queries lately, and broke "Explore Results". Includes new e2e tests: one for this issue itself, and another that the fix doesn't break real Mongo native queries. Fixes #32121.
I still get this error whenever I press the Metabase installation: v0.46.6.1 Logs:
|
@beshoyabdelmalak the fix is coming in 46.7, 46.6.1 is a security patch. |
Okay, thanks for the clarification. |
Describe the bug
When using "explore results", there's something we're sending wrong to the backend which causes the exception
To Reproduce
Expected behavior
It should work
Logs
Information about your Metabase installation
v47.0-RC2
Severity
P1
Additional context
No response
The text was updated successfully, but these errors were encountered: