fixing Complex types in Labels for Logs Details visualization #673
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
adhoc filters from details doesn't work ;(
filters works but got error on clickhouse level doesn't work SELECT *
FROM default.test_logs_with_complex_labels
WHERE (_time >= toDateTime64(1732609375, 3)) AND (_time <= toDateTime64(1732782175, 3)) AND (_map = '{"map_key0":"map_value0"}')
FORMAT JSONworks with different signle quotes serialization SELECT *
FROM default.test_logs_with_complex_labels
WHERE (_time >= toDateTime64(1732609375, 3)) AND (_time <= toDateTime64(1732782175, 3)) AND (_map = '{\'map_key0\':\'map_value0\'}')
FORMAT JSONbut this is clickhouse specific serialization, i don't know how to properly implement it for all clickhouse related invariants |
|
|
|
will fix it as separate issue, i can't propose good solution now ;( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix #672