Remove lft field from archival descriptions ES index
|Target version:||Release 2.6.0|
|Google Code Legacy ID:||Tested version:||2.5, 2.6|
The lft field on the QubitInformationObject ES index is not used and it's hard to keep it in sync with the database when there is no need.
Additionally, avoid its use to obtain the ordered ancestors while indexing, as it may lead to wrong values (CSV import without nested set update) and we can use CTE to recursively obtain the ancestors.
#3 Updated by José Raddaoui Marín almost 2 years ago
- Status changed from Code Review to QA/Review
Merged in qa/2.6.x.
For testing, we need to verify the IO ancestor ids are properly indexed and the the lft field has been removed. #13291 added a new task to easily get the indexed document by a resource's slug, which may be useful for this tests.