Skip to content

array_overlap correctness issue #3645

Closed

Description

@comphead

Describe the bug

Error executing SQL 'SELECT arrays_overlap(a, b) FROM test_arrays_overlap'

== Results ==
!== Correct Answer - 5 ==               == Spark Answer - 5 ==
 struct<arrays_overlap(a, b):boolean>   struct<arrays_overlap(a, b):boolean>
 [false]                                [false]
 [false]                                [false]
 [null]                                 [null]
![null]                                 [true]
 [true]                                 [true]

Steps to reproduce

No response

Expected behavior

No response

Additional context

No response

Activity

  1. andygrove commented on Mar 12, 2026

    @andygrove
    Member

    This may be a duplicate of #2036

  2. added a commit that references this issue on Mar 12, 2026
    c1b9f70
  3. added
    enhancementNew feature or request
    and removed
    bugSomething isn't working
    on Mar 27, 2026
  4. andygrove commented on Mar 27, 2026

    @andygrove
    Member

    This expression (ArraysOverlap) is now marked as Incompatible in Comet, which means it falls back to Spark by default and only runs natively when spark.comet.expr.allowIncompatible=true is explicitly set. Since default behavior is now correct (via Spark fallback), this is no longer a bug. Relabeling as an enhancement to track implementing compatible native behavior in the future.

  5. kazuyukitanimura commented on Apr 1, 2026

    @kazuyukitanimura
    Contributor

    Related #3175
    Related #3364

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions