-
Notifications
You must be signed in to change notification settings - Fork 69
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
Can't visualise db data with spaces in JSON Object fields on grafana. #620
Comments
@mallikarjun-12 Hey there! I'm looking into reproducing this on my side currently. Would you be able to confirm the exact schema of the table you're trying to read from ( |
Hey @mallikarjun-12! Is this still an issue? If it is, can you provide us with more information (listed in the comment above)? Thanks! |
Hi @mallikarjun-12, are you able to confirm if this is still an issue? Reading the ClickHouse docs I can see that this type is obsolete. Does the |
Hey @adamyeats I have encountered this exact same issue today. Follow the steps below for replication -
|
Thank you for the update @siva-vunet, have you also attempted a similar test with the @SpencerTorres are you able to chime in here? It seems this may be related to how ClickHouse handles JSON rather than something specific to Grafana. |
Yes I have tried this with the |
I believe the map type is preferred for now if that works for you. ClickHouse docs say the JSON field is experimental and obsolete. |
What happened:
When using the ClickHouse plugin in Grafana to retrieve data from a ClickHouse database, I have encountered issues when dealing with JSON data that contains fields with spaces. The sample JSON data provided is as follows:
Query:
SELECT "log", "level", "timestamp" FROM "default"."logs" LIMIT 10;
Error Field:
error string
Error:
error querying the database: clickhouse: unsupported column type "string String"
What you expected to happen:
Visualise data even if the JSON fields have spaces.
How to reproduce it (as minimally and precisely as possible):
Screenshots
Environment:
The text was updated successfully, but these errors were encountered: