[jira] [Updated] (PHOENIX-4151) Tests extending BaseQueryIT are flapping

2017-09-05 Thread Samarth Jain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Samarth Jain updated PHOENIX-4151:
--
Fix Version/s: 4.12.0

> Tests extending BaseQueryIT are flapping
> 
>
> Key: PHOENIX-4151
> URL: https://issues.apache.org/jira/browse/PHOENIX-4151
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Samarth Jain
>Assignee: Samarth Jain
> Fix For: 4.12.0
>
> Attachments: PHOENIX-4151.patch, PHOENIX-4151_v2.patch, 
> PHOENIX-4151_wip_master.patch, PHOENIX-4151_wip.patch
>
>
> Sample failures:
> {code}
> ERROR] 
> testNotInListOfFloat[NotQueryIT_1](org.apache.phoenix.end2end.NotQueryIT)  
> Time elapsed: 0.001 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.NotQueryIT.(NotQueryIT.java:56)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.NotQueryIT.(NotQueryIT.java:56)
> {code}
> {code}
> [ERROR] testValidStringConcatExpression[indexDDL=CREATE INDEX %s ON %s 
> (a_integer, a_string) INCLUDE (B_STRING, A_DATE) 
> %s,mutable=false,columnEncoded=false](org.apache.phoenix.end2end.QueryIT)  
> Time elapsed: 0.014 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.QueryIT.(QueryIT.java:66)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.QueryIT.(QueryIT.java:66)
> {code}
> {code}
> [ERROR] 
> testNullMultiCondCaseStatement[CaseStatementIT_1](org.apache.phoenix.end2end.CaseStatementIT)
>   Time elapsed: 0.007 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
>   at 
> org.apache.phoenix.end2end.CaseStatementIT.(CaseStatementIT.java:58)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
>   at 
> org.apache.phoenix.end2end.CaseStatementIT.(CaseStatementIT.java:58)
> {code}
> My hunch is that timeouts are happening when creating tables or indices. 
> Probably some sort of a timestamp/scn issue. [~jamestaylor] - any ideas? 
> Would injecting our own clock in EnvironmentEdge help?



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

[jira] [Updated] (PHOENIX-4151) Tests extending BaseQueryIT are flapping

2017-09-05 Thread Samarth Jain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Samarth Jain updated PHOENIX-4151:
--
Attachment: PHOENIX-4151_v2.patch

Forgot to remove two files.

> Tests extending BaseQueryIT are flapping
> 
>
> Key: PHOENIX-4151
> URL: https://issues.apache.org/jira/browse/PHOENIX-4151
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Samarth Jain
>Assignee: Samarth Jain
> Attachments: PHOENIX-4151.patch, PHOENIX-4151_v2.patch, 
> PHOENIX-4151_wip_master.patch, PHOENIX-4151_wip.patch
>
>
> Sample failures:
> {code}
> ERROR] 
> testNotInListOfFloat[NotQueryIT_1](org.apache.phoenix.end2end.NotQueryIT)  
> Time elapsed: 0.001 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.NotQueryIT.(NotQueryIT.java:56)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.NotQueryIT.(NotQueryIT.java:56)
> {code}
> {code}
> [ERROR] testValidStringConcatExpression[indexDDL=CREATE INDEX %s ON %s 
> (a_integer, a_string) INCLUDE (B_STRING, A_DATE) 
> %s,mutable=false,columnEncoded=false](org.apache.phoenix.end2end.QueryIT)  
> Time elapsed: 0.014 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.QueryIT.(QueryIT.java:66)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.QueryIT.(QueryIT.java:66)
> {code}
> {code}
> [ERROR] 
> testNullMultiCondCaseStatement[CaseStatementIT_1](org.apache.phoenix.end2end.CaseStatementIT)
>   Time elapsed: 0.007 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
>   at 
> org.apache.phoenix.end2end.CaseStatementIT.(CaseStatementIT.java:58)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
>   at 
> org.apache.phoenix.end2end.CaseStatementIT.(CaseStatementIT.java:58)
> {code}
> My hunch is that timeouts are happening when creating tables or indices. 
> Probably some sort of a timestamp/scn issue. [~jamestaylor] - any ideas? 
> Would injecting our own clock in EnvironmentEdge help?



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

[jira] [Updated] (PHOENIX-4151) Tests extending BaseQueryIT are flapping

2017-09-05 Thread Samarth Jain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Samarth Jain updated PHOENIX-4151:
--
Attachment: PHOENIX-4151.patch

