You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Quanlong Huang (Jira)" <ji...@apache.org> on 2022/04/17 12:23:00 UTC
[jira] [Updated] (IMPALA-10657) Remove usage of shaded imports
[ https://issues.apache.org/jira/browse/IMPALA-10657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Quanlong Huang updated IMPALA-10657:
------------------------------------
Fix Version/s: Impala 4.0.0
> Remove usage of shaded imports
> ------------------------------
>
> Key: IMPALA-10657
> URL: https://issues.apache.org/jira/browse/IMPALA-10657
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Reporter: John Sherman
> Assignee: John Sherman
> Priority: Major
> Fix For: Impala 4.0.0
>
>
> It seems there are a few spots where maybe an IDE automatically resolved a FE or test import to from a shaded dependency. We should use the direct dependency to remove confusion and reduce the required jars for some usages of the FE code.
> Examples being:
> fe/src/main/java/org/apache/impala/analysis/MultiAggregateInfo.java uses org.apache.kudu.shaded.com.google.common.collect.Lists
> fe/src/main/java/org/apache/impala/catalog/Transaction.java uses org.apache.curator.shaded.com.google.common.base.Preconditions
> fe/src/main/java/org/apache/impala/planner/AnalyticPlanner.java use org.apache.curator.shaded.com.google.common.collect.Iterables
> fe/src/test/java/org/apache/impala/analysis/ExprCardinalityTest.java uses org.apache.curator.shaded.com.google.common.collect.Sets
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org