hutiefang76 opened a new pull request, #1391:
URL: https://github.com/apache/arrow-java/pull/1391

   ## What's Changed
   
   `DatabaseMetaData.getTypeInfo()` currently inherits an empty result, even 
when the Flight SQL server exposes type metadata. Forward it to 
`GetXdbcTypeInfo` and map the response to the 18 JDBC columns. Preserve server 
row order and SQL NULLs, convert parameter lists to strings and the JDBC 
short-valued fields to SMALLINT, and retain the standard column schema for an 
empty stream.
   
   Real in-process Flight client/server tests cover multiple batches, unknown 
precision, NULL versus empty parameter lists, empty results, server failures 
and allocator cleanup after normal or early close. The change stays in the JDBC 
metadata bridge and its fixtures.
   
   Validation on macOS arm64, JDK 21.0.10, using the repository-pinned Arrow 
test data:
   - Nine focused tests: eight fail on unchanged production; all nine pass with 
this patch, with no skips.
   - `mvn -B -ntp -Dmaven.gitcommitid.nativegit=true -pl 
flight/flight-sql,flight/flight-sql-jdbc-core,flight/flight-sql-jdbc-driver -am 
verify` passed, including Spotless, Checkstyle and the dependency reactor. 
Flight SQL: 97 tests; JDBC Core: 1253 tests, 44 existing skips; packaged driver 
validation: 2 integration tests. Dependency modules retain their existing 
conditional skips.
   - The first full attempt failed the unchanged 
`ResultSetTest.testFallbackUnresolvableFlightServer` timing assertion (second 
attempt took 5015 ms). One complete rerun passed without changing source, 
configuration or thresholds.
   
   Closes #1382.
   
   Maintainer note: please add the `enhancement` label; my account has not had 
label permissions in this repository. Upstream CI and review remain pending.
   
   <sub>AI-generated patch and PR description using Codex and DeepSeek, with 
automated review by DeepSeek. The builds and test results above were executed 
locally.</sub>
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to