Sailesh Mukil has posted comments on this change. Change subject: IMPALA-5331: Use new libHDFS API to address "Unknown Error 255" ......................................................................
Patch Set 1: > If hdfsGetLastExceptionRootCause() always contains relevant > information, I think we should include it in all cases. What's to > be gained by leaving it out? In many cases, we avoid redundant error information by leaving it out. For example, a file not found error with this change for all types of errors: [localhost:21000] > select * from s3_test; Query: select * from s3_test Query submitted at: 2017-05-16 11:42:13 (Coordinator: http://localhost:25000) Query progress can be monitored at: http://localhost:25000/query_plan?query_id=7b4fea9564c4c1d5:fd45dd8700000000 ERROR: Failed to open HDFS file s3a://sailesh-impala-s3/s3_test_parts/asbasda Error(2): No such file or directory Root cause: FileNotFoundException: No such file or directory: s3a://sailesh-impala-s3/s3_test_parts/asbasda -- To view, visit http://gerrit.cloudera.org:8080/6894 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-MessageType: comment Gerrit-Change-Id: I181e316ed63b70b94d4f7a7557d398a931bb171d Gerrit-PatchSet: 1 Gerrit-Project: Impala-ASF Gerrit-Branch: master Gerrit-Owner: Sailesh Mukil <[email protected]> Gerrit-Reviewer: Henry Robinson <[email protected]> Gerrit-Reviewer: Sailesh Mukil <[email protected]> Gerrit-HasComments: No
