[Mondrian] Problem Using Dimension Twice

[Isaias Sanchez]

Ok, I'll talk to then.

Thanks,

Isaias S.

El mar., 5 de mayo de 2015 19:54, Julian Hyde <julianhyde at gmail.com>
escribió:

>
> On May 5, 2015, at 6:22 AM, Isaias Sanchez <isaias.sanchez.l at gmail.com>
> wrote:
>
> WITH
> SET [~FILTER] AS
>     {[Time].[Year by Weeks].[2015].[2015-05-04].[2015-05-05]}
> SET [~ROWS_Destination Info] AS
>     {[Destination Info - Client].[Destination Info].[Destination].Members}
> SET [~ROWS_Destination Info] AS
>     {[Destination Info - Internal].[Destination Info].[ABKHAZIA]}
> SELECT
> NON EMPTY {[Measures].[Calls]} ON COLUMNS,
> NON EMPTY NonEmptyCrossJoin([~ROWS_Destination Info], [~ROWS_Destination
> Info]) ON ROWS
> FROM [Traffic Management]
> WHERE [~FILTER]
>
>
> I think Saiku has generated a bad query. It is illegal to have two sets
> with the same name.
>
> Can you log a bug on Mondrian - it should give an error if set names are
> not distinct.
>
> Then Mondrian resolves
>
> > NonEmptyCrossJoin([~ROWS_Destination Info], [~ROWS_Destination Info])
>
> and of course it has asking to combine two sets of the same dimensionality.
>
> So the main bug, I think, is in Saiku; it should generate set names based
> on the use of the dimension (e.g. “~ROWS_Destination Info - Internal”)
> rather than the shared dimension.
>
> Julian
>
> _______________________________________________
> Mondrian mailing list
> Mondrian at pentaho.org
> http://lists.pentaho.org/mailman/listinfo/mondrian
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20150505/8daffca4/attachment.html