Details
-
Sub-task
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
None
-
None
-
None
-
ghx-label-9
Description
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.
Attachments
Issue Links
- is related to
-
IMPALA-7597 "show partitions" does not retry on InconsistentMetadataFetchException
- Resolved
-
IMPALA-7599 Make num retries for InconsistentMetadataFetchException configurable
- Resolved