Skip to content

Allow empty needle in function replace#69918

Merged
vitlibar merged 8 commits intoClickHouse:masterfrom
bigo-sg:replace-empty-needle
Sep 27, 2024
Merged

Allow empty needle in function replace#69918
vitlibar merged 8 commits intoClickHouse:masterfrom
bigo-sg:replace-empty-needle

Conversation

@zhanglistar
Copy link
Copy Markdown
Contributor

@zhanglistar zhanglistar commented Sep 25, 2024

Changelog category (leave one):

  • Improvements

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Allow empty needle in function replace, the same behavior with PostgreSQL.

image

Documentation entry for user-facing changes

  • Documentation is written (mandatory for new features)

Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/

CI Settings (Only check the boxes if you know what you are doing):

  • Allow: All Required Checks
  • Allow: Stateless tests
  • Allow: Stateful tests
  • Allow: Integration Tests
  • Allow: Performance tests
  • Allow: All Builds
  • Allow: batch 1, 2 for multi-batch jobs
  • Allow: batch 3, 4, 5, 6 for multi-batch jobs

  • Exclude: Style check
  • Exclude: Fast test
  • Exclude: All with ASAN
  • Exclude: All with TSAN, MSAN, UBSAN, Coverage
  • Exclude: All with aarch64, release, debug

  • Run only fuzzers related jobs (libFuzzer fuzzers, AST fuzzers, etc.)
  • Exclude: AST fuzzers

  • Do not test
  • Woolen Wolfdog
  • Upload binaries for special builds
  • Disable merge-commit
  • Disable CI cache

@vitlibar vitlibar self-assigned this Sep 25, 2024
prev_haystack_offset = haystack_offsets[i];
prev_needle_offset = needle_offsets[i];
prev_replacement_offset = replacement_offsets[i];
continue;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's simplify the logic a bit. We can treat (cur_needle_length == 0) as if there is no match.
So instead of this change we could check if (cur_needle_length == 0) and skip the cycle while (start_pos < cur_haystack_end) along with the initialization of searcher if so.

@vitlibar
Copy link
Copy Markdown
Member

Allow empty needle in function replace, the same behavior with PostgreSQL.

Is it said somewhere? I mean I opened https://www.postgresql.org/docs/8.1/functions-string.html and didn't see there that replace(string, from, to) must return string if from is empty.

@zhanglistar
Copy link
Copy Markdown
Contributor Author

Allow empty needle in function replace, the same behavior with PostgreSQL.

Is it said somewhere? I mean I opened https://www.postgresql.org/docs/8.1/functions-string.html and didn't see there that replace(string, from, to) must return string if from is empty.

https://github.com/postgres/postgres/blob/2ceeb638b7b27da156c10cb9d5ea4f81cabda0d1/src/backend/utils/adt/varlena.c#L3992 Check here pls.

@vitlibar
Copy link
Copy Markdown
Member

vitlibar commented Sep 26, 2024

Allow empty needle in function replace, the same behavior with PostgreSQL.

Is it said somewhere? I mean I opened https://www.postgresql.org/docs/8.1/functions-string.html and didn't see there that replace(string, from, to) must return string if from is empty.

https://github.com/postgres/postgres/blob/2ceeb638b7b27da156c10cb9d5ea4f81cabda0d1/src/backend/utils/adt/varlena.c#L3992 Check here pls.

Ok, I checked https://onecompiler.com/mysql/42tbkn53z and it seems most DBMS handle replace(string, from, to) with empty from in the same way you as do in this PR.

@vitlibar vitlibar added the can be tested Allows running workflows for external contributors label Sep 26, 2024
@robot-ch-test-poll2 robot-ch-test-poll2 added the pr-backward-incompatible Pull request with backwards incompatible changes label Sep 26, 2024
@robot-ch-test-poll
Copy link
Copy Markdown
Contributor

robot-ch-test-poll commented Sep 26, 2024

This is an automated comment for commit 350b9c0 with description of existing statuses. It's updated for the latest CI running

✅ Click here to open a full report in a separate page

