Skip to content

[fix](function) Support bracketed IPv6 in parse_url - #67382

Open
Mryange wants to merge 1 commit into
apache:masterfrom
Mryange:fix-parse-url-ipv6
Open

[fix](function) Support bracketed IPv6 in parse_url#67382
Mryange wants to merge 1 commit into
apache:masterfrom
Mryange:fix-parse-url-ipv6

Conversation

@Mryange

@Mryange Mryange commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Problem Summary: parse_url treated colons inside bracketed IPv6 literals as port separators, producing incorrect HOST and PORT results. The FE constant-folding and BE execution paths now recognize the closing bracket as the host boundary and only parse a port after ]:.

Release note

Support extracting HOST and PORT from URLs containing bracketed IPv6 literals.

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

### What problem does this PR solve?

Issue Number: N/A

Problem Summary: parse_url treated every colon in a bracketed IPv6 literal as a port separator, so HOST and PORT returned incorrect values. Recognize the closing bracket as the IPv6 host boundary in both FE constant folding and BE execution.

### Release note

Support extracting HOST and PORT from URLs containing bracketed IPv6 literals.

### Check List (For Author)

- Test: Regression test / Unit Test / Manual test
- Behavior changed: Yes. parse_url now handles bracketed IPv6 hosts.
- Does this need documentation: No
@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?

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