Pentaho Analysis - Mondrian
  1. Pentaho Analysis - Mondrian
  2. MONDRIAN-264

Range(start,end) should allow NULL for start and end

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Severe Severe
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Notice:
      When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.

      Description

      The RANGE(start,end) function, often used with the syntax

      {start : end}

      , returns a set of members between the start and end member inclusive. The members must be of the same Level. Using a NULL value for one of the two sides should make the set automatically go to the beginning or end of the Level. Further testing on MSAS should provide the desired behaviour to implement (I suppose that NULL:NULL doesn't make sense because there's no Level specified).

        Issue Links

          Activity

          Hide
          Mondrian Importer User added a comment -
          {mbienstein}

          , 03/01/2007: IP, Artifact Created: 57.66.77.4 |

          {jhyde}, 03/02/2007: IP, Comment Added: 66.92.12.96 | {jhyde}

          , 03/14/2007: assigned_to, 100 |

          {willgorman}

          , 03/22/2007: IP, Comment Added: 67.91.57.34 |

          {jhyde}, 03/22/2007: IP, Comment Added: 66.92.12.96 | {jhyde}

          , 03/22/2007: status_id, 1 |

          {jhyde}, 03/22/2007: close_date, 0 | {jhyde}

          , 03/22/2007: resolution_id, 100

          Show
          Mondrian Importer User added a comment - {mbienstein} , 03/01/2007: IP, Artifact Created: 57.66.77.4 | {jhyde}, 03/02/2007: IP, Comment Added: 66.92.12.96 | {jhyde} , 03/14/2007: assigned_to, 100 | {willgorman} , 03/22/2007: IP, Comment Added: 67.91.57.34 | {jhyde}, 03/22/2007: IP, Comment Added: 66.92.12.96 | {jhyde} , 03/22/2007: status_id, 1 | {jhyde}, 03/22/2007: close_date, 0 | {jhyde} , 03/22/2007: resolution_id, 100
          Hide
          Mondrian Importer User added a comment -
          {jhyde}

          , 03/02/2007: Logged In: YES
          user_id=312935
          Originator: NO

          Those semantics are inconsistent with what we agreed in bug 1403220 ( http://sourceforge.net/tracker/index.php?func=detail&aid=1403220&group_id=35302&atid=414613 ). Keep the semantics the same.

          So,

          select

          { [Time].[1997].[Q1] : NULL }

          on 0 from [Sales]

          should yield the empty set.

          Fixer should add a testcase for this. Obviously.

          Show
          Mondrian Importer User added a comment - {jhyde} , 03/02/2007: Logged In: YES user_id=312935 Originator: NO Those semantics are inconsistent with what we agreed in bug 1403220 ( http://sourceforge.net/tracker/index.php?func=detail&aid=1403220&group_id=35302&atid=414613 ). Keep the semantics the same. So, select { [Time].[1997].[Q1] : NULL } on 0 from [Sales] should yield the empty set. Fixer should add a testcase for this. Obviously.
          Hide
          Mondrian Importer User added a comment -
          {willgorman}

          , 03/22/2007: Logged In: YES
          user_id=160824
          Originator: NO

          I've checked in step one of this fix, which is supporting NULL in the expression compiler. For now, range still returns an empty set if a NULL is passed in.

          Show
          Mondrian Importer User added a comment - {willgorman} , 03/22/2007: Logged In: YES user_id=160824 Originator: NO I've checked in step one of this fix, which is supporting NULL in the expression compiler. For now, range still returns an empty set if a NULL is passed in.
          Hide
          Mondrian Importer User added a comment -
          {jhyde}

          , 03/22/2007: Logged In: YES
          user_id=312935
          Originator: NO

          That's sufficient fix for now. Marking closed. Change 8928/8929/8930, will be in mondrian-2.3.

          We can debate – and possibly change – the semantics of range next major release.

          Show
          Mondrian Importer User added a comment - {jhyde} , 03/22/2007: Logged In: YES user_id=312935 Originator: NO That's sufficient fix for now. Marking closed. Change 8928/8929/8930, will be in mondrian-2.3. We can debate – and possibly change – the semantics of range next major release.
          Hide
          Tim Richardson added a comment -

          Did this get debated and possibly changed?

          Show
          Tim Richardson added a comment - Did this get debated and possibly changed?

            People

            • Assignee:
              Will Gorman
              Reporter:
              mbienstein
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: