-
Notifications
You must be signed in to change notification settings - Fork 2.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
sql: Vitess cannot support Grafana 10+ CTEs #13632
Comments
@derekperkins Any chance you could share the query that is breaking vtgate? |
There's a test here for recursive queries And a comment about how it relates to Vitess |
I submitted a PR based on that comment, hopefully they accept it and it works |
Still trying to get this to work. There has been no movement on the original PR. This has been longer coming, but |
Now that Vitess have CTE support, do you want to try it? |
Planning on rolling out v21 this weekend, then I'll try it |
v21 actually made things worse. Previously, Grafana detected that recursive CTEs weren't supported and would fallback to other mechanisms. Now that Vitess says that they are supported, it uses the regular recursive SQL, but that fails. Here is the vttablet log. This runs on initial startup and for every search, so it makes grafana unusable.
|
That's a bummer. Can you create a separate issue with the query so that we can try to fix it? |
@derekperkins wdyt - can we close this issue now? |
Sure. I'll open it again once this is available in a release if there are any other issues |
We've used Vitess for Grafana persistence for several years, but after upgrading to v10, certain functionality including dashboard list/search fails due to usage of CTEs. This is a known issue, I just wanted to call this out specifically since we have tracked compatibility with major projects in the past. Feel free to close if it isn't useful, but it'll at least help anyone searching.
"Search failed" error="Error 1235: unsupported: with expression in select statement"
Related issues:
The text was updated successfully, but these errors were encountered: