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

["Samarth Jain (JIRA)" <ji...@apache.org>]

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

Samarth Jain edited comment on PHOENIX-4151 at 9/5/17 10:12 PM:
----------------------------------------------------------------

[~jamestaylor]  - With PHOENIX-4096, we aim to disallow DML and DDL operations when connection has SCN set. If that is the case, how can we support point in time queries in our tests? Do we need to inject our own clock and control timestamps?


was (Author: samarthjain):
With PHOENIX-4096, we aim to disallow DML and DDL operations when connection has SCN set. If that is the case, how can we support point in time queries in our tests? Do we need to inject our own clock and control timestamps? 

> 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.<init>(NotQueryIT.java:56)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
> 	at org.apache.phoenix.end2end.NotQueryIT.<init>(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.<init>(QueryIT.java:66)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
> 	at org.apache.phoenix.end2end.QueryIT.<init>(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.<init>(CaseStatementIT.java:58)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
> 	at org.apache.phoenix.end2end.CaseStatementIT.<init>(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)