[
https://issues.apache.org/jira/browse/HIVE-6137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879193#comment-13879193
]
Shuaishuai Nie commented on HIVE-6137:
--------------------------------------
Agree with [~thejas]. In this scenario, this fix may produce misleading error
message. I think the right fix should be finding the location where hive check
the existence of the external table loaction and pass "FileNotFound" exception
from there. In addition, does this problem also exist for external partition?
If so, we should keep the behavior consistence in both cases.
> Hive should report that the file/path doesn’t exist when it doesn’t (it now
> reports SocketTimeoutException)
> -----------------------------------------------------------------------------------------------------------
>
> Key: HIVE-6137
> URL: https://issues.apache.org/jira/browse/HIVE-6137
> Project: Hive
> Issue Type: Bug
> Reporter: Hari Sankar Sivarama Subramaniyan
> Assignee: Hari Sankar Sivarama Subramaniyan
> Attachments: HIVE-6137.1.patch
>
>
> Hive should report that the file/path doesn’t exist when it doesn’t (it now
> reports SocketTimeoutException):
> Execute a Hive DDL query with a reference to a non-existent blob (such as
> CREATE EXTERNAL TABLE...) and check Hive logs (stderr):
> FAILED: Error in metadata: org.apache.thrift.transport.TTransportException:
> java.net.SocketTimeoutException: Read timed out
> FAILED: Execution Error, return code 1 from
> org.apache.hadoop.hive.ql.exec.DDLTask
> This error message is not intuitive. If a file doesn't exist, Hive should
> report FileNotFoundException
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
