[ 
https://issues.apache.org/jira/browse/IMPALA-9708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889872#comment-17889872
 ] 

ASF subversion and git services commented on IMPALA-9708:
---------------------------------------------------------

Commit 4c3b5f94f190843378ad1d840b489bde5caa3955 in impala's branch 
refs/heads/master from Michael Smith
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=4c3b5f94f ]

IMPALA-13393: Remove old javax.el config

Pinning javax.el was done when Impala still used Sentry. That was
removed in IMPALA-9708, and Hbase now explicitly depends on a
specific version. So this pin is no longer relevant.

Change-Id: I5be3eeeacf2f6fb04bc5106902e1d11b3886d844
Reviewed-on: http://gerrit.cloudera.org:8080/21827
Tested-by: Michael Smith <[email protected]>
Reviewed-by: Riza Suminto <[email protected]>


> Remove Sentry support
> ---------------------
>
>                 Key: IMPALA-9708
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9708
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend, Frontend
>    Affects Versions: Impala 4.0.0
>            Reporter: Joe McDonnell
>            Assignee: Joe McDonnell
>            Priority: Major
>             Fix For: Impala 4.0.0
>
>
> This tracks the first round of removing Sentry support. In particular, it 
> should retire user-facing configurations of Sentry, such as 
> authorization_provider. The user experience and developer experience should 
> end up in a coherent place.
> There will be pieces of dead code and some obsolete functionality that will 
> not be addressed by this JIRA. There will be followup changes for those. See 
> the sentry removal epic.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to