Skip to content

branch-4.0: [bug](iceberg) mapping iceberg varint type to unsupported type #64331#64337

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

branch-4.0: [bug](iceberg) mapping iceberg varint type to unsupported type #64331#64337
github-actions[bot] wants to merge 1 commit into
branch-4.0from
auto-pick-64331-branch-4.0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #64331

### What problem does this PR solve?

```
mysql> select * from test_variant_repro;
ERROR 1105 (HY000): errCode = 2, detailMessage = IllegalArgumentException: Cannot transform unknown type: variant
mysql>
mysql> select id from test_variant_repro;
ERROR 1105 (HY000): errCode = 2, detailMessage = IllegalArgumentException: Cannot transform unknown type: variant
mysql>
```
now iceberg varint type not support in doris, so could mapping it to
unsupported type, this will not affect others columns,
eg, if only select id from table , it's could work well

Problem Summary:

### Release note

None

### Check List (For Author)

- Test <!-- At least one of them must be included. -->
    - [x] 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 <!-- Add your reason?  -->

- Behavior changed:
    - [x] No.
    - [ ] Yes. <!-- Explain the behavior change -->

- Does this need documentation?
    - [x] No.
- [ ] Yes. <!-- Add document PR link here. eg:
apache/doris-website#1214 -->

### Check List (For Reviewer who merge this PR)

- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label <!-- Add branch pick label that this PR
should merge into -->
@github-actions github-actions Bot requested a review from morningman as a code owner June 10, 2026 01:40
@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

@hello-stephen

Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage 0.00% (0/1) 🎉
Increment coverage report
Complete coverage report

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