[
https://issues.apache.org/jira/browse/HDFS-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15485744#comment-15485744
]
Andrew Wang commented on HDFS-10850:
------------------------------------
Okay, from a quick look at the Hive code, one possible issue is with
{{SemanticAnalyzer#getStagingDirectoryPathname}}, since it passes in a temp
path that might not exist yet. Correct comparison would be with the parent dir
instead.
[~daryn] do you have a stack trace we can look at?
Also, do we have any other "query" APIs that take a path, but do *not* throw
FNF? This seems semantically weird to me, which is why I'm wondering if we can
fix this in Hive instead.
> 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
