Forum Discussion
Currently, in order to use the [?(...)]
syntax in a JSON-Path, the previous part of the path needs to refer to an array or object. (Although I feel like your attempt makes sense and should have worked.)
To delete a property from an object, you need to filter the object and test for the property name and value, like so:
$[?(key == 'id' && value == null)]
Thank you! That’s what I was hoping wasn’t the case. I opened a Support ticket for it and another issue I’m having filtering an array as documented.
- bilesh_ganguly5 years agoNew Contributor II
Thank you for your response Spiro.
I’m aware of metadata snaps; I was looking for a solution that doesn’t involve creating a pipeline.
- ptaylor5 years agoEmployee
@bilesh.ganguly Did you see my reply above? The Snap Statistics feature doesn’t require creating a pipeline.
- bilesh_ganguly5 years agoNew Contributor II
- PeterRNLI3 years agoNew Contributor II
How, the metadat Snaps do not include SNAP, only SNAP PACK
- SpiroTaleski3 years agoValued Contributor
I don’t have that details why SNAP is not included.
But, if you read a PIPELINE, the metadata that will be returned will contains details about each SNAP within that pipeline.
BR,
Spiro Taleski- PeterRNLI3 years agoNew Contributor II
All very well, but only class and instance information available. Names seem to be derived from the Instance Id. Instance metadata not being available from the Meta Snaps!