starrocks
starrocks copied to clipboard
[BugFix] Byte pass through not effect when using fqdn in k8s environment
Why I'm doing:
What I'm doing:
Fixes #29677
What type of PR is this:
- [X] BugFix
- [ ] Feature
- [ ] Enhancement
- [ ] Refactor
- [ ] UT
- [ ] Doc
- [ ] Tool
Does this PR entail a change in behavior?
- [ ] Yes, this PR will result in a change in behavior.
- [x] No, this PR will not result in a change in behavior.
If yes, please specify the type of change:
- [ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
- [ ] Parameter changes: default values, similar parameters but with different default values
- [ ] Policy changes: use new policy to replace old one, functionality automatically enabled
- [ ] Feature removed
- [ ] Miscellaneous: upgrade & downgrade compatibility, etc.
Checklist:
- [ ] I have added test cases for my bug fix or my new feature
- [ ] This pr needs user documentation (for new or modified features or behaviors)
- [ ] I have added documentation for my new feature or new function
- [ ] This is a backport pr
Bugfix cherry-pick branch check:
- [X] I have checked the version labels which the pr will be auto-backported to the target branch
- [x] 3.3
- [x] 3.2
- [X] 3.1
- [ ] 3.0
- [ ] 2.5
[BE Incremental Coverage Report]
:x: fail : 3 / 6 (50.00%)
file detail
| path | covered_line | new_line | coverage | not_covered_line_detail | |
|---|---|---|---|---|---|
| :large_blue_circle: | be/src/exec/pipeline/exchange/exchange_sink_operator.cpp | 3 | 6 | 50.00% | [176, 177, 178] |
@mergifyio rebase
rebase
✅ Branch has been successfully rebased
[FE Incremental Coverage Report]
:white_check_mark: pass : 0 / 0 (0%)
Hey, any reason this was not merged?
closed via #57310