apache/shardingsphere · error · SQLFeatureNotSupportedException
getCharacterStream
Error message
getCharacterStream
What it means
java.sql.SQLFeatureNotSupportedException thrown by the Apache ShardingSphere JDBC driver when ResultSet.getCharacterStream(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. getCharacterStream(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:81
@Override
public final InputStream getBinaryStream(final String columnLabel) throws SQLException {
throw new SQLFeatureNotSupportedException("getBinaryStream");
}
@Override
public final SQLWarning getWarnings() throws SQLException {
throw new SQLFeatureNotSupportedException("getWarnings");
}
@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");
}
@OverrideView on GitHub (pinned to e952770a21)
Solutions
- Replace rs.getCharacterStream(int columnIndex) with rs.getString(...), which DatabaseMetaDataResultSet implements, then build the stream/reader yourself (new ByteArrayInputStream(s.getBytes(StandardCharsets.US_ASCII)) or new StringReader(s)).
- If binary data was intended, use rs.getBytes(...) instead of a character stream.
- If you do not control the calling code (third-party tool), point its metadata introspection at the underlying physical datasource instead of the ShardingSphere datasource.
- As a last resort wrap the metadata ResultSet in a delegating adapter that implements the stream getters on top of getString.
- Do not wait for a driver upgrade: the throw is final and by design in every ShardingSphere 5.x release.
Example fix
// before - throws SQLFeatureNotSupportedException on ShardingSphere metadata result sets
InputStream ascii = metaDataRs.getAsciiStream("REMARKS");
Reader reader = metaDataRs.getCharacterStream("REMARKS");
// after - getString is implemented; build the stream/reader yourself
String remarks = metaDataRs.getString("REMARKS");
InputStream ascii = remarks == null ? null : new ByteArrayInputStream(remarks.getBytes(StandardCharsets.US_ASCII));
Reader reader = remarks == null ? null : new StringReader(remarks); Defensive patterns
Strategy: try-catch
Validate before calling
// 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:");
} Type guard
private static boolean isUnsupportedMetaDataResultSet(final ResultSet rs) {
return rs != null && rs.getClass().getName().startsWith("org.apache.shardingsphere.driver.jdbc.core.resultset.DatabaseMetaDataResultSet");
} Try / catch
try {
return rs.getCharacterStream(int columnIndex);
} catch (final SQLFeatureNotSupportedException e) {
// ShardingSphere metadata result sets: fall back to the implemented scalar getter
final String s = rs.getString(col);
} Prevention
- Never assume a JDBC driver implements every ResultSet getter; DatabaseMetaData results are the most commonly stubbed surface.
- When adding ShardingSphere in front of an existing datasource, smoke-test the metadata paths your frameworks use (getTables/getColumns loops) before shipping.
- Prefer the simplest getter (getString/getObject/getBytes) and convert in application code; it is portable across drivers.
- Treat SQLFeatureNotSupportedException (an SQLException subclass) as a signal about capability, not a transient failure - never retry it.
When it happens
Trigger: Calling getCharacterStream(int columnIndex) on the ResultSet returned by ShardingSphereDatabaseMetaData, e.g. connection.getMetaData().getTables(null, null, "%", new String[]{"TABLE"}") followed by rs.getCharacterStream(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.
Related errors
AI-assisted analysis of apache/shardingsphere@e952770a21 (2026-08-14).
Data as JSON: /api/errors/4500bff4b37e5f99.
Report an issue: GitHub.