Fix filter for Map type LogLabels #1456
Open
+76
−14
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 filter not working when adding via + button in Explore logs
#1369 introduced OTel attribute support but broke existing Map/JSON type filter logic.
Problem 1: Empty mapKey
When clicking + button on a log field from a Map type column (e.g., LogAttributes as labels) in Explore, the filter was created with an empty key.
labels['key'] = 'value'labels = 'value'Fix: Fallback to columnName when mapKey is not set by OTel prefix parsing.
Problem 2: Empty columnType
When OTel mode is enabled, columns were set without type information, causing Map columns to be incorrectly treated as JSON.
labels['key'] = 'value'(Map syntax)labels.`key` = 'value'(JSON syntax)Fix: Fetch column type from table schema in
useOtelColumns.Related: #1369 (comment)