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

Hadoop QA commented on PHOENIX-4138:
------------------------------------

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

    {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:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

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

    {color:red}-1 lineLengths{color}.  The patch introduces the following lines longer than 100:
    +        assertFalse(MetaDataEndpointImpl.execeededIndexQuota(PTableType.INDEX, parentTable, configuration));
+        assertTrue(MetaDataEndpointImpl.execeededIndexQuota(PTableType.INDEX, parentTable, configuration));
+        conn1.createStatement().execute("CREATE INDEX " + indexTableNameOne + " ON " + tableName + "(COL1) INCLUDE (COL2,COL3,COL4)");
+        // here we ensure we get a too many indexes error since we are only allowed a max of one index.
+            conn1.createStatement().execute("CREATE INDEX " + indexTableNameTwo + " ON " + tableName + "(COL2) INCLUDE (COL1,COL3,COL4)");
+            assertEquals("ERROR 1047 (43A04): Too many indexes have already been created on the physical table. tableName=T000001", e.getMessage());
+    static boolean execeededIndexQuota(PTableType tableType, PTable parentTable, Configuration configuration) {

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
     ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.PartialIndexRebuilderIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.UpsertValuesIT

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

This message is automatically generated.

> Create a hard limit on number of indexes per table
> --------------------------------------------------
>
>                 Key: PHOENIX-4138
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4138
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Rahul Shrivastava
>            Assignee: churro morales
>         Attachments: PHOENIX-4138.patch, PHOENIX-4138.v1.patch, PHOENIX-4138.v2.patch, PHOENIX-4138_v3.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> There should be a config parameter to impose a hard limit on number of indexes per table. There is a SQL Exception https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/exception/SQLExceptionCode.java#L260 , but it gets triggered on the server side  (https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataEndpointImpl.java#L1589) . 
> We need a client side limit that can be configured via Phoenix config parameter. Something like if user create more than lets say 30 indexes per table, it would not allow more index creation for the that specific table. 



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