[
https://issues.apache.org/jira/browse/HDFS-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484338#comment-15484338
]
Sergio Peña commented on HDFS-10850:
------------------------------------
[~andrew.wang] The following class is the one that contains the calls to
{{getEncryptionZoneForPath}} (search for all method calls there):
https://github.com/apache/hive/blob/master/shims/0.23/src/main/java/org/apache/hadoop/hive/shims/Hadoop23Shims.java#L1118
The methods that call such function are:
{noformat}
public boolean isPathEncrypted(Path path) throws IOException;
public boolean arePathsOnSameEncryptionZone(Path path1, Path path2) throws
IOException;
public boolean arePathsOnSameEncryptionZone(Path path1, Path path2,
HadoopShims.HdfsEncryptionShim encryptionShim2) throws IOException;
public int comparePathKeyStrength(Path path1, Path path2) throws IOException;
{noformat}
> getEZForPath should NOT throw FNF
> ---------------------------------
>
> Key: HDFS-10850
> URL: https://issues.apache.org/jira/browse/HDFS-10850
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Affects Versions: 2.8.0
> Reporter: Daryn Sharp
> Assignee: Rakesh R
> Priority: Blocker
>
> HDFS-9433 made an incompatible change to the semantics of getEZForPath. It
> used to return the EZ of the closest ancestor path. It never threw FNF. A
> common use of getEZForPath to determining if a file can be renamed, or must
> be copied due to mismatched EZs. Notably, this has broken hive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
