[Bug] fix insert load should have the same behavior as stream load#7180
Closed
spaces-X wants to merge 3 commits intoapache:masterfrom
Closed
[Bug] fix insert load should have the same behavior as stream load#7180spaces-X wants to merge 3 commits intoapache:masterfrom
spaces-X wants to merge 3 commits intoapache:masterfrom
Conversation
morningman
reviewed
Nov 23, 2021
morningman
reviewed
Dec 1, 2021
| public long loadMemLimit = 0L; | ||
|
|
||
| @VariableMgr.VarAttr(name = INSERT_MAX_FILTER_RATIO) | ||
| public double insertMaxFilterRatio = 0L; |
Contributor
There was a problem hiding this comment.
The default should be 1.0, to be same as origin.
and please update the document:
docs/zh-CN/administrator-guide/variables.md
docs/en/administrator-guide/variables.md
6fcd7f6 to
65853d1
Compare
airborne12
added a commit
to airborne12/apache-doris
that referenced
this pull request
Feb 10, 2026
…s, and lower_case defaults Cherry-picked from jk-selectdb/hubspot branch (3 commits): 1. REGEXP lowercase fix (apache#7224): REGEXP patterns in search() are no longer lowercased, matching ES query_string behavior where regex queries match directly against the term dictionary without normalization. WILDCARD/PREFIX patterns are still lowercased. 2. Variant subcolumn index_properties: Pass index_properties from FE to BE via TSearchFieldBinding so variant subcolumn field_pattern indexes can resolve correct analyzer settings. 3. lower_case default fix (apache#7152, apache#7180): Only add lower_case=true default for built-in analyzers in to_schema_pb, not for custom analyzers where lowercase behavior is determined by the analyzer's internal token filter. Test: 113 SearchDslParser UTs + 12 SearchPredicateTest UTs pass. 5 existing search regression tests pass. test_search_variant_subcolumn_analyzer regression test passes. test_search_regexp_lowercase needs BE rebuild to pass (FE-only deploy).
airborne12
added a commit
to airborne12/apache-doris
that referenced
this pull request
Feb 10, 2026
…s, and lower_case defaults Cherry-picked from jk-selectdb/hubspot branch (3 commits): 1. REGEXP lowercase fix (apache#7224): REGEXP patterns in search() are no longer lowercased, matching ES query_string behavior where regex queries match directly against the term dictionary without normalization. WILDCARD/PREFIX patterns are still lowercased. 2. Variant subcolumn index_properties: Pass index_properties from FE to BE via TSearchFieldBinding so variant subcolumn field_pattern indexes can resolve correct analyzer settings. 3. lower_case default fix (apache#7152, apache#7180): Only add lower_case=true default for built-in analyzers in to_schema_pb, not for custom analyzers where lowercase behavior is determined by the analyzer's internal token filter. Test: 113 SearchDslParser UTs + 12 SearchPredicateTest UTs pass. 5 existing search regression tests pass. test_search_variant_subcolumn_analyzer regression test passes. test_search_regexp_lowercase needs BE rebuild to pass (FE-only deploy).
airborne12
added a commit
to airborne12/apache-doris
that referenced
this pull request
Feb 17, 2026
…s, and lower_case defaults Cherry-picked from jk-selectdb/hubspot branch (3 commits): 1. REGEXP lowercase fix (apache#7224): REGEXP patterns in search() are no longer lowercased, matching ES query_string behavior where regex queries match directly against the term dictionary without normalization. WILDCARD/PREFIX patterns are still lowercased. 2. Variant subcolumn index_properties: Pass index_properties from FE to BE via TSearchFieldBinding so variant subcolumn field_pattern indexes can resolve correct analyzer settings. 3. lower_case default fix (apache#7152, apache#7180): Only add lower_case=true default for built-in analyzers in to_schema_pb, not for custom analyzers where lowercase behavior is determined by the analyzer's internal token filter. Test: 113 SearchDslParser UTs + 12 SearchPredicateTest UTs pass. 5 existing search regression tests pass. test_search_variant_subcolumn_analyzer regression test passes. test_search_regexp_lowercase needs BE rebuild to pass (FE-only deploy).
Hastyshell
pushed a commit
to Hastyshell/doris
that referenced
this pull request
Feb 27, 2026
…ers in to_schema_pb (apache#7180) ## Proposed changes Issue Number: close #xxx <!--Describe your changes.--> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
see #7179
Types of changes
What types of changes does your code introduce to Doris?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...