You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Joan Goyeau (Jira)" <ji...@apache.org> on 2023/10/05 00:46:00 UTC
[jira] [Commented] (SPARK-44408) Remove/Reduce usage of TypeTag in public APIs
[ https://issues.apache.org/jira/browse/SPARK-44408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17772038#comment-17772038 ]
Joan Goyeau commented on SPARK-44408:
-------------------------------------
I'm linking here some work that has been done to support Scala 3 in the current Spark (Scala 2.13) [https://github.com/vincenzobaz/spark-scala3]
> Remove/Reduce usage of TypeTag in public APIs
> ---------------------------------------------
>
> Key: SPARK-44408
> URL: https://issues.apache.org/jira/browse/SPARK-44408
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 4.0.0
> Reporter: Emil Ejbyfeldt
> Priority: Major
>
> In scala 3 there is no replacement for TypeTag ([https://github.com/lampepfl/dotty-feature-requests/issues/62)] it seems like the intended replacement is just to do compile time reflection using macros.
> In order to be able to make a scala 3 compatible release of spark 4 we should reduce/remove usage of TypeTag in public APis like `org.apache.spark.sql.functions.udf` instead I suggest that it would be better it just required a `ExpressionEncoder` (or some other spark owned type class) directly. That why we would just need to provide a scala 3 specific way only for the type class derivation and not for the other APIs that are currently using TypeTag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org