MaxGekk commented on code in PR #56094:
URL: https://github.com/apache/spark/pull/56094#discussion_r3296569215
##########
sql/catalyst/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala:
##########
@@ -647,15 +647,19 @@ object SQLConf {
val TIMESTAMP_NANOS_TYPES_ENABLED =
buildConf("spark.sql.timestampNanosTypes.enabled")
.internal()
- .doc("When true, the parameterized nanosecond-precision timestamp types
" +
- "TIMESTAMP_NTZ(p) / TIMESTAMP_LTZ(p) for p in [7, 9] are recognized as
" +
- "Spark SQL data types at user-facing entry points. Default is false
because " +
- "downstream execution paths (Cast, PhysicalDataType, AnyTimestampType,
encoders, " +
- "Connect proto) are not yet wired for these types. See SPARK-56822.")
+ .doc("When true, allows nanosecond-capable timestamp types
TIMESTAMP_NTZ(p) and " +
+ "TIMESTAMP_LTZ(p) with fractional seconds precision p in [7, 9] at
user-facing " +
+ "entry points, including the SQL parser, schemas, and analyzed plans.
This is a " +
+ "preview feature under SPARK-56822 and may change in future releases.
The default is " +
+ "false in production; tests enable it by default via Utils.isTesting.
" +
+ "Unparameterized TIMESTAMP, TIMESTAMP_NTZ, and TIMESTAMP_LTZ remain
microsecond " +
+ "types. Enabling this flag does not guarantee full SQL support: casts,
Parquet read, " +
+ "typed literals, and other operations may still fail until their
respective features " +
+ "are implemented.")
.version("4.2.0")
Review Comment:
@HyukjinKwon @cloud-fan @dongjoon-hyun I merged this config to master, will
it be released in 4.2.0? Should I merge new features to branch-4.x?
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
