[ 
https://issues.apache.org/jira/browse/LENS-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549839#comment-14549839
 ] 

Hudson commented on LENS-204:
-----------------------------

SUCCESS: Integrated in Lens-Commit #780 (See 
[https://builds.apache.org/job/Lens-Commit/780/])
LENS-204 : Support union across tables in cube rewriting (Sushil Mohanty via 
amareshwari) (amareshwari: rev ab22a24b5f9a567cc92102b8e57cbc4c314242fa)
* lens-cube/src/main/java/org/apache/lens/cube/parse/DimOnlyHQLContext.java
* lens-cube/src/main/java/org/apache/lens/cube/parse/UnionHQLContext.java
* 
lens-cube/src/main/java/org/apache/lens/cube/parse/SingleFactMultiStorageHQLContext.java
* lens-cube/src/main/java/org/apache/lens/cube/parse/SingleFactHQLContext.java
* lens-cube/src/main/java/org/apache/lens/cube/parse/CubeQueryContext.java
* lens-cube/src/test/java/org/apache/lens/cube/parse/TestCubeRewriter.java
* lens-cube/src/main/java/org/apache/lens/cube/parse/CandidateFact.java
* lens-cube/src/test/java/org/apache/lens/cube/parse/CubeTestSetup.java
* lens-cube/src/main/java/org/apache/lens/cube/parse/StorageTableResolver.java


> Support union across tables in cube rewriting
> ---------------------------------------------
>
>                 Key: LENS-204
>                 URL: https://issues.apache.org/jira/browse/LENS-204
>             Project: Apache Lens
>          Issue Type: Improvement
>          Components: cube
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Sushil Mohanty
>             Fix For: 2.2
>
>         Attachments: LENS-204-1.patch, LENS-204-4.patch
>
>
> Right now, if query rewriting requires union across two or more tables, the 
> query fails. We would need union across two or more tables for the following 
> use cases
> # The time range queried is spread across two or more storage tables of a fact
> # The time range queried is spread across two or more fact tables
> # This is debatable use case - the same measure is present in two fact tables
> ** When same measure is present in more than one fact table, we pick one 
> candidate fact table right now. Optionally, we should allow union with other 
> facts through fact property. I won't push for this, but putting it here as we 
> have seen this in our internal data model.



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

Reply via email to