apache/arrow-java

Flight JDBC Driver not setting parameter correctly when parameter type is DATE<MILLISECOND>

開放

#477 建立於 2025年1月3日

 (0 則留言) (0 個反應) (0 位負責人)Java (132 個分叉)auto 404
Type: bughelp wanted

倉庫指標

星標
 (89 顆星)
PR 合併指標
 (PR 指標待抓取)

描述

Describe the bug, including details regarding any error messages, version, and platform.

Arrow Version 17.0.0

When executing a prepared statement using the Arrow Flight JDBC driver, the driver sets the value for date parameters as DAYS since unix epoch, even when the parameter type returned by the server is DATE(MILLISECONDS).

https://github.com/apache/calcite-avatica/blob/2baa36e493cd90b89a6dec5cb04db0eefe6aef93/core/src/main/java/org/apache/calcite/avatica/util/DateTimeUtils.java#L1344-L1361

The parameter converter below sets the same value regardless of the type. This results in the server receiving an unexpected parameter value.

https://github.com/apache/arrow/blob/6a2e19a852b367c72d7b12da4d104456491ed8b7/java/flight/flight-sql-jdbc-core/src/main/java/org/apache/arrow/driver/jdbc/converter/impl/DateAvaticaParameterConverter.java#L33-L43

    Properties props = new Properties();
    String connection = "jdbc:arrow-flight-sql://xx:xx/?useEncryption=false";
    String query = "select date from T where date = ?";

    try (Connection con = DriverManager.getConnection(connection, props);
         PreparedStatement ps = con.prepareStatement(query)) {

      ps.setDate(1, Date.valueOf(LocalDate.of(2000, 1, 1)), null);

      try (ResultSet rs = ps.executeQuery()) {
        rs.next();
      }
    }

Component(s)

Java

貢獻者指南