GH-37021 [Java][arrow-jdbc] Pluggable getConsumer

[aiguofer]

Rationale for this change

This was discussed in this thread. The getConsumer implementation depends on the implementation for getArrowTypeFromJdbcType, especially for timestamp objects. Since we can provide a different implementation for JdbcToArrowTypeConverter it follows we should be able to provide a different implementation for JdbcConsumerGetter

What changes are included in this PR?

Adds a way to configure an alternate JdbcToArrowUtils.getConsumer function through JdbcToArrowConfigBuilder.setJdbcConsumerGetter.

It also throws a more helpful exception from the default implementations when a provided type is not mapped.

Are these changes tested?

No, the default behavior remains unchanged.

• Related: [Java][JDBC] Converting TIMESTAMP_WITH_TIMEZONE #37021
• Closes: [Java][JDBC] Converting TIMESTAMP_WITH_TIMEZONE #37021

[github-actions]

Thanks for opening a pull request!

If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose

Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project.

Then could you also rename the pull request title in the following format?

GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

or

MINOR: [${COMPONENT}] ${SUMMARY}

In the case of PARQUET issues on JIRA the title also supports:

PARQUET-${JIRA_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

See also:

• Other pull requests
• Contribution Guidelines - How to contribute patches

[github-actions]

⚠️ GitHub issue #37021 has been automatically assigned in GitHub to PR creator.

[lidavidm]

Thanks!

[lidavidm]

Looks like a static analysis failure:

Error:  /arrow/java/adapter/jdbc/src/main/java/org/apache/arrow/adapter/jdbc/JdbcToArrowConfig.java:[201,8] error: [ChainingConstructorIgnoresParameter] The called constructor accepts a parameter with the same name and type as one of its caller's parameters, but its caller doesn't pass that parameter to it.  It's likely that it was intended to.
Error:      (see https://errorprone.info/bugpattern/ChainingConstructorIgnoresParameter)
Error:    Did you mean 'explicitTypesByColumnIndex,'?
Error:  -> [Help 1]

[lidavidm]

Thanks!

[lidavidm]

Hmm, it's not clear why, but CI is failing - does the test suite pass for you?

[aiguofer]

Hmm no... it is hanging on TestFlightSql.testGetTablesResultFilteredWithSchema, trying to track it down.

[aiguofer]

ahh tracked it down to an uncaught exception with unmapped JDBC types

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit 0e4fa8a.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about possible false positives for unstable benchmarks that are known to sometimes produce them.