[
https://issues.apache.org/jira/browse/LENS-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371229#comment-14371229
]
Hudson commented on LENS-404:
-----------------------------
SUCCESS: Integrated in Lens-Commit #653 (See
[https://builds.apache.org/job/Lens-Commit/653/])
LENS-404 : Optimize getAll lookups and JoinChain lookups in CubeMetastoreClient
(Amareshwari via jdhok) (jaideep.dhok: rev
954ee08c765e4648d3d81604bf307bb3117e8756)
*
lens-cli/src/main/java/org/apache/lens/cli/commands/LensDimensionTableCommands.java
* lens-cube/src/main/java/org/apache/lens/cube/metadata/CubeFactTable.java
* lens-cube/src/main/java/org/apache/lens/cube/metadata/CubeDimensionTable.java
* lens-cube/src/main/java/org/apache/lens/cube/metadata/CubeMetastoreClient.java
*
lens-server/src/main/java/org/apache/lens/server/metastore/CubeMetastoreServiceImpl.java
> Optimize getAll lookups and JoinChain lookups in CubeMetastoreClient
> --------------------------------------------------------------------
>
> Key: LENS-404
> URL: https://issues.apache.org/jira/browse/LENS-404
> Project: Apache Lens
> Issue Type: Improvement
> Components: cube
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Fix For: 2.1
>
> Attachments: LENS-404.3.patch
>
>
> JoinChains are not tables.
> CubeQueryContext.extractMetaTables queries metastore for all table aliases
> accessed in the query. For actual tables, the tables will be cached in cube
> metastore client. For tables that are not there, it will still do a getTable
> call.
> We should optimize joinchain lookup on the client, not to lookup metastore
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
