Allen Samuels

This is an overview of the list of core extensions that the search module would like to see. There are sub-issues for each one. * Completion of Multi/Exec notification. https://github.com/valkey-io/valkey/issues/2415...

[NEW] New Command field classification.

2

**The problem/use-case that the feature addresses** Modern Valkey clients use the information returned by the "COMMAND INFO" command to determine how to handle the fields of a command. In particular,...

[NEW] Provide Notification on Key Load

3

**The problem/use-case that the feature addresses** Today, loading an RDB with defined indexes is done sequentially in two stages. In the first stage, the Valkey databases (keys) are restored. In...

**The problem/use-case that the feature addresses** For modules like Search that have data that is related to key data (e.g., search indexes), when a slot migration happens there is not...

[NEW] Server event on cluster topology change

2

**The problem/use-case that the feature addresses** Each search query operation must be fanned out to each shard (selecting from primary/replica accordingly). This requires processing of the entire cluster map, which...

**The problem/use-case that the feature addresses** A module can determine that a multi/exec has started by checking for the multi/exec flag on each mutative keyspace notification. However, there is no...

**The problem/use-case that the feature addresses** Currently, the Search module performs an ACL check for each FT.SEARCH and FT.AGGREGATE. Currently this is implemented as a VM_Call to fetch the ACL...