Piotr Sarna b06e9447b1 view: fix use-after-move when handling view update failures ...

The code was susceptible to use-after-move if both local
and remote updates were going to be sent.
The whole routine for sending view updates is now rewritten
to avoid use-after-move.

Refs #8830
Tests: unit(release),
       dtest(secondary_indexes_test.py:TestSecondaryIndexes.test_remove_node_during_index_build)

(cherry picked from commit 8a049c9116)

2021-06-16 13:40:57 +02:00

..

build_progress_virtual_reader.hh

mutation_fragment: add schema and permit

2020-09-28 11:27:23 +03:00

node_view_update_backlog.hh

db/view: Introduce node_update_backlog class

2018-12-19 22:38:30 +00:00

row_locking.cc

code: Force formatting of pointer in .debug and .trace

2020-08-26 20:44:11 +03:00

row_locking.hh

row_locking: change estimated histogram with time_estimated_histogram

2020-07-14 11:17:43 +03:00

view_builder.hh

Revert "Revert "Merge "raft: fix replication if existing log on leader" from Gleb""

2020-12-08 19:19:55 +02:00

view_stats.hh

materialized views: reduce recompilation when db/view/view.hh changes.

2020-03-19 15:46:14 +02:00

view_update_backlog.hh

db/view: Add view_update_backlog

2018-12-19 22:38:30 +00:00

view_update_checks.hh

streaming,view: move view update checks to separate file

2019-01-03 08:31:40 +01:00

view_update_generator.cc

Revert "Revert "Merge "raft: fix replication if existing log on leader" from Gleb""

2020-12-08 19:19:55 +02:00

view_update_generator.hh

db, view: add view update generator metrics

2020-08-11 17:43:53 +02:00

view_updating_consumer.hh

mutation_fragment: add schema and permit

2020-09-28 11:27:23 +03:00

view.cc

view: fix use-after-move when handling view update failures

2021-06-16 13:40:57 +02:00

view.hh

db,view: pass base token by value to mutate_MV

2021-06-16 13:38:01 +02:00