You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/08/30 20:15:00 UTC

[jira] [Updated] (SPARK-49476) Base64 nullability change

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

ASF GitHub Bot updated SPARK-49476:
-----------------------------------
    Labels: pull-request-available  (was: )

> Base64 nullability change
> -------------------------
>
>                 Key: SPARK-49476
>                 URL: https://issues.apache.org/jira/browse/SPARK-49476
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 4.0.0, 3.5.2
>            Reporter: Adam Binford
>            Priority: Major
>              Labels: pull-request-available
>
> In [https://github.com/apache/spark/pull/47303] , the Base64 function was updated to use `StaticInvoke` instead of directly calling the underlying encode function. This change also updated Base64 of a non-nullable child to be nullable instead of non-nullable. This was backported to Spark 3.5 as well ([https://github.com/apache/spark/pull/47325)] and has caused issues with failing state schema checks for stateful streaming jobs. This should be fixed to have the nullability based on the child.



--
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