[jira] [Commented] (PHOENIX-4640) Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

2018-03-12 Thread Hudson (JIRA)

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

Hudson commented on PHOENIX-4640:
-

FAILURE: Integrated in Jenkins build PreCommit-PHOENIX-Build #1801 (See 
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/1801/])
PHOENIX-4640 Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for (jtaylor: 
rev 8e73fc7dae17c93201654c72a71154eb04951f29)
* (edit) 
phoenix-core/src/it/java/org/apache/phoenix/end2end/ParallelStatsEnabledIT.java


> Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache
> ---
>
> Key: PHOENIX-4640
> URL: https://issues.apache.org/jira/browse/PHOENIX-4640
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4640_v1.patch
>
>
> Since stats have their own client-side cache, there's no need to consider 
> STATS_UPDATE_FREQ_MS_ATTRIB for the server-side TTL cache.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4640) Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

2018-03-11 Thread Pedro Boado (JIRA)

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

Pedro Boado commented on PHOENIX-4640:
--

It fixed it. Thanks [~jamestaylor]

> Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache
> ---
>
> Key: PHOENIX-4640
> URL: https://issues.apache.org/jira/browse/PHOENIX-4640
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4640_v1.patch
>
>
> Since stats have their own client-side cache, there's no need to consider 
> STATS_UPDATE_FREQ_MS_ATTRIB for the server-side TTL cache.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4640) Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

2018-03-11 Thread Hudson (JIRA)

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

Hudson commented on PHOENIX-4640:
-

FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #58 (See 
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/58/])
PHOENIX-4640 Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for (jtaylor: 
rev b0d793d646ad93396a6b22002b31fdd48e7382a6)
* (edit) 
phoenix-core/src/it/java/org/apache/phoenix/end2end/ParallelStatsEnabledIT.java


> Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache
> ---
>
> Key: PHOENIX-4640
> URL: https://issues.apache.org/jira/browse/PHOENIX-4640
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4640_v1.patch
>
>
> Since stats have their own client-side cache, there's no need to consider 
> STATS_UPDATE_FREQ_MS_ATTRIB for the server-side TTL cache.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4640) Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

2018-03-11 Thread Hudson (JIRA)

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

Hudson commented on PHOENIX-4640:
-

FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-0.98 #1829 (See 
[https://builds.apache.org/job/Phoenix-4.x-HBase-0.98/1829/])
PHOENIX-4640 Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for (jtaylor: 
rev 71eb20468b39a0bf407c1176e1f09232c3409602)
* (edit) 
phoenix-core/src/it/java/org/apache/phoenix/end2end/ParallelStatsEnabledIT.java


> Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache
> ---
>
> Key: PHOENIX-4640
> URL: https://issues.apache.org/jira/browse/PHOENIX-4640
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4640_v1.patch
>
>
> Since stats have their own client-side cache, there's no need to consider 
> STATS_UPDATE_FREQ_MS_ATTRIB for the server-side TTL cache.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4640) Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

2018-03-11 Thread James Taylor (JIRA)

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

James Taylor commented on PHOENIX-4640:
---

I checked in an addendum for PHOENIX-4640 that should fix this issue.

> Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache
> ---
>
> Key: PHOENIX-4640
> URL: https://issues.apache.org/jira/browse/PHOENIX-4640
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4640_v1.patch
>
>
> Since stats have their own client-side cache, there's no need to consider 
> STATS_UPDATE_FREQ_MS_ATTRIB for the server-side TTL cache.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4640) Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

2018-03-11 Thread Pedro Boado (JIRA)

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

Pedro Boado commented on PHOENIX-4640:
--

Hi [~jamestaylor], any ideas why this commit could have broken
TenantSpecificTablesDDLIT and ViewIT in 4.x-cdh5.11.2 ? Branches 4.x-HBase-1.2 
and 4.x-HBase-1.3 look ok. 
{code:java}
[ERROR] Tests run: 16, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
161.966 s <<< FAILURE! - in org.apache.phoenix.end2end.TenantSpecificTablesDDLIT
[ERROR] 
testAllDropParentTableWithCascadeWithMultipleTenantTablesAndIndexes(org.apache.phoenix.end2end.TenantSpecificTablesDDLIT)
  Time elapsed: 9.184 s  <<< ERROR!
org.apache.phoenix.exception.PhoenixIOException: 
org.apache.hadoop.hbase.DoNotRetryIOException: V_T46: Table qualifier must 
not be empty
at 
org.apache.phoenix.util.ServerUtil.createIOException(ServerUtil.java:96)
at 
org.apache.phoenix.coprocessor.MetaDataEndpointImpl.dropTable(MetaDataEndpointImpl.java:2031)
at 
org.apache.phoenix.coprocessor.generated.MetaDataProtos$MetaDataService.callMethod(MetaDataProtos.java:16297)
at 
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:7874)
at 
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1989)
at 
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1971)
at 
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:33652)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2183)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112)
at 
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:185)
at 
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:165)
Caused by: java.lang.IllegalArgumentException: Table qualifier must not be empty
at 
org.apache.hadoop.hbase.TableName.isLegalTableQualifierName(TableName.java:179)
at 
org.apache.hadoop.hbase.TableName.isLegalTableQualifierName(TableName.java:149)
at org.apache.hadoop.hbase.TableName.(TableName.java:322)
at 
org.apache.hadoop.hbase.TableName.createTableNameIfNecessary(TableName.java:358)
at org.apache.hadoop.hbase.TableName.valueOf(TableName.java:418)
at 
org.apache.phoenix.coprocessor.MetaDataEndpointImpl.dropTable(MetaDataEndpointImpl.java:1985)
... 9 more

