kumarUjjawal opened a new pull request, #21754:
URL: https://github.com/apache/datafusion/pull/21754
## 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.
-->
- Part of #20585.
## Rationale for this change
`substr_index` is part of the Utf8View epic. This function was still missing
the Utf8View optimization path, and it also did extra work when delimiter and
count were constant scalars.
This PR adds the same kind of optimization used in similar string work and
includes benchmark coverage.
<!--
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?
- Return the input string type directly, including `Utf8View`.
- Add a zero-copy `Utf8View` path for `substr_index`.
- Add a scalar fast path when delimiter and count are constant.
- Keep the hot path specialized after checking a cleaner shared-helper
version and benchmarking it.
- Add SQL coverage for `Utf8View` type and value results.
- Add unit tests for the scalar fast path, sliced `Utf8View` arrays, and
the unchanged original-view case.
- Extend the benchmark to cover `Utf8`, `Utf8View`, array arguments,
scalar delimiter/count, and positive and negative counts.
<!--
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?
Yes
<!--
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?
No
<!--
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.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