Successful checks
Check nameDescriptionStatus
AST fuzzerRuns randomly generated queries to catch program errors. The build type is optionally given in parenthesis. If it fails, ask a maintainer for help✅ success
BuildsThere's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS✅ success
ClickBenchRuns [ClickBench](https://github.com/ClickHouse/ClickBench/) with instant-attach table✅ success
Compatibility checkChecks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help✅ success
Docker keeper imageThe check to build and optionally push the mentioned image to docker hub✅ success
Docker server imageThe check to build and optionally push the mentioned image to docker hub✅ success
Docs checkBuilds and tests the documentation✅ success
Fast testNormally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here✅ success
Flaky testsChecks if new added or modified tests are flaky by running them repeatedly, in parallel, with more randomization. Functional tests are run 100 times with address sanitizer, and additional randomization of thread scheduling. Integration tests are run up to 10 times. If at least once a new test has failed, or was too long, this check will be red. We don't allow flaky tests, read the doc✅ success
Install packagesChecks that the built packages are installable in a clear environment✅ success
Integration testsThe integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests✅ success
Performance ComparisonMeasure changes in query performance. The performance test report is described in detail here. In square brackets are the optional part/total tests✅ success
Stateful testsRuns stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc✅ success
Stateless testsRuns stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc✅ success
Stress testRuns stateless functional tests concurrently from several clients to detect concurrency-related errors✅ success
Style checkRuns a set of checks to keep the code style clean. If some of tests failed, see the related log from the report✅ success
Unit testsRuns the unit tests for different release types✅ success
Upgrade checkRuns stress tests on server version from last release and then tries to upgrade it to the version from the PR. It checks if the new server can successfully startup without any errors, crashes or sanitizer asserts✅ success

if (needle.empty())
throw Exception(ErrorCodes::ARGUMENT_OUT_OF_BOUND, "Length of the pattern argument in function {} must be greater than 0.", name);
{
assert(input_rows_count == haystack_data.size() / n);
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

chassert() is better because it helps us to find problem when the code is run in our CI builds.
assert() is no-op in any release builds, whereas chassert() still works in release builds with sanitizers which we run in our CI.

assert(input_rows_count == haystack_data.size() / n);
/// Since ColumnFixedString does not have a zero byte at the end, while ColumnString does,
/// we need to split haystack_data into strings of length n, add 1 zero byte to the end of each string
/// and then copy to res_data, ref: ColumnString.h and ColumnFixedString.h
Copy link
Copy Markdown
Member

@vitlibar vitlibar Sep 26, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be nice to have a test with FixedString too

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you know how to construct a ColumnConst with string type without modifying code useDefaultImplementationForConstants = false ? I have tested with changing this code locally, it works expected.

Copy link
Copy Markdown
Member

@vitlibar vitlibar Sep 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Executing of the following query

select replace(materialize(toFixedString('abcdef', 6)), '', '01')

will lead to this part of code.

Though it's strange that a more simple query

select replace(toFixedString('abcdef', 6), '', '01')

just throws exception ILLEGAL_COLUMN.

@vitlibar
Copy link
Copy Markdown
Member

vitlibar commented Sep 26, 2024

Please fix your code to pass the Style check

@vitlibar vitlibar added this pull request to the merge queue Sep 27, 2024
Merged via the queue into ClickHouse:master with commit ec6bf0d Sep 27, 2024
@robot-ch-test-poll4 robot-ch-test-poll4 added the pr-synced-to-cloud The PR is synced to the cloud repo label Sep 27, 2024


SELECT 'Check that an exception is thrown if the needle is empty';
SELECT 'Check that whether an exception is thrown if the needle is empty';
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bad grammar, please replace by "Check what happens if the needle is empty".

SELECT s, replaceOne(s, '_', 'o') AS a, replaceRegexpOne(s, '_', 'o') AS b, a = b FROM (SELECT arrayJoin(['__.__', '.__']) AS s);
SELECT s, replaceOne(s, '_', 'o') AS a, replaceRegexpOne(s, '_', 'o') AS b, a = b FROM (SELECT arrayJoin(['__.__', '__.']) AS s);
SELECT s, replaceOne(s, '_', 'o') AS a, replaceRegexpOne(s, '_', 'o') AS b, a = b FROM (SELECT arrayJoin(['__.__', '__.__']) AS s);
SELECT replace('ABCabc', '', 'DEF');
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is way too dirty. We

  • should not have 101 lines with tests where _ is used as pattern, and then suddenly test empty needles without explanation or comment what is being tested
  • and, even worse, without any connection to the test name (we are not looping anything),
  • and on top, only test the alias "replace" but not test the actual functions "replaceOne" and "replaceAll".

@zhanglistar Please move l. 102 into a new test 00240_replace_with_empty_needle and address these points.

rschu1ze added a commit to rschu1ze/ClickHouse that referenced this pull request Oct 23, 2024
github-merge-queue bot pushed a commit that referenced this pull request Oct 23, 2024
@Algunenano Algunenano added pr-improvement Pull request with some product improvements and removed pr-backward-incompatible Pull request with backwards incompatible changes labels Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

can be tested Allows running workflows for external contributors pr-improvement Pull request with some product improvements pr-synced-to-cloud The PR is synced to the cloud repo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants