- 
                Notifications
    You must be signed in to change notification settings 
- Fork 3.4k
HBASE-26510 Separate the blockcache enabled key and cache data on read key #3893
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| 🎊 +1 overall 
 
 This message was automatically generated. | 
| 💔 -1 overall 
 This message was automatically generated. | 
| 💔 -1 overall 
 This message was automatically generated. | 
| 🎊 +1 overall 
 
 This message was automatically generated. | 
| 💔 -1 overall 
 
 This message was automatically generated. | 
| 💔 -1 overall 
 
 This message was automatically generated. | 
| 🎊 +1 overall 
 
 This message was automatically generated. | 
| 🎊 +1 overall 
 
 This message was automatically generated. | 
| 💔 -1 overall 
 
 This message was automatically generated. | 
| It seems that the both UT failures are xml related. Will submit a blank commit to trigger the QA again. | 
| 🎊 +1 overall 
 
 This message was automatically generated. | 
| 🎊 +1 overall 
 
 This message was automatically generated. | 
| 🎊 +1 overall 
 
 This message was automatically generated. | 
| This is a big behavior change. I suggest you send an email to both dev and user mailing list to clearly describe the old behavior and new behavior, to collect more feedbacks from the community. Thanks. | 
| OK, will send a mail soon. | 
        
          
                hbase-client/src/main/java/org/apache/hadoop/hbase/client/ColumnFamilyDescriptorBuilder.java
          
            Show resolved
            Hide resolved
        
      | * Configuration key to turn on block cache. There are separate switches for read and write. | ||
| */ | ||
| public static final String BLOCKCACHE_ENABLED = "hbase.block.enabled"; | ||
|  | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you meet some issues that make you separate these configs to resolve them? I don't think an additional "hbase.block.enabled" is needed, this will make users confused with which meaning of 'block' here. For the meta blocks the cache should not be disabled, and this is the original design.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I got your point. Let me consider this for a while.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, these changes seems a little bit superfluous. In this case, may I just close this MR and the corresponding jira ticket?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, thanks.
https://issues.apache.org/jira/browse/HBASE-26510