prestodb/presto · error · SemanticException

NOT_SUPPORTED

NOT_SUPPORTED

Error message

'%s' is a materialized view, and rename is not supported

What it means

SemanticException (NOT_SUPPORTED) from RenameTableTask.execute: the source name passed to ALTER TABLE ... RENAME resolves to a materialized view rather than a base table, and Presto has no rename operation for materialized views. Suppressed when IF EXISTS is specified.

Source

Thrown at presto-main-base/src/main/java/com/facebook/presto/execution/RenameTableTask.java:64

        return "RENAME TABLE";
    }

    @Override
    public ListenableFuture<?> execute(RenameTable statement, TransactionManager transactionManager, Metadata metadata, AccessControl accessControl, Session session, List<Expression> parameters, WarningCollector warningCollector, String query)
    {
        QualifiedObjectName tableName = createQualifiedObjectName(session, statement, statement.getSource(), metadata);
        Optional<TableHandle> tableHandle = metadata.getMetadataResolver(session).getTableHandle(tableName);
        if (!tableHandle.isPresent()) {
            if (!statement.isExists()) {
                throw new SemanticException(MISSING_TABLE, statement, "Table '%s' does not exist", tableName);
            }
            return immediateFuture(null);
        }

        Optional<MaterializedViewDefinition> optionalMaterializedView = metadata.getMetadataResolver(session).getMaterializedView(tableName);
        if (optionalMaterializedView.isPresent()) {
            if (!statement.isExists()) {
                throw new SemanticException(NOT_SUPPORTED, statement, "'%s' is a materialized view, and rename is not supported", tableName);
            }
            return immediateFuture(null);
        }

        QualifiedObjectName target = createQualifiedObjectName(session, statement, statement.getTarget(), metadata);
        getConnectorIdOrThrow(session, metadata, target.getCatalogName(), statement, targetTableCatalogError);
        if (metadata.getMetadataResolver(session).getTableHandle(target).isPresent()) {
            throw new SemanticException(TABLE_ALREADY_EXISTS, statement, "Target table '%s' already exists", target);
        }
        if (!tableName.getCatalogName().equals(target.getCatalogName())) {
            throw new SemanticException(NOT_SUPPORTED, statement, "Table rename across catalogs is not supported");
        }
        accessControl.checkCanRenameTable(session.getRequiredTransactionId(), session.getIdentity(), session.getAccessControlContext(), tableName, target);

        metadata.renameTable(session, tableHandle.get(), target);

        return immediateFuture(null);
    }

View on GitHub (pinned to 55bb57d202)

Solutions

1. Use CREATE MATERIALIZED VIEW with the new name and DROP the old view to emulate a rename
2. Check whether the underlying connector/catalog offers a native rename DDL for materialized views
3. Target a base table if the intent was to rename a table

When it happens

Trigger: Thrown at presto-main-base/src/main/java/com/facebook/presto/execution/RenameTableTask.java:64 when the library encounters an invalid state.

Common situations: See trigger scenarios.

Understand the failure class

Background: Presto NOT_SUPPORTED error: what "not supported" means and how to fix it — this error's family across 3 libraries.

AI-assisted analysis of prestodb/presto@55bb57d202 (2026-09-04). Data as JSON: /api/errors/a8d71095d3544528. Report an issue: GitHub.