[
https://issues.apache.org/jira/browse/RANGER-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adnan Hemani updated RANGER-3365:
---------------------------------
Description:
The Ranger-Presto/Trino plugin doesn't have filesystem URL authorization
builtin for relevant connectors (such as Hive and Iceberg) like the Ranger-Hive
plugin does. I understand that only a few of Trino's connectors have locations
that should be validated - but is there any reason we don't have this for the
connectors that should be validating URLs?
>From my understanding, this will require changes on both the Ranger-Presto
>plugin and on the Trino side, so it probably won't be an easy change - but I
>think it'd be a great addition to our current feature set.
I mainly opened this ticket to see what the folks think about this - I'm happy
to look into it and contribute if there's no objections!
Summary: Trino/PrestoSQL URL Validation (was: Presto )
> Trino/PrestoSQL URL Validation
> ------------------------------
>
> Key: RANGER-3365
> URL: https://issues.apache.org/jira/browse/RANGER-3365
> Project: Ranger
> Issue Type: Improvement
> Components: plugins, Ranger
> Reporter: Adnan Hemani
> Priority: Major
>
> The Ranger-Presto/Trino plugin doesn't have filesystem URL authorization
> builtin for relevant connectors (such as Hive and Iceberg) like the
> Ranger-Hive plugin does. I understand that only a few of Trino's connectors
> have locations that should be validated - but is there any reason we don't
> have this for the connectors that should be validating URLs?
>
> From my understanding, this will require changes on both the Ranger-Presto
> plugin and on the Trino side, so it probably won't be an easy change - but I
> think it'd be a great addition to our current feature set.
>
> I mainly opened this ticket to see what the folks think about this - I'm
> happy to look into it and contribute if there's no objections!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
