@kapa.ai https://github.com/airbytehq/airbyte/issues/61419 facing the same issue -> java.lang.RuntimeException: java.sql.SQLFeatureNotSupportedException: getResultSet not implemented . I see its resolved but still getting the error. Also our clickhouse is updated to latest version , 0.2.6. Can you tell me what is the issue.

You’re hitting a known ClickHouse source connector issue. From the GitHub issue you linked, the error

java.lang.RuntimeException: java.sql.SQLFeatureNotSupportedException: getResultSet not implemented

comes from the ClickHouse JDBC driver’s

Array#getResultSet()

not being implemented. [clickhouse issue] Key points from that issue: • The problem is in the ClickHouse JDBC driver, not in your Airbyte config. [clickhouse issue] • The ClickHouse team implemented the missing method in JDBC driver version

0.9.5

. [clickhouse issue] • Airbyte then fixed the connector by updating to a driver version that includes this implementation (closed as “Fixed in PR #72395”). [clickhouse issue] However, the knowledge sources do not state: • Which exact Airbyte

source-clickhouse

connector version first included that fix. • Whether connector version

0.2.6

(your version) already contains the updated JDBC driver. So based only on the provided information, I can’t definitively say whether

0.2.6

is using the fixed JDBC driver or not. What you can infer and check: 1. The error you see is exactly the one caused by the missing

getResultSet()

in the JDBC driver, so it strongly suggests your running connector is still using an older ClickHouse JDBC version (pre‑0.9.5). [clickhouse issue] 2. The GitHub issue is marked fixed via PR

#72395

, so you likely need the connector version that includes that PR; if your deployment is not on that version (or is using a cached/older image), you’ll still see the error. [clickhouse issue] Because the knowledge sources don’t list the exact mapping between connector versions and JDBC driver versions, I can’t tell you precisely which Airbyte

source-clickhouse

version you must upgrade to. Recommended next steps (based on what we know): • Ensure you are running a

source-clickhouse

connector version that includes PR

#72395

(or newer). • If you are already on such a version but still see the error, it likely means the runtime image still bundles an older ClickHouse JDBC driver; in that case, you’ll need to: ◦ Confirm the connector image tag actually changed in your Airbyte deployment, and ◦ Open a new GitHub issue referencing #61419 and PR #72395 so the team can verify the driver version in the

0.2.6

image. If you can share the exact Airbyte platform version and the full connector image tag you’re running, support/maintainers can cross‑check it against the PR that fixed this. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai i used some 0.3.0-rc docker images but now i am getting this error CompositeIterator(close):126 exception while closing java.lang.RuntimeException: java.sql.SQLException: No current row

The knowledge sources don’t mention the

java.sql.SQLException: No current row

error specifically, so I can’t say with certainty what the exact root cause is in your case. What we do know from the linked issues: •

0.3.0-rc.1

of the ClickHouse source upgrades the JDBC driver to

0.9.5

with custom type mapping. [ClickHouse changelog] • That upgrade was done to fix the earlier

SQLFeatureNotSupportedException: getResultSet not implemented

problem by pulling in the ClickHouse JDBC driver where

Array#getResultSet()

is implemented. [ClickHouse issue 61419; ClickHouse changelog] So: • Moving to

0.3.0-rc

images likely resolved the

getResultSet not implemented

error by changing the driver, but the new

No current row

exception is not documented in the provided sources as a known Airbyte ClickHouse connector issue. • The stack traces we have for ClickHouse in the sources only show: ◦

SQLFeatureNotSupportedException: getResultSet not implemented

[ClickHouse issue 61419] ◦

java.io.IOException: Premature EOF

[ClickHouse issue 69337] and nothing about

No current row

. Given that, I can’t reliably tell whether

No current row

is: • A new regression in the

0.3.0-rc

connector, • A behavior change in the upgraded ClickHouse JDBC driver, • Or something specific to your query/data pattern. Practical next steps (based only on what’s documented): 1. Capture and share the full stack trace and connector version (e.g.

source-clickhouse:0.3.0-rc.1

) in a new GitHub issue, referencing: ◦ The previous

getResultSet

issue (#61419) and ◦ The driver upgrade PR (#72395). [ClickHouse issue 61419; ClickHouse changelog] 2. If possible, also test with the latest non‑RC ClickHouse source version available in your Airbyte deployment, in case the RC has a regression that was later fixed (the sources don’t state this either way). Because the knowledge sources don’t describe

No current row

at all, anything more specific would be speculation. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

can you check, @kapa.ai when this issue was resolved then what happened, like why it was fixed and why it worked for people.

From the information in the linked issue and docs, we can see what changed and why it fixed the problem for many users, but not every low‑level detail. What the original problem was The failing call was:

java.sql.SQLFeatureNotSupportedException: getResultSet not implemented

coming from

com.clickhouse.jdbc.ClickHouseArray.getResultSet

. [SQLFeatureNotSupported issue] Airbyte’s JDBC-based ClickHouse source uses

java.sql.Array#getResultSet()

when reading array‑typed columns. Because the ClickHouse JDBC driver did not implement this method, any table with such types could cause the source to crash during sync. [SQLFeatureNotSupported issue] What changed on the ClickHouse side In the GitHub comments, a ClickHouse maintainer explains: • The method was missing in the driver. • They implemented it and released it in ClickHouse JDBC 0.9.5. [SQLFeatureNotSupported issue] So the root cause was: driver didn’t implement a method Airbyte relies on. What changed on the Airbyte side Airbyte then: 1. Upgraded the ClickHouse source connector to use a newer JDBC driver: ◦

0.3.0-rc.1

of

source-clickhouse

is documented as: “Upgrade ClickHouse JDBC driver to 0.9.5 with custom type mapping.” [ClickHouse source changelog] 2. Closed the GitHub issue as “Fixed in PR #72395”, which is that same upgrade. [SQLFeatureNotSupported issue] Once Airbyte’s connector image started bundling JDBC 0.9.5, the previously missing

Array#getResultSet()

was now implemented, so the same Airbyte code path no longer threw

SQLFeatureNotSupportedException

. Why it then worked for people For users who: • Upgraded to a ClickHouse source connector version that includes PR #72395 (e.g.

0.3.0-rc.1

with JDBC 0.9.5), and • Ran syncs against the same schemas, the behavior changed because: • The Airbyte code still calls

getResultSet()

on arrays. • The new JDBC driver now supports that call instead of throwing

SQLFeatureNotSupportedException

. So the exact same sync that previously failed at runtime now completes successfully, because the underlying driver behavior changed. What we don’t know from the sources The knowledge we have does not say: • Whether any additional Airbyte-side logic changes (beyond the driver bump and “custom type mapping”) were needed to make it work. • Why some users in the comments still see issues even after trying

0.3.0-rc

or `0.2.6`; one user explicitly reports still getting the error and another confirms only that the fix was merged. [SQLFeatureNotSupported issue] So, based on the available information, the resolution story is: > ClickHouse implemented

Array#getResultSet()

in JDBC 0.9.5 → Airbyte updated the ClickHouse source to use that driver in PR #72395 → for users running that updated connector image, the

getResultSet not implemented

error disappeared because the driver now supports the method Airbyte was already calling. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.