By default, Maestro builds the Elasticsearch index based on a pre-defined default index mapping. The name of this default mapping gets set in the .env.maestro
environment variable file.
While this mapping is not configurable in runtime, there may be cases where an administrator will need to change the mapping.
For example, when updating Songs' dynamic schemas the administrator must also update Maestros' index mapping.
Guidelines for index migration are outlined here:
Update the existing index mapping to account for the new analysis types and fields.
Re-index the data. Trigger indexing by updating the .env.maestro
environment file with the new index mapping or index via the Elasticsearch API.
Update your Elasticsearch aliases to point to the new or updated index instead of the old one.
Following these steps, the data will be migrated and Maestro will now index based on the new mapping.