phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-4091) Document TABLESAMPLE feature
Date Sat, 16 Sep 2017 19:46:02 GMT


Hadoop QA commented on PHOENIX-4091:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against master branch at commit df5b0d213887ef79b83d1e4dbf15dce8d128272f.
  ATTACHMENT ID: 12887514

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

    {color:green}+0 tests included{color}.  The patch appears to be a documentation, build,
                        or dev patch that doesn't require tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output:

This message is automatically generated.

> Document TABLESAMPLE feature
> ----------------------------
>                 Key: PHOENIX-4091
>                 URL:
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: James Taylor
>            Assignee: Ethan Wang
>             Fix For: 4.12.0
>         Attachments: PHOENIX-4091.diff, Sampling_Accuracy_Performance.jpg
> Now that PHOENIX-153 has been committed, we need to update our website documentation
to describe how to use it. For an overview of updating the website, see
For TABLESAMPLE, we need:
> - Inclusion of TABLESAMPLE in our grammar description (which lives in phoenix.csv) so
that it shows up here:
> - Top level page describing how to use TABLESAMPLE from a user perspective. These pages
are typically done in markdown. For example, see
which lives in
> - Inclusion of the new top level page in the Features menu (which lives in site.xml).

This message was sent by Atlassian JIRA

View raw message