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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
