[
https://issues.apache.org/jira/browse/DRILL-8548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18099027#comment-18099027
]
ASF GitHub Bot commented on DRILL-8548:
---------------------------------------
shfshihuafeng commented on PR #3056:
URL: https://github.com/apache/drill/pull/3056#issuecomment-5075379157
> > > @shfshihuafeng Do you use the Drill slack channel? I had a question
for you that does not pertain to this pull request.
> > > @cgivre I haven't joined the Drill Slack channel yet, since Slack is
not accessible within mainland China. If convenient, email me at
[[email protected]](mailto:[email protected])/[[email protected]](mailto:[email protected])
>
> I sent you an email.
@cgivre Thank you for your reply. I did reply to your previous email a few
days ago, but I'm not sure if you received it. Could you please confirm? I will
resend my reply right now
> Integrate Apache Ranger authorization for Drill
> -----------------------------------------------
>
> Key: DRILL-8548
> URL: https://issues.apache.org/jira/browse/DRILL-8548
> Project: Apache Drill
> Issue Type: New Feature
> Components: Server
> Affects Versions: 1.23.0
> Reporter: shihuafeng
> Priority: Major
> Fix For: 1.23.0
>
>
> This issue introduces Apache Ranger as a pluggable authorization framework
> for Drill, enabling centralized table-level and column-level access control
> for Drill queries. It is a substantial feature spanning three layers: a new
> drill-ranger module , integration hooks in exec/java-exec, and distribution
> packaging. The design follows Drill's existing AccessAuthorizer SPI and
> Calcite's RelShuttle mechanism so that column-level checks happen in the
> toRel phase before physical planning
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
