- First commit to issue fork.
- Merge request !70Draft: Skipped rows are processed continuously at each batch iteration → (Open) created by Duwid
It seems like there's some problem in the way MigrateBatchExecutable handles skipped rows.
Since there's no way the MigrateBatchExecutable (or even core MigrateExecutable) could distinguish between rows skipped during this run and those skipped previously, each batch iteration retries importing skipped rows, leading to increased processing time as batch runs.
Also as a side-effect, this may lead to incomplete migrations (e.g. in case of batch-based migrations, like CSV import running from UI) since the batch would count skipped rows multiple times.
Execute the migration using skip_on_empty, attach with debugger. Observe that skip_on_empty transform() method is being called for first skipped row at each batch process.
Patch attached.
None.
None.
None.
None.
Needs work
6.0
Code
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.