Initializing the record transformer before the loop

[DmitryFurs]

Description

When migrating data in the EAV Step, the record transformer instance is initialized inside the records loop. This leads to the fact that for each record transformer, new instances of handlers are initialized. Since some handlers make a query to the db and store the result in their properties, it turns out that each new handler instance will execute this query.

A similar issue is present in the Tier Price Step, only the record transformer is initialized inside the pages loop.

Manual testing scenarios

1. Add breakpoint at \Migration\Handler\EavAttribute\ApplyTo::checkIfUserDefined() this handler will transform catalog_eav_attribute.apply_to field
2. Run migrating of the EAV Step
3. Catch multiple duplicate unnecessary queries to the db per table transformation

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)

[victor-v-rad]

Hi @DmitryFurs

Thank you for your contribution to the project! Internal ticket MC-30836 to process the PR

[ghost]

Hi @DmitryFurs, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.