This is an automated email from the ASF dual-hosted git repository.
alexey pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git
The following commit(s) were added to refs/heads/master by this push:
new 357dd89f7 KUDU-2671 mark --enable_per_range_hash_schemas as 'advanced'
357dd89f7 is described below
commit 357dd89f7acc645456eea1c46d233f94aaa4e150
Author: Alexey Serbin <ale...@apache.org>
AuthorDate: Sat Jul 2 10:40:03 2022 -0700
KUDU-2671 mark --enable_per_range_hash_schemas as 'advanced'
Since the functionality for KUDU-2671 is almost there, this patch
removes the 'unsafe' tag from the newly introduced
--enable_per_range_hash_schemas flag which enables support for
range-specific hash schemas. Now the flag is marked as 'advanced'
instead and also marked as 'runtime' as well.
Change-Id: Iecfebf908745d279bb7a276806c7c96b363ba8db
Reviewed-on: http://gerrit.cloudera.org:8080/18694
Reviewed-by: Attila Bukor <abu...@apache.org>
Tested-by: Alexey Serbin <ale...@apache.org>
---
src/kudu/master/catalog_manager.cc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/kudu/master/catalog_manager.cc
b/src/kudu/master/catalog_manager.cc
index 2a0d88200..da017d828 100644
--- a/src/kudu/master/catalog_manager.cc
+++ b/src/kudu/master/catalog_manager.cc
@@ -355,7 +355,8 @@ TAG_FLAG(table_locations_cache_capacity_mb, advanced);
DEFINE_bool(enable_per_range_hash_schemas, false,
"Whether the ability to specify different hash schemas per range
is enabled");
-TAG_FLAG(enable_per_range_hash_schemas, unsafe);
+TAG_FLAG(enable_per_range_hash_schemas, advanced);
+TAG_FLAG(enable_per_range_hash_schemas, runtime);
DEFINE_bool(enable_table_write_limit, false,
"Enable the table write limit. "
