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

Tajo QA commented on TAJO-1447:
-------------------------------

{color:green}*+1 overall.*{color}  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12707720/TAJO-1447.patch
  against master revision release-0.9.0-rc0-222-gb1e174e.

    {color:green}+1 @author.{color}  The patch does not contain any @author 
tags.

    {color:green}+1 tests included.{color}  The patch appears to include 3 new 
or modified test files.

    {color:green}+1 javac.{color}  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc.{color}  The applied patch does not increase the 
total number of javadoc warnings.

    {color:green}+1 checkstyle.{color}  The patch generated 0 code style errors.

    {color:green}+1 findbugs.{color}  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit.{color}  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests.{color}  The patch passed unit tests in 
tajo-core.

Test results: 
https://builds.apache.org/job/PreCommit-TAJO-Build/667//testReport/
Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/667//console

This message is automatically generated.

> Implement ntile window function 
> --------------------------------
>
>                 Key: TAJO-1447
>                 URL: https://issues.apache.org/jira/browse/TAJO-1447
>             Project: Tajo
>          Issue Type: Sub-task
>            Reporter: Seungun Choe
>            Assignee: Seungun Choe
>            Priority: Minor
>         Attachments: TAJO-1447.patch
>
>
> Function : ntile(num_buckets integer)
> Return Type : integer
> Descriptions : integer ranging from 1 to the argument value, dividing the 
> partition as equally as possible



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to