You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2013/09/16 14:12:51 UTC

[jira] [Commented] (TAJO-46) The "having" clause does not work properly

    [ https://issues.apache.org/jira/browse/TAJO-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768267#comment-13768267 ] 

Hyunsik Choi commented on TAJO-46:
----------------------------------

I adjusted the priority of this issue to critical because 'having' clause is very basic feature in SQL. Also, I've assigned to myself.
                
> The "having" clause does not work properly
> ------------------------------------------
>
>                 Key: TAJO-46
>                 URL: https://issues.apache.org/jira/browse/TAJO-46
>             Project: Tajo
>          Issue Type: Bug
>            Reporter: Hyoseok Ryu
>            Assignee: Hyunsik Choi
>            Priority: Critical
>
> I used the following query for testing 
> {code}
> select client, count(requestaddr) as req_cnt from  weblog_day_20130407 where timestamp > 1365332400 and timestamp < 1365333600 group by client having req_cnt > 5
> {code}
> The result of the query includes tuples which does not satisfy the having predicate "req_cnt > 5".
> {code}
> client,  req_cnt
> -------------------------------
> 182.242.126.67,  7
> 117.4.43.183,  2
> 180.175.60.23,  2
> 111.121.67.70,  7
> 223.65.142.52,  7
> 171.252.149.187,  246
> 2.94.0.205,  4
> 183.36.65.68,  9
> 221.214.213.226,  4
> 113.240.238.196,  1
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira