You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lens.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/08/11 10:25:46 UTC

[jira] [Commented] (LENS-711) Allow chain ref columns to have multiple chain destinations

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

Hudson commented on LENS-711:
-----------------------------

FAILURE: Integrated in Lens-Commit #875 (See [https://builds.apache.org/job/Lens-Commit/875/])
LENS-711 : Allow chain ref columns to have multiple chain destinations (amareshwari: rev bab05e4fa42cacdf7d605bc61a7261d39222e974)
* lens-cube/src/main/java/org/apache/lens/cube/parse/DenormalizationResolver.java
* lens-cube/src/test/java/org/apache/lens/cube/parse/TestTimeRangeWriterWithQuery.java
* lens-cube/src/test/java/org/apache/lens/cube/parse/TestDenormalizationResolver.java
* lens-cube/src/test/java/org/apache/lens/cube/parse/TestBaseCubeQueries.java
* lens-cli/src/test/java/org/apache/lens/cli/TestLensCubeCommands.java
* lens-examples/src/main/resources/sales-cube.xml
* lens-server/src/test/java/org/apache/lens/server/metastore/TestMetastoreService.java
* lens-cube/src/test/java/org/apache/lens/cube/metadata/TestCubeMetastoreClient.java
* lens-cube/src/main/java/org/apache/lens/cube/metadata/CubeMetastoreClient.java
* lens-cube/src/main/java/org/apache/lens/cube/parse/FieldValidator.java
* lens-api/src/main/resources/cube-0.1.xsd
* lens-cli/src/test/resources/sample-cube.xml
* lens-cube/src/main/java/org/apache/lens/cube/metadata/MetastoreUtil.java
* lens-cli/src/test/resources/test-detail.xml
* lens-cube/src/main/java/org/apache/lens/cube/metadata/ReferencedDimAtrribute.java
* lens-cube/src/test/java/org/apache/lens/cube/parse/CubeTestSetup.java
* lens-server/src/main/java/org/apache/lens/server/metastore/JAXBUtils.java
* lens-cube/src/main/java/org/apache/lens/cube/parse/CandidateTableResolver.java
* lens-cube/src/main/java/org/apache/lens/cube/parse/JoinResolver.java


> Allow chain ref columns to have multiple chain destinations
> -----------------------------------------------------------
>
>                 Key: LENS-711
>                 URL: https://issues.apache.org/jira/browse/LENS-711
>             Project: Apache Lens
>          Issue Type: Improvement
>          Components: cube
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 2.3
>
>         Attachments: LENS-711.3.patch
>
>
> Right now, we allow ReferenceDimAttribute to be a chain ref column which specifies chain_name, and ref_col from the chain. This improvement proposed is to allow different chain_name, ref_col pair to be accepted.
> Usecase :
> We have multiple time dimension tables : say HourDim, DayDim and MonthDim.
> All of them have timestamp as field which can be mapped to a time field on cube. So, there will be three different chains associated with this reference attribute and optionally the referring column can be different as well.



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

Re: [jira] [Commented] (LENS-711) Allow chain ref columns to have multiple chain destinations

Posted by "amareshwarisr ." <am...@gmail.com>.
Failure seems unrelated, as the tests did not finish in lens-cube module.
Rerunning the build.

On Tue, Aug 11, 2015 at 1:55 PM, Hudson (JIRA) <ji...@apache.org> wrote:

>
>     [
> https://issues.apache.org/jira/browse/LENS-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681429#comment-14681429
> ]
>
> Hudson commented on LENS-711:
> -----------------------------
>
> FAILURE: Integrated in Lens-Commit #875 (See [
> https://builds.apache.org/job/Lens-Commit/875/])
> LENS-711 : Allow chain ref columns to have multiple chain destinations
> (amareshwari: rev bab05e4fa42cacdf7d605bc61a7261d39222e974)
> *
> lens-cube/src/main/java/org/apache/lens/cube/parse/DenormalizationResolver.java
> *
> lens-cube/src/test/java/org/apache/lens/cube/parse/TestTimeRangeWriterWithQuery.java
> *
> lens-cube/src/test/java/org/apache/lens/cube/parse/TestDenormalizationResolver.java
> *
> lens-cube/src/test/java/org/apache/lens/cube/parse/TestBaseCubeQueries.java
> * lens-cli/src/test/java/org/apache/lens/cli/TestLensCubeCommands.java
> * lens-examples/src/main/resources/sales-cube.xml
> *
> lens-server/src/test/java/org/apache/lens/server/metastore/TestMetastoreService.java
> *
> lens-cube/src/test/java/org/apache/lens/cube/metadata/TestCubeMetastoreClient.java
> *
> lens-cube/src/main/java/org/apache/lens/cube/metadata/CubeMetastoreClient.java
> * lens-cube/src/main/java/org/apache/lens/cube/parse/FieldValidator.java
> * lens-api/src/main/resources/cube-0.1.xsd
> * lens-cli/src/test/resources/sample-cube.xml
> * lens-cube/src/main/java/org/apache/lens/cube/metadata/MetastoreUtil.java
> * lens-cli/src/test/resources/test-detail.xml
> *
> lens-cube/src/main/java/org/apache/lens/cube/metadata/ReferencedDimAtrribute.java
> * lens-cube/src/test/java/org/apache/lens/cube/parse/CubeTestSetup.java
> * lens-server/src/main/java/org/apache/lens/server/metastore/JAXBUtils.java
> *
> lens-cube/src/main/java/org/apache/lens/cube/parse/CandidateTableResolver.java
> * lens-cube/src/main/java/org/apache/lens/cube/parse/JoinResolver.java
>
>
> > Allow chain ref columns to have multiple chain destinations
> > -----------------------------------------------------------
> >
> >                 Key: LENS-711
> >                 URL: https://issues.apache.org/jira/browse/LENS-711
> >             Project: Apache Lens
> >          Issue Type: Improvement
> >          Components: cube
> >            Reporter: Amareshwari Sriramadasu
> >            Assignee: Amareshwari Sriramadasu
> >             Fix For: 2.3
> >
> >         Attachments: LENS-711.3.patch
> >
> >
> > Right now, we allow ReferenceDimAttribute to be a chain ref column which
> specifies chain_name, and ref_col from the chain. This improvement proposed
> is to allow different chain_name, ref_col pair to be accepted.
> > Usecase :
> > We have multiple time dimension tables : say HourDim, DayDim and
> MonthDim.
> > All of them have timestamp as field which can be mapped to a time field
> on cube. So, there will be three different chains associated with this
> reference attribute and optionally the referring column can be different as
> well.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>