[
https://issues.apache.org/jira/browse/IMPALA-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889871#comment-17889871
]
ASF subversion and git services commented on IMPALA-13393:
----------------------------------------------------------
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]>
> Cleanup outdated maven config
> -----------------------------
>
> Key: IMPALA-13393
> URL: https://issues.apache.org/jira/browse/IMPALA-13393
> Project: IMPALA
> Issue Type: Task
> Components: Frontend
> Affects Versions: Impala 4.4.0
> Reporter: Michael Smith
> Assignee: Michael Smith
> Priority: Major
> Fix For: Impala 4.5.0
>
>
> The config around javax.el is very outdated. It was added in 2018, when
> Impala used Sentry. The comment about Hbase depending on it is also no longer
> accurate. There's no need to pin javax.el anymore, and an update to
> CDP_BUILD_NUMBER will update cron-utils (via HMS) so javax.el isn't used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
