apache/iceberg · error · RuntimeException

Failed to get view info from metastore %s.%s

Error message

Failed to get view info from metastore %s.%s

What it means

HiveViewOperations.doRefresh throws a RuntimeException (wrapping the original Thrift exception) when the Hive metastore call to fetch view info fails with a generic TException. This indicates a metastore communication or server-side failure rather than a missing object, so it is surfaced with the database/view name and the cause chained.

Source

Thrown at hive-metastore/src/main/java/org/apache/iceberg/hive/HiveViewOperations.java:109

    try {
      table = metaClients.run(client -> client.getTable(database, viewName));

      // Check if we are trying to load an Iceberg Table as a View
      HiveOperationsBase.validateIcebergTableNotLoadedAsIcebergView(table, fullName);
      // Check if it is a valid Iceberg View
      HiveOperationsBase.validateTableIsIcebergView(table, fullName);

      metadataLocation =
          table.getParameters().get(BaseMetastoreTableOperations.METADATA_LOCATION_PROP);

    } catch (NoSuchObjectException e) {
      if (currentMetadataLocation() != null) {
        throw new NoSuchViewException("View does not exist: %s.%s", database, viewName);
      }
    } catch (TException e) {
      String errMsg =
          String.format("Failed to get view info from metastore %s.%s", database, viewName);
      throw new RuntimeException(errMsg, e);
    } catch (InterruptedException e) {
      Thread.currentThread().interrupt();
      throw new RuntimeException("Interrupted during refresh", e);
    }

    refreshFromMetadataLocation(metadataLocation);
  }

  @SuppressWarnings("checkstyle:CyclomaticComplexity")
  @Override
  public void doCommit(ViewMetadata base, ViewMetadata metadata) {
    boolean newView = base == null;
    String newMetadataLocation = writeNewMetadataIfRequired(metadata);
    boolean hiveEngineEnabled = false;

    CommitStatus commitStatus = CommitStatus.FAILURE;
    boolean updateHiveView = false;

View on GitHub (pinned to 86d9c8fc54)

Solutions

1. Check HMS availability and logs; restart or fail over the metastore if it is unhealthy.
2. Verify hive.metastore.uris and network connectivity/firewall rules from the client.
3. Retry the operation after confirming the metastore is reachable; inspect the chained cause (getCause()) for the underlying Thrift error.
4. Align hive-metastore client library versions with the server if protocol errors appear.

Example fix

// before: no handling of transient metastore failures
view.refresh();
// after
try {
  view.refresh();
} catch (RuntimeException e) {
  if (e.getCause() instanceof TException) { /* retry or fail over */ }
  throw e;
}

// Pre-check metastore reachability
// e.g., ping HMS or validate hive.metastore.uris configuration before bulk operations

try {
  view.refresh();
} catch (RuntimeException e) {
  if (e.getCause() instanceof TException) {
    // retry with backoff after checking HMS health
  } else { throw e; }
}

When it happens

Trigger: Any refresh of a Hive view where hive.getView (or equivalent metastore RPC) throws TException — e.g., metastore connectivity failures, HMS server errors, thrift protocol issues.

Common situations: Hive metastore down or restarting; network partitions between client and HMS; thrift version/protocol mismatch; HMS timeouts under load; misconfigured metastore URIs.

Understand the failure class

Background: Database query failed: Internal Server Error 500s wrapping SQL, Prisma, and connection failures — what to check first — this error's family across 16 libraries.

Related errors

• Failed to list all tables under namespace ${namespace}
• Failed to list all views under namespace ${namespace}
• Failed to drop ${identifier}
• Failed to drop view ${identifier}
• Failed to check table existence of ${baseTableIdentifier}

AI-assisted analysis of apache/iceberg@86d9c8fc54 (2026-09-12). Data as JSON: /api/errors/5de9d2d45dded59a. Report an issue: GitHub.