arElasticSearchInformationObjectPdo exception when parentId is not found in keymap during CSV updates
|Target version:||Release 2.4.0|
|Google Code Legacy ID:||Tested version:|
I somewhat suspect this is actually a bug that's been around since the original --update. At any rate, to reproduce:
Run a csv:import with --update='match-and-update', have one row in the csv file that refers to a parentId that doesn't exist.
Result: after the "For legacyId 999 Could not find parentId 1234 in key_map table" error, we then get an exception:
arElasticSearchInformationObjectPdo: Couldn't find ancestors, please make sure lft and rgt values are correct
#2 Updated by Mike Gale over 5 years ago
I'm going to bundle it into a single PR with https://github.com/artefactual/atom/tree/dev/issue-10150-update-fixes soon so we don't have to do several code reviews separately for each issue.
#3 Updated by Mike Gale over 5 years ago
- Status changed from New to QA/Review
- Assignee changed from Mike Gale to Dan Gillean
this is related to 9775 and can be verified when 9775 is good to go I think, sorry for the separate ticket but the problem was in some code that I didn't touch for these features, it just showed up in this case.