HBASE CREATE command parsing

  
create 'NewsClickFeedback',{NAME=>'Toutiao',VERSIONS=>3,BLOCKCACHE=>true,BLOOMFILTER=>'ROW',COMPRESSION=>'SNAPPY',TTL => ' 259200 '},{SPLITS => ['1','2','3','4','5','6','7','8','9','a','b','c','d','e','f']}

 

VERSION

  scan 'NewsClickFeedback',{VERSIONS => 2}

 

BLOOMFILTER

value: NONE|ROW|ROWCOL

Function: For get operations and some scan operations, unused storage files can be eliminated, the actual number of IOs can be reduced, and random read performance can be improved.

  
ROW type applies to: get 'NewsClickFeedback', 'rowkey1'
ROWCOL type applies to: get 'NewsClickFeedback','rowkey1',{COLUMN => 'Toutiao'}

 

COMPRESSION

value: Gzip|LZO|Snappy

Snappy has the lowest compression rate, the highest codec rate, and the smallest CPU consumption. It is recommended to use

 

TTL

Data expiration time, the default is permanent storage

 

IN_MEMORY

Whether the data is resident in memory, the default is false

If set to true, the business data will be stored in the same cache area as the HBase Meta metadata. If the business data is too large, the Meta data will be replaced, resulting in decreased cluster performance.

 

BLOCK CACHE

Whether to enable block cache cache, it is enabled by default

 

SPLITS

region pre-allocation strategy

To a certain extent, it solves the performance problems caused by the automatic split of the system caused by the rapid increase of hot application data.

 

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=324907473&siteId=291194637