Vector Remap Error: Parent Path Segment Rejects Mutation When Using del(.)

[Anton0C]

I have the following configuration:

First remap:

. = merge!(., parse_json(.message))

Second remap(in a deeper location):

event_data = del(.)
meta_data = %my_source

# Now, try to form a new object with only the required properties:
.log.level = "info"
.some.property = event_data.some.property 

But got error:

"parent path segment rejects this mutation"
"querying a field of a non-object type is unsupported"

This issue is related to:

This change was made to prevent accidentally overwriting non-collection types. As the diagnostic message suggests, you can still achieve the desired result by first re-writing the non-collection type to a collection type (foo = {}), and then mutating the collection itself.
https://vector.dev/highlights/2022-08-16-0-24-0-upgrade-guide/

⚠️ Without del(.), it works as expected; however, in my case I do not need everything inside .
It would nice to have the ability to restore . (root) object after del(.)

[pront]

Hi @Anton0C, check out this example. It restores the previous . inside a new ., if this is what you are after.

P.S. There are few open issues around del, probably you are interested in this one #48

[Anton0C]

I would like to do the following:

del(.)
.a.b.c.d.e.f = "info"

instead of:

del(.)
.a={}
.a.b={}
.a.b.c={}
.a.b.c.d={}
.a.b.c.d.e={}
.a.b.c.d.e.f = "info"

This is because I have multiple deep children (for example, see [this CSV])
Removing the incoming “root object” with del(.) leaves me unable to restore it with the same properties.

⚠️ Without del(.), it works as expected:

# some code
# ...
.a.b.c.d.e.f = "info"

[pront]

Gotcha, thanks for the example. Unfortunately, this is what you have to do for now. We can definitely try to improve del in the future.