scylladb

Files

Pavel Emelyanov e2ec5eecf6 view_update: Do not need storage_proxy

The view_update_generator acceps (and keeps) database and storage_proxy,
the latter is only needed to initialize the view_updating_consumer which,
in turn, only needs it to get database from (to find column family).

This can be relaxed by providing the database from _generator to _consumer
directly, without using the storage_proxy in between.

Signed-off-by: Pavel Emelyanov <xemul@scylladb.com>
Message-Id: <20200207112427.18419-1-xemul@scylladb.com>

2020-02-07 13:30:01 +02:00

build_progress_virtual_reader.hh

treewide: replace reader_resource_tracer with reader_permit

2020-01-28 08:13:16 +02:00

node_view_update_backlog.hh

db/view: Introduce node_update_backlog class

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

row_locking.cc

db: add row locking metrics

2018-05-22 16:52:58 +02:00

row_locking.hh

db: add row locking metrics