You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Thomas D'Silva (JIRA)" <ji...@apache.org> on 2019/01/18 22:27:00 UTC

[jira] [Updated] (PHOENIX-3928) Consider retrying once after any SQLException

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

Thomas D'Silva updated PHOENIX-3928:
------------------------------------
    Fix Version/s:     (was: 4.15.0)

> 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
>            Assignee: Maddineni Sukumar
>            Priority: Major
>
> 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
(v7.6.3#76005)