phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3928) Consider retrying once after any SQLException
Date Fri, 09 Jun 2017 00:41:18 GMT

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

James Taylor commented on PHOENIX-3928:
---------------------------------------

WDYT, [~sukunaidu@gmail.com]? Is this something you might have spare cycles to pursue? An
example of a test would be QueryCompilerTest.testOnDupKeyWithGlobalIndex() where the first
client drops the index and then the second client attempts an UPSERT with an ON DUPLICATE
KEY clause. There are many other examples of this in these negative tests that depend on the
state of the metadata.

> Consider retrying once after any SQLException
> ---------------------------------------------
>
>                 Key: PHOENIX-3928
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3928
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>             Fix For: 4.12.0
>
>
> There are more cases in which a retry would successfully execute than when a MetaDataEntityNotFoundException.
For example, certain error cases that depend on the state of the metadata would work on retry
if the metadata had changed. We may want to retry on any SQLException and simply loop through
the tables involved (plan.getSourceRefs().iterator()), and if any meta data was updated, go
ahead and retry once.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message