Replies: 1 comment
-
Nevermind: false alarm: it turns out that it does already work if you use the syntax |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I originally posted this as a feature request (#5146), but it hasn't received any comments, so I'm posting it here as a question (apologies if I'm breaking any rules in the process!):
I am storing unique tags in my payload as the keys of a dict (metadata.tags), rather than a list, because that enables me to append a new tag idempotently to multiple points at once:
which is very clean and efficient. And I can query them with:
which also works great. However, a problem arises when my tags include legal (JSON) characters such as "/", because the "foo.bar.baz" key syntax breaks when you include certain characters in a naked key like that. For instance:
generates a parsing error, even though "tag-with/slash" is a JSON dict key.
I would like to be able specify my key in such a way that non-compatible (but JSON-legal) characters can be escaped. For instance:
which would echo jq's alternate query syntax. But I'd be happy with any solution.
Beta Was this translation helpful? Give feedback.
All reactions