push
github
applier: drop apply_final_join_tx Can use the regular applier_apply_tx(), they do the same. The latter is just more protective, but doesn't matter much in this case if the code does a few latch locks. The patch also drops an old test about double-received row panic during final join. The logic is that absolutely the same situation could happen during subscribe, but it was always filtered out by checking replicaset.applier.vclock and skipping duplicate rows. There doesn't seem to be a reason why final join must be any different. It is, after all, same subscribe logic but the received rows go into replica's initial snapshot instead of xlogs. Now it even uses the same txn processing function applier_apply_tx(). The patch also moves `replication_skip_conflict` option setting after bootstrap is finished. In theory, final join could deliver a conflicting row and it must not be ignored. The problem is that it can't be reproduced anyhow without illegal error injection (which would corrupt something in an unrealistic way). But lets anyway move it below bootstrap for clarity. Follow-up #10113 NO_DOC=refactoring NO_CHANGELOG=refactoring (cherry picked from commit da158b9bf)
62739 of 114028 branches covered (55.02%)
17 of 22 new or added lines in 2 files covered. (77.27%)
539 existing lines in 14 files now uncovered.93662 of 109120 relevant lines covered (85.83%)
2588479.15 hits per line