Design/Proposals for Search Index Creation/Maintenance/Migrations

[bsbodden]

• Spring configuration for Index Creation and output of Indices text for DevOps purposes
• Maven and Gradle tasks to output the current list of indices and Redis Search command

[joedickeyredis]

Maybe there could be a mechanism for assigning an alias when index is created initially so that when changes are made to the schema, a new index is created with incremented version number, alias points to new index, old index is dropped? To the end user they only ever access through the alias.

Something like:

1. User creates initial index: FT.CREATE myindex_v1 ... FT.ALIASADD myindex myindex_v1
2. Any change is made to schema: FT.CREATE myindex_v2 ... FT.ALIASUPDATE myindex myindex_v2 FT.DROPINDEX myindex_v1

End user only accesses index through alias, myindex. Would need to evaluate performance impact if lots of updates are being made in short amount of time

11:52 Could have performance impact if lots of changes are made close together