Reasoning for content events initialization

[karolberezicki]

Hi,

The content events are currently initialized in IndexingJobService in the method InitContentEvent after the IndexAllOnce.
However, once the application is restarted / redeployed, the content events will be lost unless we'll reindex the whole site again, and for bigger sites it may take couple of hours.
I'm wondering if there's any particular reason why the content events are not initialized during the application startup, but rather in the reindexing job?

[lunchin]

Not sure why was done like this. We can try to move to application startup and see if works fine.

[karolberezicki]

I'll try it and create another PR if it proves to be working good.

[ellinge]

We had our luck reverting these changes (init of events in job and indexing directly in job), more details in #29