You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/25 14:50:20 UTC
[jira] [Commented] (KAFKA-3987) Allow configuration of the hash
algorithm used by the LogCleaner's offset map
[ https://issues.apache.org/jira/browse/KAFKA-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392037#comment-15392037 ]
ASF GitHub Bot commented on KAFKA-3987:
---------------------------------------
GitHub user luafran opened a pull request:
https://github.com/apache/kafka/pull/1661
KAFKA-3987: Allow config of the hash algorithm used by the log cleaner
Allow configuration of the hash algorithm used by the Log Cleaner's offset map
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/luafran/kafka config-for-log-cleaner-hash-algo
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1661.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1661
----
commit 2e7e507903c73740ca498405c5680a8c528ccda6
Author: Luciano Afranllie <lu...@gmail.com>
Date: 2016-07-25T14:39:59Z
KAFKA-3987: Allow configuration of the hash algorithm used by the LogCleaner's offset map
----
> Allow configuration of the hash algorithm used by the LogCleaner's offset map
> -----------------------------------------------------------------------------
>
> Key: KAFKA-3987
> URL: https://issues.apache.org/jira/browse/KAFKA-3987
> Project: Kafka
> Issue Type: Improvement
> Components: config
> Reporter: Luciano Afranllie
> Priority: Minor
> Fix For: 0.10.1.0
>
>
> In order to be able to do deployments of Kafka that are FIPS 140-2 (https://en.wikipedia.org/wiki/FIPS_140-2) complaint one of the requirements is not to use MD5.
> Kafka is using MD5 to hash message keys in the offset map (SkimpyOffsetMap) used by the log cleaner.
> The idea is to be able to configure this hash algorithm to something allowed by FIPS using a new configuration property.
> The property could be named "log.cleaner.hash.algorithm" with a default value equal to "MD5" and the idea is to use it in the constructor of CleanerConfig.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)