feat: Support for StringSplit

[Shekharrajak]

Fixes #2707

We have scalar function:
https://datafusion.apache.org/user-guide/sql/scalar_functions.html#string-to-array

[comphead]

Thanks @Shekharrajak for you contribution, please add a function to the fuzztesting kit, similar to #2755

[mbutrovich]

In the past I think we've encountered differences in Java and Rust's regex engines wrt graphemes. Could we get some larger UTF-8 characters in the tests?

[andygrove]

In the past I think we've encountered differences in Java and Rust's regex engines wrt graphemes. Could we get some larger UTF-8 characters in the tests?

We probably need to fall back to Spark unless this config is enabled:

  val COMET_REGEXP_ALLOW_INCOMPATIBLE: ConfigEntry[Boolean] =
    conf("spark.comet.regexp.allowIncompatible")
      .category(CATEGORY_EXEC)
      .doc("Comet is not currently fully compatible with Spark for all regular expressions. " +
        s"Set this config to true to allow them anyway. $COMPAT_GUIDE.")
      .booleanConf
      .createWithDefault(false)

[Shekharrajak]

Thanks @Shekharrajak for you contribution, please add a function to the fuzztesting kit, similar to #2755

Thanks! Added in commit 8eddd29

[Shekharrajak]

In the past I think we've encountered differences in Java and Rust's regex engines wrt graphemes. Could we get some larger UTF-8 characters in the tests?

Added tests 987b646

[Shekharrajak]

In the past I think we've encountered differences in Java and Rust's regex engines wrt graphemes. Could we get some larger UTF-8 characters in the tests?

We probably need to fall back to Spark unless this config is enabled:

  val COMET_REGEXP_ALLOW_INCOMPATIBLE: ConfigEntry[Boolean] =
    conf("spark.comet.regexp.allowIncompatible")
      .category(CATEGORY_EXEC)
      .doc("Comet is not currently fully compatible with Spark for all regular expressions. " +
        s"Set this config to true to allow them anyway. $COMPAT_GUIDE.")
      .booleanConf
      .createWithDefault(false)

How can we check if it is not falling back to Spark's JVM execution? @andygrove

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.03%. Comparing base (f09f8af) to head (e7b267b).
⚠️ Report is 918 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #2772      +/-   ##
============================================
+ Coverage     56.12%   60.03%   +3.90%     
- Complexity      976     1428     +452     
============================================
  Files           119      170      +51     
  Lines         11743    15809    +4066     
  Branches       2251     2608     +357     
============================================
+ Hits           6591     9491    +2900     
- Misses         4012     5000     +988     
- Partials       1140     1318     +178     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[kazuyukitanimura]

Thanks @Shekharrajak
Looks like there are rust check failures
https://github.com/apache/datafusion-comet/actions/runs/19441578149/job/55638326879?pr=2772

Perhaps you can try cargo fix?

[Shekharrajak]

Perhaps you can try cargo fix?

I ran but I am not sure why the checks keep failing

[Shekharrajak]

Please trigger the workflow.

[Shekharrajak]

All checks are looking fine. This is ready to merge.

[Shekharrajak]

Updated the branch with latest main branch. Please trigger the workflow