d0b02dc0d0
Currently when a partition is deleted from the base table, we generate a row tombstone update for each one of the view rows in the partition. When the partition key in the view is the same as the base, maybe in a different order, this can be done more efficiently - The whole corresponding view partition can be deleted with one partition tombstone update. With this commit, when generating view updates, if the update mutation has a partition tombstone then for the views which have the same partition key we will generate a partition tombstone update, and skip the individual row tombstone updates. Fixes scylladb/scylladb#8199
93 lines
3.2 KiB
C++
93 lines
3.2 KiB
C++
/*
|
|
* Copyright (C) 2017-present ScyllaDB
|
|
*/
|
|
|
|
/*
|
|
* SPDX-License-Identifier: AGPL-3.0-or-later
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include "query-request.hh"
|
|
#include "schema/schema_fwd.hh"
|
|
#include "db/view/view.hh"
|
|
|
|
namespace cql3::statements {
|
|
class select_statement;
|
|
}
|
|
|
|
class view_info final {
|
|
const schema& _schema;
|
|
raw_view_info _raw;
|
|
// The following fields are used to select base table rows.
|
|
mutable shared_ptr<cql3::statements::select_statement> _select_statement;
|
|
mutable std::optional<query::partition_slice> _partition_slice;
|
|
db::view::base_info_ptr _base_info;
|
|
mutable bool _has_computed_column_depending_on_base_non_primary_key;
|
|
|
|
// True if the partition key columns of the view are the same as the
|
|
// partition key columns of the base, maybe in a different order.
|
|
mutable bool _is_partition_key_permutation_of_base_partition_key;
|
|
public:
|
|
view_info(const schema& schema, const raw_view_info& raw_view_info);
|
|
|
|
const raw_view_info& raw() const {
|
|
return _raw;
|
|
}
|
|
|
|
const table_id& base_id() const {
|
|
return _raw.base_id();
|
|
}
|
|
|
|
const sstring& base_name() const {
|
|
return _raw.base_name();
|
|
}
|
|
|
|
bool include_all_columns() const {
|
|
return _raw.include_all_columns();
|
|
}
|
|
|
|
const sstring& where_clause() const {
|
|
return _raw.where_clause();
|
|
}
|
|
|
|
cql3::statements::select_statement& select_statement(data_dictionary::database) const;
|
|
const query::partition_slice& partition_slice(data_dictionary::database) const;
|
|
const column_definition* view_column(const schema& base, column_kind kind, column_id base_id) const;
|
|
const column_definition* view_column(const column_definition& base_def) const;
|
|
bool has_base_non_pk_columns_in_view_pk() const;
|
|
bool has_computed_column_depending_on_base_non_primary_key() const {
|
|
return _has_computed_column_depending_on_base_non_primary_key;
|
|
}
|
|
|
|
bool is_partition_key_permutation_of_base_partition_key() const {
|
|
return _is_partition_key_permutation_of_base_partition_key;
|
|
}
|
|
|
|
/// Returns a pointer to the base_dependent_view_info which matches the current
|
|
/// schema of the base table.
|
|
///
|
|
/// base_dependent_view_info lives separately from the view schema.
|
|
/// It can change without the view schema changing its value.
|
|
/// This pointer is updated on base table schema changes as long as this view_info
|
|
/// corresponds to the current schema of the view. After that the pointer stops tracking
|
|
/// the base table schema.
|
|
///
|
|
/// The snapshot of both the view schema and base_dependent_view_info is represented
|
|
/// by view_and_base. See with_base_info_snapshot().
|
|
const db::view::base_info_ptr& base_info() const { return _base_info; }
|
|
void set_base_info(db::view::base_info_ptr);
|
|
db::view::base_info_ptr make_base_dependent_view_info(const schema& base_schema) const;
|
|
|
|
friend bool operator==(const view_info& x, const view_info& y) {
|
|
return x._raw == y._raw;
|
|
}
|
|
friend fmt::formatter<view_info>;
|
|
};
|
|
|
|
template <> struct fmt::formatter<view_info> : fmt::formatter<string_view> {
|
|
auto format(const view_info& view, fmt::format_context& ctx) const {
|
|
return fmt::format_to(ctx.out(), "{}", view._raw);
|
|
}
|
|
};
|