[ 
https://issues.apache.org/jira/browse/HBASE-10752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942020#comment-13942020
 ] 

Ted Yu commented on HBASE-10752:
--------------------------------

Thanks for the reminder, Andy.
I pasted wrong segment of console - here is the correct one where syntax error 
was fixed:
{code}
hbase(main):002:0> alter 'testtable', {NAME => 'cf1', DATA_BLOCK_ENCODING => 
'FAST_DIFF'}
Updating all regions with the new schema...
0/1 regions updated.
1/1 regions updated.
Done.
0 row(s) in 2.3960 seconds

hbase(main):003:0> describe 'testtable'
DESCRIPTION                                                                     
                                ENABLED
 'testtable', {NAME => 'cf1', DATA_BLOCK_ENCODING => 'FAST_DIFF', BLOOMFILTER 
=> 'ROW', REPLICATION_SCOPE => '0 true
 ', VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIONS => '0', TTL => 
'2147483647', KEEP_DELETED_CELLS => 'fa
 lse', BLOCKSIZE => '65536', IN_MEMORY => 'false', BLOCKCACHE => 'true'}
1 row(s) in 0.0680 seconds
{code}

> Port HBASE-10270 'Remove DataBlockEncoding from BlockCacheKey' to trunk
> -----------------------------------------------------------------------
>
>                 Key: HBASE-10752
>                 URL: https://issues.apache.org/jira/browse/HBASE-10752
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>            Priority: Minor
>             Fix For: 0.99.0
>
>         Attachments: 10752-v1.txt, 10752-v2.txt, 10752-v3.txt, 10752-v4.txt
>
>
> The JIRA removes the block encoding from the key and forces the caller of 
> HFileReaderV2.readBlock() to specify the expected BlockType as well as the 
> expected DataBlockEncoding when these matter. This allows for a decision on 
> either of these at read time instead of cache time, puts responsibility where 
> appropriate, fixes some cache misses when using the scan preloading (which 
> does a read without knowing the type or encoding), allows for the 
> BlockCacheKey to be re-used by the L2 BucketCache and sets us up for a future 
> CompoundScannerV2 which can read both un-encoded and encoded data blocks.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to