You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Wenzhe Zhou (Jira)" <ji...@apache.org> on 2020/10/07 21:44:00 UTC
[jira] [Commented] (IMPALA-10207) Replace MD5 hash for lineage
graph
[ https://issues.apache.org/jira/browse/IMPALA-10207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209882#comment-17209882 ]
Wenzhe Zhou commented on IMPALA-10207:
--------------------------------------
Went through Apache Atlas source code. ImpalaQuery.getHash() function ([https://github.com/apache/atlas/blob/master/addons/impala-bridge/src/main/java/org/apache/atlas/impala/model/ImpalaQuery.java#L60]) is not called anywhere. Don't see any dependency on the hash value in Atlas.
> Replace MD5 hash for lineage graph
> ----------------------------------
>
> Key: IMPALA-10207
> URL: https://issues.apache.org/jira/browse/IMPALA-10207
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Affects Versions: Impala 4.0
> Reporter: Wenzhe Zhou
> Assignee: Wenzhe Zhou
> Priority: Major
> Labels: FIPS
>
> To support FIPS, we have to use FIPS-approved algorithms. In front end, we use MD5 hash algorithms to generate query hash for lineage graph. But MD5 is one of forbidden algorithms for FIPS. We have to replace MD5 with FIPS-approved algorithm, or non-cryptographic hash function like murmur3_128.
> We might need to figure out if there are external dependencies on the hash. e.g. the lineage graph was consumed by other component services, like Apache Atlas, and maybe they somehow rely on the hash being consistent across versions (seems unlikely).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org