[jira] [Commented] (DRILL-2034) Use the correct schema when creating FileSystem object in HiveScan

["Jason Altekruse (JIRA)" <ji...@apache.org>]

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

Jason Altekruse commented on DRILL-2034:
----------------------------------------

Is there any way to add a unit test for this patch?

> Use the correct schema when creating FileSystem object in HiveScan
> ------------------------------------------------------------------
>
>                 Key: DRILL-2034
>                 URL: https://issues.apache.org/jira/browse/DRILL-2034
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - Hive
>            Reporter: Venki Korukanti
>            Assignee: Venki Korukanti
>             Fix For: 0.8.0
>
>         Attachments: 0001-DRILL-2034-Use-the-correct-schema-when-creating-File.patch
>
>
> We currently get the FileSystem object using FileSystem.get(JobConf) which always returns the FileSystem implementation of default FS setting in conf. This causes problem when Hive MetaStore has tables stored in different storages. For example one table has data on HDFS and other on S3 filesystem. 
> {code}
>         Path path = new Path(table.getSd().getLocation());
>         FileSystem fs = FileSystem.get(job);
>         if (fs.exists(path)) {
>            ....
> {code}
> We should call Path.getFileSystem() which takes the URI schema from the path.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)