[
https://issues.apache.org/jira/browse/IMPALA-10711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe McDonnell reassigned IMPALA-10711:
--------------------------------------
Assignee: Joe McDonnell
> Allow restricting the filesystem permissions check at startup to a particular
> directory
> ---------------------------------------------------------------------------------------
>
> Key: IMPALA-10711
> URL: https://issues.apache.org/jira/browse/IMPALA-10711
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Affects Versions: Impala 4.0
> Reporter: Joe McDonnell
> Assignee: Joe McDonnell
> Priority: Critical
>
> At startup, Impala validates that it has access to the filesystem (via
> JniFrontend::checkFileSystem()). It does this by doing a
> getTotalNumVisibleFiles() on the root path. The root path is defined by the
> fs.defaultFS property. On S3 and other object stores, that is always the root
> of the bucket.
> Code:
> https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/service/JniFrontend.java#L887
> For security reasons, a user may want to restrict an Impala instance to a
> subdirectory of the s3 bucket (or other object store). This check at the root
> on startup makes that impossible.
> Impala should provide a way to customize where the check takes place. The
> check is primarily about making sure that Impala has appropriate permissions
> and is configured correctly. Checking a subdirectory of the s3 bucket is just
> as effective for this purpose.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
