...
Each row in the MIGRATE_CHS_CONTENT_TO_JCR table contains the CONTENT_ID, the Status, and the Event Type. It's important that the table be interpreted as existing linearly in time. Any row further down the table is expected to model a content event that occurred after the ones previously. Processing the table rows in order from top to bottom is required.
Status | CodesCode |
|---|---|
Not Started | 0 |
Finished | 1 |
Those are the only two. In the event that add the ability to run this in parallel on multiple cluster nodes, we will certainly have to add more status types.
Event TypesTypes | Description |
|---|---|
ORIGINAL_MIGRATION | This means that is was part of the original table copy |
content.add | This means that it was added to the migration table as the result of receiving a content.add event. |
content.write | Same idea as above for writes |
content.delete | Same idea as above for deletes |
...