Replies: 3 comments
|
@mrgleeco |
|
@vyavdoshenko questions can also be posted to Q&A in Github Discussions. I am moving this there |
|
@mrgleeco .Honestly, no not in the “index my whole labels map without thinking about it” way.Hashes are dumb in a good way: you list the fields in the schema, and that’s what gets indexed. Extra keys in the hash that you never mentioned? They’re just sitting there. There’s no secret * in FT.CREATE that means “whatever keys show up, make them all TAGs.” JSON is a bit more flexible because you can sometimes write a path that pulls out several values at once, but they still land in one field you defined. you’re not getting a fresh named field for every random key in the object. For K8s-style labels where every resource has different keys, that’s awkward if you wanted @some-label: to work per key without maintaining a huge schema. People mix up FT.SEARCH using * with “index everything.” That star is about the search, not about auto-discovering hash/json keys at create time. |
Uh oh!
There was an error while loading. Please reload this page.
After some research, it is still not clear if this capability exists or if I am seeking a new feature:
Given a
HASH(or JSON), is it possible to index all its members with a given type?For example a hash that represents labels (eg. Kubernetes labels) where it is string->string
Is this possible today -or ever- with
FT.CREATE? Is there some wildcard magic that one can use?All reactions