Asif created SPARK-52517:
----------------------------
Summary: Recent change of default value of nullable in
TransformingEncoder, from true to false, can cause issues
Key: SPARK-52517
URL: https://issues.apache.org/jira/browse/SPARK-52517
Project: Spark
Issue Type: Bug
Components: SQL
Affects Versions: 4.0.1
Reporter: Asif
Previously the default value of nullable in the TransformingEncoder was true,
which is now changed to false.
For fields in POJO/ Bean class which can only use Binary Serialization, the
TransformingEncoder that gets created has nullable as false.
Ideally the nullable notation on accessors should determine the type of
TransformingEncoder that gets created.
Some of the tests in the existing PR for spark bug
[https://issues.apache.org/jira/projects/SPARK/issues/SPARK-49789|https://issues.apache.org/jira/projects/SPARK/issues/SPARK-49789],
got impacted due to this. I have attempted to fix the issue in the PR for
SPARK-49789.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]