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 2019/01/07 23:20:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Kunal Khatua updated DRILL-5984:
--------------------------------
Fix Version/s: Future
> 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
> Assignee: Pritesh Maker
> Priority: Major
> Fix For: Future
>
>
> 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)