[BUG] JDBC driver forces SQL plugin to use the v1 engine

[MaxKsyunz]

What is the bug?
Users of the JDBC driver cannot make use of new SQL plugin features because queries sent by the JDBC driver by-pass v2 engine and are always executed by the v1 engine.

What is the expected behavior?
Queries sent by JDBC driver to be attempted by v2 engine first and only fallback to v1 engine if it uses unsupported SQL features.

What is your host/environment?

• OpenSearch 2.4.0.0
• JDBC Driver 1.1.0.1

Do you have any additional context?
When JDBC executes a statement, it sets fetch_size parameter to 100. This fails this check here.

[MaxKsyunz]

I haven't found where this happens, yet when I create a connection fetchSize is 0, but when createStatement is called, the query it generates sets fetch_size to 100.

[MaxKsyunz]

I found that the same query works fine in DbVisualizer but in IntelliJ Database tool, fetch_size ends up being 100.

The culprit is probably Statement.setFetchSize override. It's a JDBC method that the client can use to control how many rows are fetched in one request. OpenSearch JDBC driver's ends up setting fetch_size in the REST query to value provided to Statement.setFetchSize.

[jlarue26]

Hi @MaxKsyunz any thoughts on when this bug will be resolved?

[acarbonetto]

Hi @MaxKsyunz any thoughts on when this bug will be resolved?

Working on it currently.

A draft PR is up for the base cases and we're hoping to get it into 2.6 release. Additional features for pagination (larger datasets, WHERE filter, and aggregation) will be coming out periodically with subsequent releases (2.7...).