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/01/30 19:20:00 UTC

[jira] [Updated] (SPARK-51042) Read and write CalendarIntervals using one call to get/putLong consistently

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

ASF GitHub Bot updated SPARK-51042:
-----------------------------------
    Labels: big-endian pull-request-available  (was: big-endian)

> Read and write CalendarIntervals using one call to get/putLong consistently
> ---------------------------------------------------------------------------
>
>                 Key: SPARK-51042
>                 URL: https://issues.apache.org/jira/browse/SPARK-51042
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 4.0.0, 3.5.4
>            Reporter: Jonathan Albrecht
>            Priority: Minor
>              Labels: big-endian, pull-request-available
>
> In commit ac07cea234f4fb687442aafa8b6d411695110a4e there was a performance improvement to reading a writing CalendarIntervals in UnsafeRow. This same change can be applied to UnsafeArrayData and UnsafeWriter.
> This would also fix big endian platforms where the current and proposed methods of reading and writing CalendarIntervals do not order the bytes in the same way. Currently CalendarInterval related tests in Catalyst and SQL are failing on big endian platforms.
> There would be no effect on little endian platforms (byte order is not affected) except for performance improvement.



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