What are the Slack Archives?
It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hello guys. One more technical question. As I see you disabled event behavior during default import
Hello guys. One more technical question. As I see you disabled event behavior during default import processes and trigger all events manually. What was the purpose of it? I need also to trigger event in my custom import. Should i trigger it manually? Or can enable event behavior only during my import?
Comments
-
bonjour! the background to disabling it is that in many cases there are a lot of duplicated events that would be fired during import. potentially hundreds of thousands.
0 -
so we disable and accumulate the events and only fire them once, after import
0 -
see
\Spryker\Zed\DataImport\Business\Model\DataImportStep\PublishAwareStep
0 -
i think it could also be possible to activate the behaviour, but @UK9N7MP96 probably has more insight here
0 -
ok. good to know. thank you for inforamtion
0 -
if need be you might have a look here:
0 -
\Spryker\Zed\DataImport\Communication\Plugin\DataImportEventBehaviorPlugin
0 -
ah wait, i was copying the wrong locations above 🤦
0 -
yes yes. I found it already
0 -
thanks
0 -
that one is registered as before hook on most of the importers, e.h. the importer collection
0 -
(fixed the above class names, if someone else should stumble upon this)
0 -
There is also the issue with triggering events related to records that are inside a transaction that is not commited yet… Yhis can lead to issues…
0 -
yes I found this hook during debugging) because I added event behavior to the database table but it didn't work. And found this hook then
0 -
@U010MDPMB3N can you elaborate?
0 -
If we don’t control the flow of the events, they will be sent to RabbitMQ with ids that are not yet saved on the DB. Then, when the workers process them, they will complain because the data was, at that point, not yet commited (pending transaction)
0 -
ah, ok. another reason to accumulate first
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 75 Spryker News
- 924 Developer Corner
- 783 Spryker Development
- 88 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 25 Job Opportunities
- 3.2K 📜 Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random