-
Notifications
You must be signed in to change notification settings - Fork 121
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
Integer or String? #240
Integer or String? #240
Comments
@ghuname do you use Table as visualization plugin? could you click "Query Inspector" -> "Query" -> copy to clipboard |
Yes I am using Table as visualization plugin and Format as: Table.
|
@ghuname did you upgrade your vertamedia-clickhouse-grafana to 2.x version? |
@ghuname issue still actual for you after an upgrade to 2.x? |
Yes I have upgraded to 2.0.1, and the issue is still present. |
I fixed same issue by converting count() to UInt32.
Seems like Grafana v6.6.2 or Clickhouse plugin can't understand type UInt64. |
@ghuname I tried to reproduce UInt64 + table plugin grafana dashboard with I just add only one thing for that so just use |
# 2.0.3 (2020-07-24) ## Enhancements: * add setup notes for Grafana 7.x to README * add SQL preprocessing logic on browser side with <% js code subset %>, #186, thanks @fgbogdan * improve alerts query processing for use case when `query(query_name, from, to)` time range is less than visible dashboard time range, see #237 * improve alerts json parsing in golang part for case when we have string fields in response which interprets as series name, see #230 * properly parsing POST queries in golang part of plugin, #228, thanks @it1804 ## Fixes: * add Vagrantfile for statefull environment and allow to upgrade scenario like grafana 7.1.0 + grafana-cli upgrade-all * fix #244 * fix #243 * add multiple dashboard examples for github issues: * fix #240 * fix #135 * fix #245 * fix #238 * fix #232 * fix #127 * fix #141
## Enhancements: * add setup notes for Grafana 7.x to README * add SQL preprocessing logic on browser side with <% js code subset %>, Altinity/clickhouse-grafana#186, thanks @fgbogdan * improve alerts query processing for use case when `query(query_name, from, to)` time range is less than visible dashboard time range, see Altinity/clickhouse-grafana#237 * improve alerts json parsing in golang part for case when we have string fields in response which interprets as series name, see Altinity/clickhouse-grafana#230 * properly parsing POST queries in golang part of plugin, Altinity/clickhouse-grafana#228, thanks @it1804 ## Fixes: * add Vagrantfile for statefull environment and allow to upgrade scenario like grafana 7.1.0 + grafana-cli upgrade-all * fix Altinity/clickhouse-grafana#244 * fix Altinity/clickhouse-grafana#243 * add multiple dashboard examples for github issues: * fix Altinity/clickhouse-grafana#240 * fix Altinity/clickhouse-grafana#135 * fix Altinity/clickhouse-grafana#245 * fix Altinity/clickhouse-grafana#238 * fix Altinity/clickhouse-grafana#232 * fix Altinity/clickhouse-grafana#127 * fix Altinity/clickhouse-grafana#141 Signed-off-by: Eugene Klimov <[email protected]>
# 2.1.0 (2020-08-13) ## Enhancement: * add "Skip comments" checkbox to query editor to pass SQL comments to server, fix Altinity/clickhouse-grafana#265 * add setup notes for Grafana 7.x to README * add SQL preprocessing logic on browser side with <% js code subset %>, Altinity/clickhouse-grafana#186, thanks @fgbogdan * improve alerts query processing for use case when `query(query_name, from, to)` time range is less than visible dashboard time range, see Altinity/clickhouse-grafana#237 * improve alerts json parsing in golang part for case when we have string fields in response which interprets as series name, see Altinity/clickhouse-grafana#230 * properly parsing POST queries in golang part of plugin, Altinity/clickhouse-grafana#228, thanks @it1804 ## Fixes: * fix corner cases for $macro + subquery, see Altinity/clickhouse-grafana#276 and Altinity/clickhouse-grafana#277 * fix parallel query execution, see Altinity/clickhouse-grafana#273 * fix identifiers quotes, see Altinity/clickhouse-grafana#276, Altinity/clickhouse-grafana#277 * fix plugin.json for pass `grafana-plugin-repository` plugin validator * fix multi-value variables behavior - Altinity/clickhouse-grafana#252 * add Vagrantfile for statefull environment and allow to upgrade scenario like grafana 7.1.0 + grafana-cli upgrade-all * fix Altinity/clickhouse-grafana#244 * fix Altinity/clickhouse-grafana#243 * add multiple dashboard examples for github issues: * fix Altinity/clickhouse-grafana#240 * fix Altinity/clickhouse-grafana#135 * fix Altinity/clickhouse-grafana#245 * fix Altinity/clickhouse-grafana#238 * fix Altinity/clickhouse-grafana#232 * fix Altinity/clickhouse-grafana#127 * fix Altinity/clickhouse-grafana#141 Signed-off-by: Eugene Klimov <[email protected]>
My grafana [Grafana v6.6.2 (3fa63cfc34)] clickhouse
(ClickHouse client version 20.3.12.112., ClickHouse server version 20.3.12 revision 54433.) datasource has the following select:
describe [describe (select above) ] of the select looks like this:
As you can see, modem_cnt is of UInt64 type.
For presenting the select I am using official grafana table plugin. In this plugin, modem_cnt column is treated as a string instead of integer (number).
If I look in the output of the Query Inspector, one row looks like this:
As you can see modem_cnt is "12" - string type.
What can I do in order to treat modem_cnt column as number?
I have to present modem_cnt desc, in table but numbers go as 14, 1, 2...
Who is making transformation of the UInt64 to the String?
Is it fault of the clickhouse-grafana data source, or...?
I tried to add a rule:
but modem_cnt is still sorted as sting:
What are my options?
The text was updated successfully, but these errors were encountered: