New default 'complete node migration' migrates all revisions including translations

A new node migration, d*_node_complete.yml, referred to as the 'complete node migration', now exists that will migrate all nodes, the node revisions, including translated nodes and the translated node revisions. The complete node migration will eventually replace the existing trio of node migrations, d*_node, d*_node_revision and d*_node_translation, now collectively referred to as the classic node migrations.

When using the core migrate UI, /upgrade, the d*_node_complete migration is the default. The classic node migrations are completely removed from the list of migrations that are run. It will be used for all new migrations.

The classic node migrations are not deprecated. Both exist in core and other migrations that depend on the node migrations are modified at run time to work with both the classic node migration and the complete node migration.

Changed migrations

There are several migrations that are modified so that the complete migration can use the same migrations as the classic node migration. The changes are to any process pipeline that uses a migration_lookup process plugin with a classic node migration as the migration lookup source.

The migrations changed are: d6_term_node, d6_term_node_revision, d6_term_node_translation, d6_comment, d6_url_alias,d7_comment, d7_url_alias, statistics_node_counter and node_translation_menu_links.

Migration dependencies altered

When the new complete node migration is in use any migration which has dependencies on a the classic node migrations is altered to change those dependencies to complete node migrations.

These alterations are done in migrate_drupal.module, via hook_migrations_plugin_alter(), when the complete node migration is in use.

Incremental migrations

The classic node migrations will run if, and only if, the new site has classic node migration map tables with rows. If you have run an upgrade, /upgrade, prior to this change then migrate_map node tables will have data. So that when an incremental is run from /upgrade the classic node migration will run.

Drush

When using drush to run migration both the classic and complete migrations are available.

Before

These migrations are now referred to as the classic node migrations.

After

There is one node migration referred to as the complete node migration.

Defaulting to the classic migrations

If you are developing custom migrations that depend on the classic migrations and you don't want to change them to use the new complete node migration then you can override the default using settings.php. Add the following line to default to classic migrations.

$settings['migrate_node_migrate_type_classic'] = TRUE;