Skip to content

branch-4.1: [fix](be) Reject super wildcard path in json keys #63300#63369

Open
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-63300-branch-4.1
Open

branch-4.1: [fix](be) Reject super wildcard path in json keys #63300#63369
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-63300-branch-4.1

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Cherry-picked from #63300

### What problem does this PR solve?

Issue Number: None

Related PR: None

Problem Summary: `json_keys`/`jsonb_keys` rejected ordinary wildcard
paths but allowed super wildcard paths such as $**.a to fall through and
return NULL. The function only supports reading keys from a single
object, so super wildcard paths should fail with the same
INVALID_JSON_PATH error as other wildcard paths.

### Release note

Reject unsupported super wildcard JSON paths in json_keys/jsonb_keys
instead of returning NULL.

### Check List (For Author)

- Test: Unit Test / Regression test / Static check
- Unit Test: ./run-be-ut.sh --run
--filter=FunctionJsonbTEST.JsonbKeysRejectSuperWildcardPath
- Regression test: Added
regression-test/suites/jsonb_p0/test_jsonb_keys_invalid_path.groovy (not
run locally; no FE/BE cluster was listening on configured regression
ports)
    - Static check: build-support/check-format.sh
- Static check: build-support/run-clang-tidy.sh --build-dir
be/ut_build_ASAN (failed due to pre-existing function_jsonb.cpp
complexity diagnostics and toolchain header/NOLINTEND errors)
- Behavior changed: Yes (json_keys/jsonb_keys now return
INVALID_JSON_PATH for $** paths instead of NULL)
- Does this need documentation: No
@github-actions github-actions Bot requested a review from yiguolei as a code owner May 18, 2026 13:11
@hello-stephen
Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@hello-stephen
Copy link
Copy Markdown
Contributor

run buildall

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants