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

Hadoop QA commented on PHOENIX-3807:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12877169/PHOENIX-3807.v2.patch
  against master branch at commit 8a34de7a4c74584f5fb3a7ab9aaa64fd6269717b.
  ATTACHMENT ID: 12877169

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

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

Console output: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1213//console

This message is automatically generated.

> Add server level metrics for secondary indexes
> ----------------------------------------------
>
>                 Key: PHOENIX-3807
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3807
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Assignee: Vincent Poon
>             Fix For: 4.12.0
>
>         Attachments: PHOENIX-3807.v1.master.patch, PHOENIX-3807.v2.patch, 
> Screen Shot 2017-05-31 at 4.00.16 PM.png
>
>
> Add server level metrics for secondary indexes
> - Histogram metrics for time to complete all secondary index updates per 
> primary table update per index type. Will help us trend perf over time and 
> catch impending issues. 
> - Histogram metrics for number of updates dispatched to secondary index 
> stores to service one primary table update per index type. Will help us catch 
> inefficient behavior or problematic schema design. 
> - Count of deployed secondary indexes by type. Will help understand and trend 
> index usage, or catch deploy of an unwanted index type.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to