apache/shardingsphere · error · SQLFeatureNotSupportedException

getArray

Error message

getArray

What it means

java.sql.SQLFeatureNotSupportedException thrown by the Apache ShardingSphere JDBC driver when ResultSet.getArray(int columnIndex) is called on a DatabaseMetaData result set. Metadata calls such as Connection.getMetaData().getTables()/getColumns()/getIndexInfo()/getPrimaryKeys() on a jdbc:shardingsphere: URL return a synthesized DatabaseMetaDataResultSet that buffers every row as plain Java objects, so only scalar getters (getString, getInt, getBytes, single-arg getDate/getTime/getTimestamp, ...) are implemented. getArray(int columnIndex) is declared final in AbstractUnsupportedDatabaseMetaDataResultSet and always throws, so this is a permanent, intentional limitation, not a version bug.

Source

Thrown at jdbc/src/main/java/org/apache/shardingsphere/driver/jdbc/unsupported/AbstractUnsupportedDatabaseMetaDataResultSet.java:91

    
    @Override
    public final void clearWarnings() throws SQLException {
        throw new SQLFeatureNotSupportedException("clearWarnings");
    }
    
    @Override
    public final Reader getCharacterStream(final int columnIndex) throws SQLException {
        throw new SQLFeatureNotSupportedException("getCharacterStream");
    }
    
    @Override
    public final Reader getCharacterStream(final String columnLabel) throws SQLException {
        throw new SQLFeatureNotSupportedException("getCharacterStream");
    }
    
    @Override
    public final Array getArray(final int columnIndex) throws SQLException {
        throw new SQLFeatureNotSupportedException("getArray");
    }
    
    @Override
    public final Array getArray(final String columnLabel) throws SQLException {
        throw new SQLFeatureNotSupportedException("getArray");
    }
    
    @Override
    public final Blob getBlob(final int columnIndex) throws SQLException {
        throw new SQLFeatureNotSupportedException("getBlob");
    }
    
    @Override
    public final Blob getBlob(final String columnLabel) throws SQLException {
        throw new SQLFeatureNotSupportedException("getBlob");
    }
    
    @Override

View on GitHub (pinned to e952770a21)

Solutions

1. Replace rs.getArray(int columnIndex) with rs.getString(...)/rs.getObject(...), which DatabaseMetaDataResultSet implements; metadata catalogs only contain short scalar values (names, types, remarks).
2. For java.sql.Blob/Clob objects you need for an API, construct SerialBlob/SerialClob (com.sun.rowset or javax.sql.rowset.serial) from the byte[]/String you read.
3. If you need real LOB columns of actual user tables, SELECT them through a normal sharded Statement (whose ResultSet is a ShardingResultSet with full getter support), not through DatabaseMetaData.
4. If you do not control the calling code (third-party tool), run its metadata introspection against the physical datasource.
5. Do not wait for a driver upgrade: the throw is final and by design.

Example fix

// before - throws SQLFeatureNotSupportedException on ShardingSphere metadata result sets
Array array = metaDataRs.getArray("SOURCE_DATA_TYPES");

// after - read the raw literal and parse it yourself
String literal = metaDataRs.getString("SOURCE_DATA_TYPES"); // usually null for metadata catalogs anyway

// Run BEFORE using exotic getters: detect a ShardingSphere-synthesized metadata ResultSet
static boolean isShardingSphereMetaDataResultSet(final ResultSet rs) {
    return rs != null && "org.apache.shardingsphere.driver.jdbc.core.resultset.DatabaseMetaDataResultSet"
            .equals(rs.getClass().getName());
}

static boolean supportsMetaDataGetter(final Connection c) throws SQLException {
    // jdbc:shardingsphere: URLs return the synthesized metadata result set
    return c != null && !c.getMetaData().getURL().startsWith("jdbc:shardingsphere:");
}

private static boolean isUnsupportedMetaDataResultSet(final ResultSet rs) {
    return rs != null && rs.getClass().getName().startsWith("org.apache.shardingsphere.driver.jdbc.core.resultset.DatabaseMetaDataResultSet");
}

try {
    return rs.getArray(int columnIndex);
} catch (final SQLFeatureNotSupportedException e) {
    // ShardingSphere metadata result sets: fall back to the implemented scalar getter
    final String literal = rs.getString(col);
}

When it happens

Trigger: Calling getArray(int columnIndex) on the ResultSet returned by ShardingSphereDatabaseMetaData, e.g. connection.getMetaData().getTables(null, null, "%", new String[]{"TABLE"}") followed by rs.getArray(1)) where connection was opened with the org.apache.shardingsphere.driver JDBC URL (jdbc:shardingsphere:classpath:sharding.yaml or jdbc:shardingsphere:...). Both the int-columnIndex and String-columnLabel overloads of every listed getter throw; the methods are final so no subclass can override them.

Common situations: Code that ran unchanged against the native MySQL/PostgreSQL/OpenGauss driver and is repointed to the ShardingSphere driver URL, so the same metadata loop now hits the stubbed getter; generic schema tooling that enumerates JDBC metadata with feature-rich getters (DBeaver, Squirrel SQL, Liquibase/Hibernate/Flyway schema validators, code generators, DBDiff tools); hand-written metadata loops that defensively call getWarnings()/clearWarnings() or use the Calendar overloads to pin a timezone. LOB getters are a common reflex when columns look binary/large even though metadata columns are short catalog strings.

Related errors

• getUnicodeStream
• getBinaryStream
• getWarnings
• clearWarnings
• getCharacterStream

AI-assisted analysis of apache/shardingsphere@e952770a21 (2026-08-14). Data as JSON: /api/errors/74c927463f66323f. Report an issue: GitHub.