Implement FT.ALIASADD, FT.ALIASUPDATE, and FT.ALIASDEL

[vyavdoshenko]

Alias management commands (FT.ALIASADD, FT.ALIASUPDATE, FT.ALIASDEL) allow users to assign stable, human-readable names to existing indexes.

Expected behavior:

FT.ALIASADD

• Creates a new alias for the specified index.
• Returns an error if the alias already exists.

FT.ALIASUPDATE

• Adds or updates an alias to point to a new index.
• If the alias doesn’t exist, it is created.
• If it exists, it’s updated atomically to point to the new index.

FT.ALIASDEL

• Deletes an existing alias without removing the underlying index.

[romange]

Is not it a deprecated feature? Why do we need it? Roman Gershman CTO --- *www.dragonflydb.io <http://www.dragonflydb.io>*

…

On Fri, Oct 24, 2025, 4:57 PM Volodymyr Yavdoshenko < ***@***.***> wrote: *vyavdoshenko* created an issue (dragonflydb/dragonfly#5962) <#5962> Alias management commands (FT.ALIASADD, FT.ALIASUPDATE, FT.ALIASDEL) allow users to assign stable, human-readable names to existing indexes. Expected behavior: FT.ALIASADD - Creates a new alias for the specified index. - Returns an error if the alias already exists. FT.ALIASUPDATE - Adds or updates an alias to point to a new index. - If the alias doesn’t exist, it is created. - If it exists, it’s updated atomically to point to the new index. FT.ALIASDEL - Deletes an existing alias without removing the underlying index. — Reply to this email directly, view it on GitHub <#5962>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4BFCGDDIURBJS7WWE5QPT3ZIV23AVCNFSM6AAAAACKDZG5CKVHI2DSMVQWIX3LMV43ASLTON2WKOZTGU2DSNRTG43DEMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[vyavdoshenko]

Is not it a deprecated feature?

Is not it a deprecated feature? Why do we need it?

This is the actual API. I think this feature can be marked as a low-priority feature. This issue opened after my RLTest investigation.