prestodb/presto · error · PrestoException

NOT_FOUND

NOT_FOUND

Error message

Catalog not found: 

What it means

Failure in AbstractPropertyManager.getSupportedProperties while looking up properties: no connector is registered for the given catalog name, so its property metadata cannot be loaded; the catalog name is appended to the message.

Source

Thrown at presto-main-base/src/main/java/com/facebook/presto/metadata/AbstractPropertyManager.java:190

                Object value = propertyMetadata.getDefaultValue();
                if (value != null) {
                    properties.put(propertyMetadata.getName(), value);
                }
            }
        }
        return properties.build();
    }

    public Map<ConnectorId, Map<String, PropertyMetadata<?>>> getAllProperties()
    {
        return ImmutableMap.copyOf(connectorProperties);
    }

    private Map<String, PropertyMetadata<?>> getSupportedProperties(ConnectorId connectorId, String catalog)
    {
        Map<String, PropertyMetadata<?>> supportedProperties = connectorProperties.get(connectorId);
        if (supportedProperties == null) {
            throw new PrestoException(NOT_FOUND, "Catalog not found: " + catalog);
        }
        return supportedProperties;
    }

    private Object evaluatePropertyValue(Expression expression, Type expectedType, Session session, Metadata metadata, Map<NodeRef<Parameter>, Expression> parameters)
    {
        Expression rewritten = ExpressionTreeRewriter.rewriteWith(new ParameterRewriter(parameters), expression);
        Object value = evaluateConstantExpression(rewritten, expectedType, metadata, session, parameters);

        // convert to object value type of SQL type
        BlockBuilder blockBuilder = expectedType.createBlockBuilder(null, 1);
        writeNativeValue(expectedType, blockBuilder, value);
        Object objectValue = expectedType.getObjectValue(session.getSqlFunctionProperties(), blockBuilder, 0);

        if (objectValue == null) {
            throw new PrestoException(propertyError, format("Invalid null value for %s property", propertyType));
        }
        return objectValue;

View on GitHub (pinned to 55bb57d202)

Solutions

1. Verify the catalog name spelling and that the catalog is registered (SHOW CATALOGS)
2. Create the catalog via its connector configuration and ensure it loaded successfully
3. Check coordinator logs for connector load failures for that catalog

When it happens

Trigger: Thrown at presto-main-base/src/main/java/com/facebook/presto/metadata/AbstractPropertyManager.java:190 when the library encounters an invalid state.

Common situations: See trigger scenarios.

Understand the failure class

Background: NOT_FOUND error code: why tRPC, Harbor, Nacos and other libraries return 404 "not found" errors for resources that may still exist — this error's family across 11 libraries.

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