[Mondrian] Unexpected behaviour while using a TopCount in a Named Set

Pedro Salgueiro pedro.salgueiro at inductiva.pt
Thu Jul 12 06:41:03 EDT 2012


Forgot to post the jira case location:
http://jira.pentaho.com/browse/MONDRIAN-1187?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aworklog-tabpanel#issue-tabs

On 07/12/2012 11:14 AM, Pedro Salgueiro wrote:
> Thank you all for your help.
> I have just now filled a jira case.
>
> Best regards,
> Pedro
>
>
>
> On 07/11/2012 08:06 PM, Julian Hyde wrote:
>> On Jul 11, 2012, at 11:28 AM, Pedro Alves wrote:
>>
>>> does this also apply for native top count evaluation?
>> No.
>>
>> In May, Pedro Vale fixed native evaluation of topcount so that it 
>> took ranges in the slicer into account, but he didn't fix non-native 
>> evaluation.
>>
>> This bug is that non-native evaluation now behaves differently to 
>> native evaluation. Well, duh.
>>
>> Adding Distinct( ... ) has the effect (the only effect, in this case) 
>> of disabling native evaluation.
>>
>> A workaround, obviously, is to make the argument to TopCount simple 
>> enough that it can use native evaluation.
>>
>> Julian
>>
>> _______________________________________________
>> Mondrian mailing list
>> Mondrian at pentaho.org
>> http://lists.pentaho.org/mailman/listinfo/mondrian
>>
>
>




More information about the Mondrian mailing list