[
https://issues.apache.org/jira/browse/TAJO-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513963#comment-14513963
]
ASF GitHub Bot commented on TAJO-1415:
--------------------------------------
Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/454#issuecomment-96620163
@sirpkt thanks for updating your patch.
I've tested the following query and found that the result of Tajo is
different from that of pgsql.
**Tajo**
```
default> select l_partkey, first_value(l_linestatus) over (partition by
l_partkey order by l_tax rows between 5 preceding and 8 following) from
lineitem;
...
l_partkey, ?windowfunction
-------------------------------
1,
1,
1,
1,
1,
1, F
1, O
1, O
1, F
1, F
1, O
1, F
1, F
1, F
1, F
1, O
1, O
1, F
1, F
1, F
1, O
1, O
1, F
1, F
1, O
1, F
1, F
1, F
1, O
1, F
1, O
2,
2,
2,
2,
2,
2, O
...
```
**PostgreSQL**
```
jihoonson=# select l_partkey, first_value(l_linestatus) over (partition by
l_partkey order by l_tax rows between 5 preceding and 8 following) from
lineitem;
l_partkey | first_value
-----------+-------------
1 | O
1 | O
1 | O
1 | O
1 | O
1 | O
1 | F
1 | O
1 | F
1 | F
1 | F
1 | F
1 | O
1 | F
1 | F
1 | O
1 | O
1 | F
1 | F
1 | F
1 | F
1 | F
1 | O
1 | O
1 | O
1 | F
1 | O
1 | F
1 | F
1 | F
1 | O
2 | O
...
```
As you can see, some values are null in Tajo.
> Window frame support
> --------------------
>
> Key: TAJO-1415
> URL: https://issues.apache.org/jira/browse/TAJO-1415
> Project: Tajo
> Issue Type: Sub-task
> Components: distributed query plan, parser, physical operator,
> planner/optimizer
> Reporter: Keuntae Park
> Assignee: Keuntae Park
> Fix For: window function
>
>
> We can define frame clause in window definition like
> {code}
> [ RANGE | ROWS ] frame_start
> [ RANGE | ROWS ] BETWEEN frame_start AND frame_end
> {code}
> , where frame_start and frame_end can be one of
> {code}
> UNBOUNDED PRECEDING
> value PRECEDING
> CURRENT ROW
> value FOLLOWING
> UNBOUNDED FOLLOWING
> {code}
> According to the window functions description of
> PostgreSQL(http://www.postgresql.org/docs/9.4/static/functions-window.html),
> there are two types of window functions based on window frame support.
> 1) row_number, rank, dense_rank, percent_rank, cume_dist, tile, lag and lead:
> these functions only work within window partition, which means window frame
> has no effect on these functions.
> 2) first_value, last_value, nth_value, and aggregation function as as window
> function: these functions should work with rows within window frame.
> Currently, Tajo parser recognize the window frame grammar but windowAggExec
> does not use that information.
> It works as if window frame is set as "RANGE BETWEEN UNBOUND PROCEEDING AND
> UNBOUNDED FOLLOWING", which is different from the default window frame
> setting of most DBMSs "RANGE BETWEEN UNBOUND PROCEEDING AND CURRENT ROW".
> Following should be done:
> 1) Applying correct default window frame for first_value, last_value,
> nth_value, and aggregation functions .
> 2) Supporting various window frame expressions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
