So with RediSearch 1.x we’ve always manually created our index and manually added documents to it. What was indexed wasn’t a hash table, but simply bits of information stored in the redis key value (simple string value). This would be like storing a person’s name from the person key who has visited certain cities. I’m sure I’m not explaining this correctly, but if I understand correctly Redis 2.0 doesn’t allow this.
This also meant our index didn’t have any relationship to one specific key. With 2.0 it tries to create a hash with the detail provided. So if we wanted to do the same, we’d have to structure our data like:
cities:los_angeles:visited:frank (or something). Point being, we can’t just create an index and populate it manually. Am I understanding that correctly? I know I’m saying this poorly, but we’re looking to functionally create indexes based on related keys (similar to a join) and store that index as something other than the keys that it’s indexing.