prestodb/presto · error · PrestoException

PROCEDURE_NOT_FOUND

PROCEDURE_NOT_FOUND

Error message

Procedure not registered: 

What it means

Testing-only registry error from TestProcedureRegistry.resolve: no procedure with the requested schema.table name is registered for the connector. This is the PROCEDURE_NOT_FOUND sentinel for the in-memory test registry; the faulty input is the procedure name being resolved.

Source

Thrown at presto-main-base/src/main/java/com/facebook/presto/testing/TestProcedureRegistry.java:68

    }

    @Override
    public void removeProcedures(ConnectorId connectorId)
    {
        connectorProcedures.remove(connectorId);
    }

    @Override
    public BaseProcedure<?> resolve(ConnectorId connectorId, SchemaTableName name)
    {
        Map<SchemaTableName, BaseProcedure<?>> procedures = connectorProcedures.get(connectorId);
        if (procedures != null) {
            BaseProcedure<?> procedure = procedures.get(name);
            if (procedure != null) {
                return procedure;
            }
        }
        throw new PrestoException(PROCEDURE_NOT_FOUND, "Procedure not registered: " + name);
    }

    @Override
    public DistributedProcedure resolveDistributed(ConnectorId connectorId, SchemaTableName name)
    {
        Map<SchemaTableName, BaseProcedure<?>> procedures = connectorProcedures.get(connectorId);
        if (procedures != null) {
            BaseProcedure<?> procedure = procedures.get(name);
            if (procedure instanceof DistributedProcedure) {
                return (DistributedProcedure) procedure;
            }
        }
        throw new PrestoException(PROCEDURE_NOT_FOUND, "Distributed procedure not registered: " + name);
    }

    @Override
    public boolean isDistributedProcedure(ConnectorId connectorId, SchemaTableName name)
    {

View on GitHub (pinned to 55bb57d202)

Solutions

1. Register the procedure via addProcedures before resolving it
2. Check the procedure's schema and table name spelling
3. Ensure the correct ConnectorId is used when resolving

When it happens

Trigger: Thrown at presto-main-base/src/main/java/com/facebook/presto/testing/TestProcedureRegistry.java:68 when the library encounters an invalid state.

Common situations: See trigger scenarios.

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