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 2025/07/13 16:25:00 UTC

[jira] [Updated] (SPARK-52772) Inconsistent table attribute handling during updates

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

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

> Inconsistent table attribute handling during updates
> ----------------------------------------------------
>
>                 Key: SPARK-52772
>                 URL: https://issues.apache.org/jira/browse/SPARK-52772
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 4.1
>            Reporter: Kevin Beyer
>            Priority: Minor
>              Labels: pull-request-available
>
> TableOutputResolver is inconsistent in copying the table attribute metadata to the query columns.  For example, it does not copy for struct fields but does copy for primitives. 
> Adding a test case for a struct field to 
> InsertSuite.test("SPARK-40001 JSON DEFAULT columns = JSON_GENERATOR_WRITE_NULL_IF_WITH_DEFAULT_VALUE off).  
> exposes the bug.
> JacksonGenerator#writeFields depends on the attribute metadata from the query field to detect if a field has a default value.  It should instead look in the table columns.
> We should stop copying the metadata to the query fields in all cases.  Then fix any uses to use the table columns.
>  



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