HBASE-24354 Make it so can make an hbase1 schema and hbase2 schema equate (#1696)
This commit is contained in:
parent
c4e892e3f1
commit
dc360f0f41
|
@ -299,7 +299,11 @@ public class ColumnFamilyDescriptorBuilder {
|
|||
DEFAULT_VALUES.put(CACHE_BLOOMS_ON_WRITE, String.valueOf(DEFAULT_CACHE_BLOOMS_ON_WRITE));
|
||||
DEFAULT_VALUES.put(EVICT_BLOCKS_ON_CLOSE, String.valueOf(DEFAULT_EVICT_BLOCKS_ON_CLOSE));
|
||||
DEFAULT_VALUES.put(PREFETCH_BLOCKS_ON_OPEN, String.valueOf(DEFAULT_PREFETCH_BLOCKS_ON_OPEN));
|
||||
DEFAULT_VALUES.put(NEW_VERSION_BEHAVIOR, String.valueOf(DEFAULT_NEW_VERSION_BEHAVIOR));
|
||||
// Do NOT add this key/value by default. NEW_VERSION_BEHAVIOR is NOT defined in hbase1 so
|
||||
// it is not possible to make an hbase1 HCD the same as an hbase2 HCD and so the replication
|
||||
// compare of schemas will fail. It is OK not adding the below to the initial map because of
|
||||
// fetch of this value, we will check for null and if null will return the default.
|
||||
// DEFAULT_VALUES.put(NEW_VERSION_BEHAVIOR, String.valueOf(DEFAULT_NEW_VERSION_BEHAVIOR));
|
||||
DEFAULT_VALUES.keySet().forEach(s -> RESERVED_KEYWORDS.add(new Bytes(Bytes.toBytes(s))));
|
||||
RESERVED_KEYWORDS.add(new Bytes(Bytes.toBytes(ENCRYPTION)));
|
||||
RESERVED_KEYWORDS.add(new Bytes(Bytes.toBytes(ENCRYPTION_KEY)));
|
||||
|
|
Loading…
Reference in New Issue