busbey commented on pull request #2539: URL: https://github.com/apache/hbase/pull/2539#issuecomment-714540943
We should use the one in the hfile, otherwise the only way to change the config is to throw away your cluster and start over. I think a DEBUG message of what hash we're using is a good idea. I don't think it needs to be at a more visible level since most uses wouldn't be impacted by that information. For something like a restricted system that shouldn't use unapproved algorithms can we rely on an external enforcement mechanism? Like if I have configured my cluster to use some FIPS compliant checksum and I believe I have rewritten all my data so that there are no more hfiles with e.g. MD5, is there something that could cause the RS to get an exception should it attempt to use MD5 to read an old hfile that was somehow missed? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
