Changing a Migration's group unregisters the migration and causes all data for the migration to be wiped if/when it gets re-registered. This seems like a bug, since the group is more or less an organizational decoration, not actually important information about the Migration.

Comments

mikeryan’s picture

Status: Active » Postponed (maintainer needs more info)

Can you describe exactly what you did when changed the group (I assume you mean the group name), and what exactly happened? I tried this using migrate_example - I changed the wine group's name to wine2 in migrate_example.migrate.inc, reregistered, and everything worked fine.

Note that groups are more than just a name, you can assign arguments to a group that will be applied to all migrations within the group.

mikeryan’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)