> Tests extending BaseQueryIT are flapping
> 
>
> Key: PHOENIX-4151
> URL: https://issues.apache.org/jira/browse/PHOENIX-4151
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Samarth Jain
>Assignee: Samarth Jain
> Attachments: PHOENIX-4151.patch, PHOENIX-4151_wip_master.patch, 
> PHOENIX-4151_wip.patch
>
>
> Sample failures:
> {code}
> ERROR] 
> testNotInListOfFloat[NotQueryIT_1](org.apache.phoenix.end2end.NotQueryIT)  
> Time elapsed: 0.001 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.NotQueryIT.(NotQueryIT.java:56)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.NotQueryIT.(NotQueryIT.java:56)
> {code}
> {code}
> [ERROR] testValidStringConcatExpression[indexDDL=CREATE INDEX %s ON %s 
> (a_integer, a_string) INCLUDE (B_STRING, A_DATE) 
> %s,mutable=false,columnEncoded=false](org.apache.phoenix.end2end.QueryIT)  
> Time elapsed: 0.014 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.QueryIT.(QueryIT.java:66)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.QueryIT.(QueryIT.java:66)
> {code}
> {code}
> [ERROR] 
> testNullMultiCondCaseStatement[CaseStatementIT_1](org.apache.phoenix.end2end.CaseStatementIT)
>   Time elapsed: 0.007 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
>   at 
> org.apache.phoenix.end2end.CaseStatementIT.(CaseStatementIT.java:58)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
>   at 
> org.apache.phoenix.end2end.CaseStatementIT.(CaseStatementIT.java:58)
> {code}
> My hunch is that timeouts are happening when creating tables or indices. 
> Probably some sort of a timestamp/scn issue. [~jamestaylor] - any ideas? 
> Would injecting our own clock in EnvironmentEdge help?



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

[jira] [Updated] (PHOENIX-4151) Tests extending BaseQueryIT are flapping

2017-09-05 Thread Samarth Jain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Samarth Jain updated PHOENIX-4151:
--
Attachment: PHOENIX-4151_wip_master.patch

Down to last few tests. There are some tests that deal with grouped aggregation 
that are relying on timestamp. Need to figure out what to do with them.

> Tests extending BaseQueryIT are flapping
> 
>
> Key: PHOENIX-4151
> URL: https://issues.apache.org/jira/browse/PHOENIX-4151
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Samarth Jain
>Assignee: Samarth Jain
> Attachments: PHOENIX-4151_wip_master.patch, PHOENIX-4151_wip.patch
>
>
> Sample failures:
> {code}
> ERROR] 
> testNotInListOfFloat[NotQueryIT_1](org.apache.phoenix.end2end.NotQueryIT)  
> Time elapsed: 0.001 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.NotQueryIT.(NotQueryIT.java:56)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.NotQueryIT.(NotQueryIT.java:56)
> {code}
> {code}
> [ERROR] testValidStringConcatExpression[indexDDL=CREATE INDEX %s ON %s 
> (a_integer, a_string) INCLUDE (B_STRING, A_DATE) 
> %s,mutable=false,columnEncoded=false](org.apache.phoenix.end2end.QueryIT)  
> Time elapsed: 0.014 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.QueryIT.(QueryIT.java:66)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.QueryIT.(QueryIT.java:66)
> {code}
> {code}
> [ERROR] 
> testNullMultiCondCaseStatement[CaseStatementIT_1](org.apache.phoenix.end2end.CaseStatementIT)
>   Time elapsed: 0.007 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
>   at 
> org.apache.phoenix.end2end.CaseStatementIT.(CaseStatementIT.java:58)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
>   at 
> org.apache.phoenix.end2end.CaseStatementIT.(CaseStatementIT.java:58)
> {code}
> My hunch is that timeouts are happening when creating tables or indices. 
> Probably some sort of a timestamp/scn issue. [~jamestaylor] - any ideas? 
> Would injecting our own clock in EnvironmentEdge help?



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

[jira] [Updated] (PHOENIX-4151) Tests extending BaseQueryIT are flapping

2017-09-03 Thread Samarth Jain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Samarth Jain updated PHOENIX-4151:
--
Attachment: PHOENIX-4151_wip.patch

Attaching a work in progress patch. Some tests do rely on the timestamp. I am 
inclined to comment them out or tweak them. Or maybe not have them test out the 
indexing code path.

> Tests extending BaseQueryIT are flapping
> 
>
> Key: PHOENIX-4151
> URL: https://issues.apache.org/jira/browse/PHOENIX-4151
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Samarth Jain
>Assignee: Samarth Jain
> Attachments: PHOENIX-4151_wip.patch
>
>
> Sample failures:
> {code}
> ERROR] 
> testNotInListOfFloat[NotQueryIT_1](org.apache.phoenix.end2end.NotQueryIT)  
> Time elapsed: 0.001 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.NotQueryIT.(NotQueryIT.java:56)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.NotQueryIT.(NotQueryIT.java:56)
> {code}
> {code}
> [ERROR] testValidStringConcatExpression[indexDDL=CREATE INDEX %s ON %s 
> (a_integer, a_string) INCLUDE (B_STRING, A_DATE) 
> %s,mutable=false,columnEncoded=false](org.apache.phoenix.end2end.QueryIT)  
> Time elapsed: 0.014 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.QueryIT.(QueryIT.java:66)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
>   at org.apache.phoenix.end2end.QueryIT.(QueryIT.java:66)
> {code}
> {code}
> [ERROR] 
> testNullMultiCondCaseStatement[CaseStatementIT_1](org.apache.phoenix.end2end.CaseStatementIT)
>   Time elapsed: 0.007 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
>   at 
> org.apache.phoenix.end2end.CaseStatementIT.(CaseStatementIT.java:58)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
>   at 
> org.apache.phoenix.end2end.CaseStatementIT.(CaseStatementIT.java:58)
> {code}
> My hunch is that timeouts are happening when creating tables or indices. 
> Probably some sort of a timestamp/scn issue. [~jamestaylor] - any ideas? 
> Would injecting our own clock in EnvironmentEdge help?



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