Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Even if I only have ~4000 nodes with nodeword data to migrate, it still creates batche operations consisting of all 20,000 of my nodes where it does nothing for most of them.
Rather than selecting every nid in the node table, we should just select nids for nodes that have data in nodewords.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | metatags_quick-slow_migration-1532666-3.patch | 443 bytes | iamEAP |
| #1 | metatags_quick-slow_migration-1532666-1.patch | 1.59 KB | iamEAP |
| metatags_quick-slow_migration-0-0.patch | 1.4 KB | iamEAP |
Comments
Comment #1
iamEAP CreditAttribution: iamEAP commentedMistakes in my understanding of the DB API.
Comment #2
iamEAP CreditAttribution: iamEAP commentedNevermind, this actually doesn't appear to be solving anything.
Comment #3
iamEAP CreditAttribution: iamEAP commentedAh, the real problem was in the node_save(). Very expensive; it's better to just save the fields attached to it.
The above work may still be relevant, but this patch is a significant improvement.
Sorry for all the noise as I work through this.
Comment #4
valthebaldI think this approach completely makes sense.
Committed to 7.x-2.x-dev, thank you!