at 
org.apache.phoenix.end2end.TenantSpecificTablesDDLIT.validateTenantViewIsDropped(TenantSpecificTablesDDLIT.java:411)
at 
org.apache.phoenix.end2end.TenantSpecificTablesDDLIT.testAllDropParentTableWithCascadeWithMultipleTenantTablesAndIndexes(TenantSpecificTablesDDLIT.java:378)
Caused by: org.apache.hadoop.hbase.DoNotRetryIOException: 
org.apache.hadoop.hbase.DoNotRetryIOException: V_T46: Table qualifier must 
not be empty
at 
org.apache.phoenix.util.ServerUtil.createIOException(ServerUtil.java:96)
at 
org.apache.phoenix.coprocessor.MetaDataEndpointImpl.dropTable(MetaDataEndpointImpl.java:2031)
at 
org.apache.phoenix.coprocessor.generated.MetaDataProtos$MetaDataService.callMethod(MetaDataProtos.java:16297)
at 
org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:7874)
at 
org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1989)
at 
org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1971)
at 
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:33652)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2183)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112)
at 
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:185)
at 
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:165)
Caused by: java.lang.IllegalArgumentException: Table qualifier must not be empty
at 
org.apache.hadoop.hbase.TableName.isLegalTableQualifierName(TableName.java:179)
at 
org.apache.hadoop.hbase.TableName.isLegalTableQualifierName(TableName.java:149)
at org.apache.hadoop.hbase.TableName.(TableName.java:322)
at 
org.apache.hadoop.hbase.TableName.createTableNameIfNecessary(TableName.java:358)
at org.apache.hadoop.hbase.TableName.valueOf(TableName.java:418)
at 
org.apache.phoenix.coprocessor.MetaDataEndpointImpl.dropTable(MetaDataEndpointImpl.java:1985)
... 9 more

Caused by: org.apache.hadoop.hbase.ipc.RemoteWithExtrasException: 
org.apache.hadoop.hbase.DoNotRetryIOException: V_T46: Table qualifier must 
not be empty
at 
org.apache.phoenix.util.ServerUtil.createIOException(ServerUtil.java:96)
at 

[jira] [Commented] (PHOENIX-4640) Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

2018-03-09 Thread Hudson (JIRA)

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

Hudson commented on PHOENIX-4640:
-

SUCCESS: Integrated in Jenkins build PreCommit-PHOENIX-Build #1797 (See 
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/1797/])
PHOENIX-4640 Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for (jtaylor: 
rev 32a8f3b290d29a1203485cf8aa6649f338277894)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/cache/GlobalCache.java


> Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache
> ---
>
> Key: PHOENIX-4640
> URL: https://issues.apache.org/jira/browse/PHOENIX-4640
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4640_v1.patch
>
>
> Since stats have their own client-side cache, there's no need to consider 
> STATS_UPDATE_FREQ_MS_ATTRIB for the server-side TTL cache.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4640) Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

2018-03-06 Thread Hudson (JIRA)

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

Hudson commented on PHOENIX-4640:
-

FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #54 (See 
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/54/])
PHOENIX-4640 Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for (jtaylor: 
rev 7047077c0e708cdf14d05467288c4d4daaabf40f)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/cache/GlobalCache.java


> Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache
> ---
>
> Key: PHOENIX-4640
> URL: https://issues.apache.org/jira/browse/PHOENIX-4640
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Fix For: 4.14.0
>
> Attachments: PHOENIX-4640_v1.patch
>
>
> Since stats have their own client-side cache, there's no need to consider 
> STATS_UPDATE_FREQ_MS_ATTRIB for the server-side TTL cache.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4640) Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

2018-03-05 Thread Thomas D'Silva (JIRA)

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

Thomas D'Silva commented on PHOENIX-4640:
-

+1

> Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache
> ---
>
> Key: PHOENIX-4640
> URL: https://issues.apache.org/jira/browse/PHOENIX-4640
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Fix For: 4.14.0
>
> Attachments: PHOENIX-4640_v1.patch
>
>
> Since stats have their own client-side cache, there's no need to consider 
> STATS_UPDATE_FREQ_MS_ATTRIB for the server-side TTL cache.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4640) Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

2018-03-05 Thread James Taylor (JIRA)

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

James Taylor commented on PHOENIX-4640:
---

Oops. Attached now.

> Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache
> ---
>
> Key: PHOENIX-4640
> URL: https://issues.apache.org/jira/browse/PHOENIX-4640
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Fix For: 4.14.0
>
> Attachments: PHOENIX-4640_v1.patch
>
>
> Since stats have their own client-side cache, there's no need to consider 
> STATS_UPDATE_FREQ_MS_ATTRIB for the server-side TTL cache.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4640) Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

2018-03-05 Thread Thomas D'Silva (JIRA)

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

Thomas D'Silva commented on PHOENIX-4640:
-

[~jamestaylor] you forgot to attach the patch.

> Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache
> ---
>
> Key: PHOENIX-4640
> URL: https://issues.apache.org/jira/browse/PHOENIX-4640
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Fix For: 4.14.0
>
>
> Since stats have their own client-side cache, there's no need to consider 
> STATS_UPDATE_FREQ_MS_ATTRIB for the server-side TTL cache.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4640) Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache

2018-03-05 Thread James Taylor (JIRA)

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

James Taylor commented on PHOENIX-4640:
---

Trivial patch. Please review, [~tdsilva].

> Don't consider STATS_UPDATE_FREQ_MS_ATTRIB in TTL for server side cache
> ---
>
> Key: PHOENIX-4640
> URL: https://issues.apache.org/jira/browse/PHOENIX-4640
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Fix For: 4.14.0
>
>
> Since stats have their own client-side cache, there's no need to consider 
> STATS_UPDATE_FREQ_MS_ATTRIB for the server-side TTL cache.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)