bart-samwel commented on pull request #28534: URL: https://github.com/apache/spark/pull/28534#issuecomment-629106064
This is a behavior change for existing Spark workloads. Even if the code is not compatible with Hive here, we shouldn't break existing workloads. See also the versioning [policy.](https://spark.apache.org/versioning-policy.html). If we really want to fix this, we would have to introduce a compatibility flag, and fail this construct by default so that people can choose. A better solution would be to introduce functions that are explicit about the meaning of their source operand. E.g. this is how it is [done in BigQuery](https://cloud.google.com/bigquery/docs/reference/standard-sql/timestamp_functions#timestamp_millis), with functions like `TIMESTAMP_MILLIS` to get a timestamp from a Unix miliseconds timestamp. @cloud-fan @MaxGekk FYI ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
