[
https://issues.apache.org/jira/browse/SPARK-57840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Max Gekk updated SPARK-57840:
-----------------------------
Shepherd: Max Gekk
> Add nanosecond-precision timestamp support to the Spark Connect JDBC client
> ---------------------------------------------------------------------------
>
> Key: SPARK-57840
> URL: https://issues.apache.org/jira/browse/SPARK-57840
> Project: Spark
> Issue Type: Sub-task
> Components: Connect
> Affects Versions: 4.3.0
> Reporter: Max Gekk
> Priority: Major
>
> This sub-task is part of the umbrella SPARK-56822 (timestamps with nanosecond
> precision).
> h2. Problem
> The Spark Connect JDBC client's {{JdbcTypeUtils}}
> (sql/connect/client/jdbc/.../util/JdbcTypeUtils.scala ~L36-163) handles only
> {{TimestampType}} / {{TimestampNTZType}} and throws
> {{SQLFeatureNotSupportedException}} for other types, so nanosecond columns
> break JDBC metadata/typing over Connect. This is distinct from SPARK-57460
> (server-side JDBC datasource) and SPARK-57161 (Connect proto<->Catalyst).
> h2. Goal
> Map {{TimestampNTZNanosType}} / {{TimestampLTZNanosType}} in the Connect JDBC
> client type utilities (JDBC type code, type name, value accessors).
> h2. Scope
> Add nanosecond arms to {{JdbcTypeUtils}} (and any related ResultSet metadata
> mapping in the Connect JDBC client).
> h2. Acceptance criteria
> * Querying a nanosecond column through the Connect JDBC client returns
> correct JDBC metadata and values (as strings/timestamps consistent with the
> server rendering).
> h2. Testing
> Connect JDBC client tests.
> h2. Dependencies
> Blocked by SPARK-57161 (Connect proto<->Catalyst conversion, still open);
> relates to SPARK-57738 (Connect Arrow reader guard). Independent of
> SPARK-57460 (server JDBC datasource).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
