[
https://issues.apache.org/jira/browse/LENS-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583103#comment-14583103
]
Hudson commented on LENS-414:
-----------------------------
SUCCESS: Integrated in Lens-Commit #816 (See
[https://builds.apache.org/job/Lens-Commit/816/])
LENS-414: Move LeastPartitionResolver after LeastFactResolver (rajatgupta59:
rev b8995ed3ff3d25bca82448a12fdcbaafc6ada2d6)
* lens-cube/src/main/java/org/apache/lens/cube/parse/LeastPartitionResolver.java
* lens-cube/src/test/java/org/apache/lens/cube/parse/TestQueryMetrics.java
* lens-cube/src/main/java/org/apache/lens/cube/parse/CubeQueryRewriter.java
> LeastPartitionResolver broken after partition timeline cache?
> -------------------------------------------------------------
>
> Key: LENS-414
> URL: https://issues.apache.org/jira/browse/LENS-414
> Project: Apache Lens
> Issue Type: Bug
> Components: cube
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Fix For: 2.2
>
> Attachments: LENS-414.2.patch
>
>
> The number of partitions being calculated is not the correct number after
> LENS-281. It is only number of time values now instead of partitions.
> We might have to change LeastPartitionResolver accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
