[
https://issues.apache.org/jira/browse/TAJO-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14034916#comment-14034916
]
ASF GitHub Bot commented on TAJO-774:
-------------------------------------
Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/13#issuecomment-46403452
Hyunsik, thanks for your contribution.
I tried to review the patch carefully, and left some comments.
In addition, I have one more question.
In your patch, bound types of window frame are divided into two groups
according to whether each of them is the start bound or end bound. Thus, an
window frame has one of unbounded preceding, value preceding, or current row as
its start bound and one of unbounded following, value following, or current row
as its end bound.
But I found that precedings(followings) are also allowed as start(end)
bound in PostgreSQL.
(Here is the link to bound restrictions in PostgreSQL.
http://www.postgresql.org/docs/9.1/static/sql-expressions.html#SYNTAX-WINDOW-FUNCTIONS)
Do you have any reasons of this restriction?
> Implement logical plan part and physical executor for window function.
> ----------------------------------------------------------------------
>
> Key: TAJO-774
> URL: https://issues.apache.org/jira/browse/TAJO-774
> Project: Tajo
> Issue Type: Sub-task
> Components: planner/optimizer
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.9.0
>
>
> See the title. The main objective of this issue is to implement the logical
> planning part for window function support.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
