Project

Profile

Help

Issue #8044

closed

no index for _last_updated on content models causes a fatal error when ordered result is queried

Added by ttereshc over 3 years ago. Updated about 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
2.21.5
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 88
Quarter:

Description

To ensure data correctness, Migration plugin requires fetching content in ordered way. For this _last_updated field is used.

Without index, the query ordered by that field fails due to lack of memory and complains that no index is present.


Related issues

Related to Migration Plugin - Issue #7781: In case of any issues in the middle of pre-migration, migration re-run doesn't pick up all the needed content.CLOSED - CURRENTRELEASEggaineyActions

Also available in: Atom PDF