FT.ALIASADD, FT.ALIASDEL, FT.ALIASUPDATE Implementation Proposal

[jonathanc-n]

Overview

These commands are used to add, delete and update alias (names which can substitute keys).

I'm thinking to store a table for all the Aliases in IndexManager. Here are some of the features:

• Add, Delete, Update function for table.
• Two way mapping for index lookups and alias reverse lookups for deletion and such.
• Get function for alias->index.
• DeleteByIndexName function.

Metadata

The specifics stored in search_encoding.h:

Can use perfect hashing to create 64 bit values to make lesser memory overhead. Due to alias being made one at a time, there will be limited time overhead from hashing.

Alias table
| Hashed Alias Name (64 bits) | Index Name (32 bytes) |

Index table
| Hashed Index Name (64 bits) | Alias Name/Array (32 bytes +) | - this is due to multiple alias mapped to same index

• if strings are too big I can possibly store them as German-styled strings (would need to figure out how to implement this into current architecture though).

Not sure whether to store both maps as pair values, using encoding/decoding, or to operate on them as slices on storage. What are your thoughts for this?

[jonathanc-n]

Is someone able to take a look at this?