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

Posted to issues-all@impala.apache.org by "bharath v (JIRA)" <ji...@apache.org> on 2018/09/12 01:41:00 UTC

[jira] [Assigned] (IMPALA-7530) Re-plan queries on InconsistentMetadataException

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

bharath v reassigned IMPALA-7530:
---------------------------------

    Assignee: Vuk Ercegovac

> Re-plan queries on InconsistentMetadataException
> ------------------------------------------------
>
>                 Key: IMPALA-7530
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7530
>             Project: IMPALA
>          Issue Type: Sub-task
>            Reporter: Todd Lipcon
>            Assignee: Vuk Ercegovac
>            Priority: Critical
>
> In the case that the impalad has cached some information about a table, but the table has since been modified or deleted on the catalogd, the metaprovider can throw an InconsistentMetadataException after invalidating the cached information. On a re-plan, we'll see the new version and avoid the issue. The front-end needs to catch the exception and trigger the replan.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org