Task #13356

Remove lft field from archival descriptions ES index

Added by José Raddaoui Marín 4 months ago. Updated 4 months ago.

Status:VerifiedStart date:06/15/2020
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Information object
Target version:Release 2.6.0
Google Code Legacy ID: Tested version:2.5, 2.6
Sponsored:No Requires documentation:No

Description

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.

History

#1 Updated by José Raddaoui Marín 4 months ago

  • Tracker changed from Bug to Task

#2 Updated by José Raddaoui Marín 4 months ago

  • Status changed from New to Code Review
  • Target version set to Release 2.6.0

#3 Updated by José Raddaoui Marín 4 months 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.

#4 Updated by Dan Gillean 4 months ago

  • Status changed from QA/Review to Verified
  • Requires documentation set to No

Looks good! Did not see lft in the index output, and checked the parentID listed for a child record using SQL and the slug.

Also available in: Atom PDF