You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lens.apache.org by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org> on 2015/05/05 19:40:00 UTC

[jira] [Updated] (LENS-481) LeastPartitionResolver should check for actual partitions and not requested partitions when lens.cube.query.fail.if.data.partial=false

     [ https://issues.apache.org/jira/browse/LENS-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amareshwari Sriramadasu updated LENS-481:
-----------------------------------------
      Component/s: cube
    Fix Version/s: 2.2

> LeastPartitionResolver should check for actual partitions and not requested partitions when lens.cube.query.fail.if.data.partial=false
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: LENS-481
>                 URL: https://issues.apache.org/jira/browse/LENS-481
>             Project: Apache Lens
>          Issue Type: Bug
>          Components: cube
>            Reporter: Angad Singh
>            Assignee: Rajat Khandelwal
>             Fix For: 2.2
>
>
> Currently LeastPartitionResolver prunes facts based on the desired/requested partitions of facts (based on granularity). Consider a cube with 2 facts - one at daily granularity and one of monthly. Suppose the monthly fact is registered with no partitions and the daily fact has 1 partitions. when you query on a year-long time range, the LeastPartitionResolver spuriously prunes the daily fact (even though it had data) and selects the monthly cube (which doesn't have any data), and runs the query (giving no output).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)