You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2019/09/22 08:01:00 UTC
[jira] [Resolved] (SPARK-29200) Optimize `extract`/`date_part` for
epoch
[ https://issues.apache.org/jira/browse/SPARK-29200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-29200.
----------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
Issue resolved by pull request 25881
[https://github.com/apache/spark/pull/25881]
> Optimize `extract`/`date_part` for epoch
> ----------------------------------------
>
> Key: SPARK-29200
> URL: https://issues.apache.org/jira/browse/SPARK-29200
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Maxim Gekk
> Assignee: Maxim Gekk
> Priority: Minor
> Fix For: 3.0.0
>
>
> The method `DateTimeUtils.getEpoch()` can be speeded up by avoiding decimal operations and converting shifted by time zone timestamp to decimal at the end. Results of `ExtractBenchmark` should be regenerated as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org