Inconsistent handling of dots in field names by json_parser #2814
Labels
domain: data model
Anything related to Vector's internal data model
domain: logs
Anything related to Vector's log events
have: must
We must have this feature, it is critical to the project's success. It is high priority.
type: bug
A code related bug.
When the
json_parser
transform unpacks JSON with dots in a key name, then it handles field names containing dots inconsistently, e.g. see the below config/setup/output. I'm working around this for now but hope it can be fixed & isn't a designed-in ambiguity...When you run v0.9.2 vector (on Linux FWIW) with the below input file.
... you get the below result (pretty printed for clarity), noting "field.with.dots" is now a three-level hierarchy not a string:
If you uncomment the target_field to make sure it's always not-inserting-at-root then the problem disappears.
The text was updated successfully, but these errors were encountered: