drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5365) FileNotFoundException when reading a parquet file
Date Sun, 26 Mar 2017 01:15:42 GMT

    [ https://issues.apache.org/jira/browse/DRILL-5365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942093#comment-15942093

ASF GitHub Bot commented on DRILL-5365:

Github user paul-rogers commented on a diff in the pull request:

    --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/store/dfs/FileSystemPlugin.java
    @@ -74,6 +74,7 @@ public FileSystemPlugin(FileSystemConfig config, DrillbitContext context,
               fsConf.set(s, config.config.get(s));
    +      fsConf.set("fs.default.name", config.connection);
    --- End diff --
    Please use `FileSystem.FS_DEFAULT_NAME_KEY`. It seems that `"fs.default.name"` is deprecated.
    But, note, that is exactly what the next line of code does. So, perhaps there is more
going on here than a first read suggests? Or, are we confusing ourselves about the meaning
of the two properties?

> 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

View raw message