You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Kunal Khatua (JIRA)" <ji...@apache.org> on 2018/05/31 20:22:00 UTC

[jira] [Commented] (DRILL-5984) Support for Symlinked Table Paths to be used in Drill Queries.

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

Kunal Khatua commented on DRILL-5984:
-------------------------------------

This is interesting because for even simple text files, it is not able to read the entire file, but only the first line. Upvoting this so that it gets picked up.

> Support for Symlinked Table Paths to be used in Drill Queries.
> --------------------------------------------------------------
>
>                 Key: DRILL-5984
>                 URL: https://issues.apache.org/jira/browse/DRILL-5984
>             Project: Apache Drill
>          Issue Type: New Feature
>    Affects Versions: 1.11.0
>         Environment: OS : CentOS 7.1
> MapR-DB Version: 5.2.2
>            Reporter: Saravanabavagugan Vengadasundaram
>            Priority: Major
>
> MapR-FS supports symlinks and hence MapR-DB table paths support symlinks as well. As part of the project I work on, we use symlinks as a means of communication to talk to the physical file. An employee table in MapR-DB will be represented as  "/tables/Employee/Entity_1233232" and there will be a symlink called "/tables/Employee/Entity" pointing to the actual physical table. Currently, drill does not understand queries having the symlink path but only executes queries having the actual physical table path. So every time, I need to find out the actual physical path of the table and frame my query. It would be nice to have this feature in next version of Drill. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)