From 697e2fc66dcac8dfb076097655a91e8c4e5e2fb5 Mon Sep 17 00:00:00 2001 From: Piotr Sarna Date: Thu, 15 Jul 2021 14:09:37 +0200 Subject: [PATCH] db,view: drop the artificial limit on view update mutation size The series which split the view update process into smaller parts accidentally put an artificial 10MB limit on the generated mutation size, which is wrong - this limit is configurable for users, and, what's more important, this data was already validated when it was inserted into the base table. Thus, the limit is lifted. Tests: unit(release), dtest(wide_rows_test) --- db/view/view.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/db/view/view.cc b/db/view/view.cc index a1357915ad..c84be13430 100644 --- a/db/view/view.cc +++ b/db/view/view.cc @@ -409,7 +409,7 @@ private: public: data_query_result_builder(const schema& s, const query::partition_slice& slice) - : _res_builder(slice, query::result_options::only_result(), query::result_memory_accounter{10*1024*1024}) + : _res_builder(slice, query::result_options::only_result(), query::result_memory_accounter{query::result_memory_limiter::unlimited_result_size}) , _builder(s, _res_builder) { } void consume_new_partition(const dht::decorated_key& dk) { _builder.consume_new_partition(dk); }