You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/03/25 00:14:41 UTC
[jira] [Commented] (DRILL-5365) FileNotFoundException when reading
a parquet file
[ https://issues.apache.org/jira/browse/DRILL-5365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941370#comment-15941370 ]
ASF GitHub Bot commented on DRILL-5365:
---------------------------------------
GitHub user chunhui-shi opened a pull request:
https://github.com/apache/drill/pull/796
DRILL-5365: DrillFileSystem setConf in constructor. DrillFileSystem c…
…ould be created based on provided URI.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chunhui-shi/drill DRILL_5365
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/796.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #796
----
commit e91755a4668346636dc1a33b6b0a86ad6a5654e2
Author: chunhui-shi <cs...@maprtech.com>
Date: 2017-03-02T00:53:23Z
DRILL-5365: DrillFileSystem setConf in constructor. DrillFileSystem could be created based on provided URI.
----
> FileNotFoundException when reading a parquet file
> -------------------------------------------------
>
> Key: DRILL-5365
> URL: https://issues.apache.org/jira/browse/DRILL-5365
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Hive
> Affects Versions: 1.10.0
> Reporter: Chun Chang
> Assignee: Chunhui Shi
>
> The parquet file is generated through the following CTAS.
> To reproduce the issue: 1) two or more nodes cluster; 2) enable impersonation; 3) set "fs.default.name": "file:///" in hive storage plugin; 4) restart drillbits; 5) as a regular user, on node A, drop the table/file; 6) ctas from a large enough hive table as source to recreate the table/file; 7) query the table from node A should work; 8) query from node B as same user should reproduce the issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)