prestodb/presto · error · PrestoException

NOT_SUPPORTED

NOT_SUPPORTED

Error message

Unsupported type ${type}

What it means

Type dispatch guard in PrometheusRecordCursor.getLong: the column's Type is not one the cursor can convert to a long (only TIMESTAMP_WITH_TIME_ZONE is handled here), so the unsupported type is reported. Fires on schema/connector drift rather than data problems.

Source

Thrown at presto-prometheus/src/main/java/com/facebook/presto/plugin/prometheus/PrometheusRecordCursor.java:232

    @Override
    public boolean getBoolean(int field)
    {
        return true;
    }

    @Override
    public long getLong(int field)
    {
        Type type = getType(field);
        if (type.equals(TIMESTAMP_WITH_TIME_ZONE)) {
            Instant dateTime = (Instant) requireNonNull(getFieldValue(field));
            // render with the fixed offset of the Presto server
            int offsetMinutes = dateTime.atZone(ZoneId.systemDefault()).getOffset().getTotalSeconds() / 60;
            return packDateTimeWithZone(dateTime.toEpochMilli(), offsetMinutes);
        }
        else {
            throw new PrestoException(NOT_SUPPORTED, "Unsupported type " + getType(field));
        }
    }

    @Override
    public double getDouble(int field)
    {
        checkFieldType(field, DOUBLE);
        return (double) getFieldValue(field);
    }

    @Override
    public Slice getSlice(int field)
    {
        checkFieldType(field, createUnboundedVarcharType());
        return Slices.utf8Slice((String) requireNonNull(getFieldValue(field)));
    }

    @Override

View on GitHub (pinned to 55bb57d202)

Solutions

  1. Only select columns whose Prometheus types map to supported Presto types
  2. Add a mapping branch for the new type in getLong if support is needed
  3. Check the connector type mapping configuration
Defensive patterns

Strategy: type-guard

When it happens

Trigger: Thrown at presto-prometheus/src/main/java/com/facebook/presto/plugin/prometheus/PrometheusRecordCursor.java:232 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/134c87e54e15d00a. Report an issue: GitHub.