This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/datafusion.git


The following commit(s) were added to refs/heads/main by this push:
     new 4e2e4e84d5 fix: Df int timestamp cast fix failing CI  (#21163)
4e2e4e84d5 is described below

commit 4e2e4e84d501b0344ac7d4212c7f3b0f0ce05dd5
Author: Bhargava Vadlamani <[email protected]>
AuthorDate: Wed Mar 25 21:42:26 2026 -0700

    fix: Df int timestamp cast fix failing CI  (#21163)
    
    ## Which issue does this PR close?
    
    <!--
    We generally require a GitHub issue to be filed for all bug fixes and
    enhancements and this helps us generate change logs for our releases.
    You can link an issue to this PR using the GitHub syntax. For example
    `Closes #123` indicates that this PR will close issue #123.
    -->
    
    - Closes #.
    Fixes CI failures caused by PR :
    https://github.com/apache/datafusion/pull/20555
    ## Rationale for this change
    
    <!--
    Why are you proposing this change? If this is already explained clearly
    in the issue then this section is not needed.
    Explaining clearly why changes are proposed helps reviewers understand
    your changes and offer better suggestions for fixes.
    -->
    
    ## What changes are included in this PR?
    
    <!--
    There is no need to duplicate the description in the issue here but it
    is sometimes worth providing a summary of the individual changes in this
    PR.
    -->
    
    ## Are these changes tested?
    
    <!--
    We typically require tests for all PRs in order to:
    1. Prevent the code from being accidentally broken by subsequent changes
    2. Serve as another way to document the expected behavior of the code
    
    If tests are not included in your PR, please explain why (for example,
    are they covered by existing tests)?
    -->
    
    ## Are there any user-facing changes?
    
    <!--
    If there are user-facing changes then we may require documentation to be
    updated before approving the PR.
    -->
    
    <!--
    If there are any breaking changes to public APIs, please add the `api
    change` label.
    -->
---
 .../test_files/spark/conversion/cast_int_to_timestamp.slt           | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git 
a/datafusion/sqllogictest/test_files/spark/conversion/cast_int_to_timestamp.slt 
b/datafusion/sqllogictest/test_files/spark/conversion/cast_int_to_timestamp.slt
index 8b77533729..931f7c5d35 100644
--- 
a/datafusion/sqllogictest/test_files/spark/conversion/cast_int_to_timestamp.slt
+++ 
b/datafusion/sqllogictest/test_files/spark/conversion/cast_int_to_timestamp.slt
@@ -15,6 +15,8 @@
 # specific language governing permissions and limitations
 # under the License.
 
+# Tests for casting integer types to timestamp using spark_cast
+
 # Test spark_cast from int8 to timestamp
 query P
 SELECT spark_cast(arrow_cast(0, 'Int8'), 'timestamp');
@@ -189,7 +191,7 @@ SELECT spark_cast(1710057600::bigint, 'timestamp');
 ----
 2024-03-10T01:00:00-07:00
 
-# Reset to default UTC
+# Reset to default
 statement ok
 SET datafusion.execution.time_zone = 'UTC';
 
@@ -246,7 +248,7 @@ NULL NULL NULL NULL
 
 # Reset and cleanup
 statement ok
-SET datafusion.execution.time_zone = 'UTC';
+RESET datafusion.execution.time_zone;
 
 statement ok
 DROP TABLE int_test;


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to