Skip to content

Support batches processing for media gallery synchronization queue messages #29543

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

yolouiese
Copy link
Contributor

@yolouiese yolouiese commented Aug 14, 2020

Description (*)

Added an implementation to support batch processing for synchronization queue messages

Related Pull Requests

https://github.com/magento/partners-magento2-infrastructure/pull/36

Fixed Issues (if relevant)

  1. Fixes Support batches processing for synchronization queue messages adobe-stock-integration#1724: Support batches processing for synchronization queue messages

Manual testing scenarios (*)

Check synchronization when enabling new media gallery
Check bin/magento media-gallery:sync functionality
Check bin/magento media-content:sync functionality

General synchronization test case:

  1. Upload a couple of images or save images from Adobe Stock
  2. Add/insert images to either category, product, cms pages or blocks
  3. Delete rows from tables media_gallery_asset and media_content_asset
  4. Disable Enhanced Media Gallery and save configuration (Assuming it is already enabled)
  5. Enable Enhanced Media Gallery and save configuration (Changes in the system configuration for the Enhanced Media Gallery triggers the Media Gallery and Media Content sychronization publishers)
  6. Run bin/magento queue:consumers:start media.gallery.synchronization
  7. Open Media Gallery and ensure the images are present in the grid. (Check media_gallery_asset table if data are saved)
  8. Run bin/magento queue:consumers:start media.content.synchronization
  9. View details of the images in the media gallery and ensure the Used In information is correct. (Check media_content_asset table if data are saved)

Batch synchronization test case:

  1. Upload a couple of images or save images from Adobe Stock
  2. Add/insert these images to either category, product, cms pages or blocks
  3. Delete rows from tables media_gallery_asset and media_content_asset
  4. Call the \Magento\MediaGallerySynchronization\Model\Publish::execute passing the paths of the images
  5. Run bin/magento queue:consumers:start media.gallery.synchronization
  6. Open Media Gallery and ensure the images are present in the grid. (Check media_gallery_asset table if data are saved)
  7. Call the \Magento\MediaContentSynchronization\Model\Publish::execute passing the contentIdentities of the places where the images have been added to
  8. Run bin/magento queue:consumers:start media.content.synchronization
  9. View details of the images in the media gallery and ensure the Used In information is correct. (Check media_content_asset table if data are saved)

Questions or comments

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)
  • All automated tests passed successfully (all builds are green)

…ssages - updated synchronization consumer and added media content bulk service
@yolouiese yolouiese requested a review from sivaschenko August 14, 2020 13:01
@m2-assistant
Copy link

m2-assistant bot commented Aug 14, 2020

Hi @yolouiese. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@tanghongtanghong
Copy link

hi,hello

…synchronization queue messages - implemented gallery synchronization functionality
@sivaschenko sivaschenko added Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Aug 19, 2020
…synchronization queue messages - implemented media content sychronization
@yolouiese
Copy link
Contributor Author

@magento run all tests

@yolouiese
Copy link
Contributor Author

@magento run all tests

…synchronization queue messages - added media content sychronizer and save contents to database
@yolouiese
Copy link
Contributor Author

@magento run all tests

…synchronization queue messages - added method to sync and save media content to database
@yolouiese
Copy link
Contributor Author

@magento run all tests

…synchronization queue messages - fixed failed static test
@yolouiese
Copy link
Contributor Author

@magento run all tests

@sivaschenko sivaschenko self-assigned this Aug 24, 2020
@yolouiese
Copy link
Contributor Author

@magento run all tests

@sivaschenko sivaschenko added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Sep 6, 2020
@sivaschenko
Copy link
Member

@magento run all tests

);
}

$this->setLastExecutionTime();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The falg should be set only after full synchronization, not after partial

}

$this->setLastExecutionTime();
$this->removeObsoleteContent->execute();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RemoveObsoleteContentAsset is a part of full synchronization, shouldn't be a part of partial

/**
* @inheritDoc
*/
public function execute(array $mediaContentIdentities): void
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to check that the content links are removed if the entity is no longer present (was deleted)

@sivaschenko
Copy link
Member

@magento run all tests

@magento-engcom-team
Copy link
Contributor

Hi @sivaschenko, thank you for the review.
ENGCOM-8146 has been created to process this Pull Request

@sivaschenko
Copy link
Member

@magento run Integration Tests

@sivaschenko
Copy link
Member

@magento run all tests

@m2-assistant
Copy link

m2-assistant bot commented Sep 11, 2020

Hi @yolouiese, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Component: MediaContentSynchronization Component: MediaContentSynchronizationApi Component: MediaContentSynchronizationCatalog Component: MediaContentSynchronizationCms Component: MediaGallerySynchronization Priority: P3 May be fixed according to the position in the backlog. Progress: accept Project: ASI QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Support batches processing for synchronization queue messages
5 participants