You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2018/07/02 19:08:00 UTC

[jira] [Assigned] (SPARK-24673) scala sql function from_utc_timestamp second argument could be Column instead of String

     [ https://issues.apache.org/jira/browse/SPARK-24673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Apache Spark reassigned SPARK-24673:
------------------------------------

    Assignee:     (was: Apache Spark)

> scala sql function from_utc_timestamp second argument could be Column instead of String
> ---------------------------------------------------------------------------------------
>
>                 Key: SPARK-24673
>                 URL: https://issues.apache.org/jira/browse/SPARK-24673
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.3.1
>            Reporter: Antonio Murgia
>            Priority: Minor
>
> As of 2.3.1 the scala API for the built-in function from_utc_timestamp (org.apache.spark.sql.functions#from_utc_timestamp) is less powerful than its SQL counter part. In particular, given a dataset/dataframe with the following schema:
> {code:java}
> CREATE TABLE MY_TABLE (
>   ts TIMESTAMP,
>   tz STRING
> ){code}
> from the SQL api I can do something like:
> {code:java}
> SELECT FROM_UTC_TIMESTAMP(TS, TZ){code}
> while from the programmatic api I simply cannot because
> {code:java}
> functions.from_utc_timestamp(ts: Column, tz: String){code}
> second argument is a String.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org