[
https://issues.apache.org/jira/browse/DRILL-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735807#comment-14735807
]
Venki Korukanti commented on DRILL-3467:
----------------------------------------
UnsupportedOperationException is thrown by FileSystem implementations such as
'ClasspathFileSystem' which have different mechanism of getting the file info
than the normal FileSystem implementations. We want to show this workspace as
we cann't conclusively determine whether it is accessible to the given user.
Ultimately the query may fail if the FileSystem can't provide details of the
file/directory due to permission error. This behavior is consistent with the
behavior when we try to find the view files in ClassPathFileSystem workspaces.
Exception is already passed to the logger.trace method.
> Restrict 'show databases' based on underlying permissions.
> ----------------------------------------------------------
>
> Key: DRILL-3467
> URL: https://issues.apache.org/jira/browse/DRILL-3467
> Project: Apache Drill
> Issue Type: Improvement
> Components: Metadata
> Reporter: Andy Pernsteiner
> Assignee: Venki Korukanti
> Attachments: DRILL-3467-1.patch
>
>
> Ideally, an administrator would have the ability to restrict the visibility
> of workspaces based on the FS permissions that underly those workspaces.
> Currently it appears we only honor this for 'show tables' , but not for 'show
> databases'.
> Without this functionality (or something that gives an equivalent result),
> users will be able to see any and all workspaces, including ones which
> administrators may wish to keep 'invisible'. Additionally, when having
> hundreds (or potentially thousands) of users, seeing all workspaces via 'show
> databases' is likely to make it difficult for end-users to know what they can
> and cannot access.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
