Description
A recent sit-down with a customer highlighted the desire to include the key names (meta().id) when looking for commonality across flavors.
A simple description of the use case:
A few different flavors of documents in a bucket, and using a key-name prefix to identify each one:
- "user::<user_name>" for user profile documents
- "order::<order_id>" for order documents
- etc
Now, in the document editor, I just see a long list of these and I might want to filter down to a particular type using the key name...let's assume I just have a primary index so can't actually do a reasonably timed query on type or other embedded field.
If the INFER output (and therefore the QWB insights) showed me that one flavor of document all shared a common key prefix ("user::xxx") then I could use that to understand my key naming scheme.