Comment 3 for bug 1433926

add specific scenarios for this issue with type 'default/aggregated'.

1. interval.time = 1, limit.time = 120
    a. aggr stats works as expected.
    b. query stats works as expected.
        query ran for 01:32 did not publish.
        query ran for 02:24 published.

2. interval.time = 1, limit.time = 5
    a. aggr stats works as expected.
    b. query stats works as expected.
        query ran for 01:30 published.
        query ran for 00:07 published.

3. interval.time = 60, limit.time = 5
    a. aggr stats works as expected.
    b. problem with query stats. Looks it took 60 instead.
        query ran for 01:29 published.
        query ran for 00:28 did not publish.

4. interval.time = 180, limit.time = 120
    a. aggr stats works as expected.
    b. problem with query stats. Looks it took 180 instead.
        query ran for 03:41 published.
        query ran for 02:20 did not publish.

5. interval.time = 60, limit.time = 120
    a. aggr stats works as expected.
    b. query stats works as expected.
        query ran for 01:34 did not publish.
        query ran for 03:43 published.

6. interval.time = 1, limit.time = 0
    a. aggr stats works as expected.
    b. problem with query stats. Looks it took 60.
        query ran for 00:25 did not publish.
        query ran for 01:28 published.

7. interval.time = 1, limit.time = -1
    a. no aggr stats.
    b. no query stats. Query ran for 01:35 did not publish.
    c. no session stats.

8. interval.time = -1, limit.time = 1
    a. no aggr stats.
    b. no query stats. Query ran for 01:35 did not publish.
    c. no session stats.

9. interval.time = 0, limit.time = 0
    a. aggr stats works as default 60.
    b. query stats works as default 60.
        query ran for 00:28 did not publish.
        query ran for 01:35 published.