Uh oh!
There was an error while loading. Please reload this page.
Add LogicalSystemLimit automatically for data-intensive operations - #3749
Add LogicalSystemLimit automatically for data-intensive operations#3749LantaoJin wants to merge 13 commits into
Conversation
Signed-off-by: Lantao Jin <ltjin@amazon.com>
Signed-off-by: Lantao Jin <ltjin@amazon.com>
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Signed-off-by: Lantao Jin <ltjin@amazon.com>
qianheng-aws
commented
Jun 10, 2025
|
Uh oh!
There was an error while loading. Please reload this page.
Signed-off-by: Lantao Jin <ltjin@amazon.com>
Signed-off-by: Lantao Jin <ltjin@amazon.com>
Signed-off-by: Lantao Jin <ltjin@amazon.com>
LantaoJin
commented
Jun 11, 2025
@penghuo@qianheng-aws@dai-chen I have updated the description with new code refactor, and docs. please take another look. |
This PR is stalled because it has been open for 30 days with no activity. |
RyanL1997
commented
Aug 19, 2025
Hi @LantaoJin , is this still requred? |
This PR is stalled because it has been open for 30 days with no activity. |
LantaoJin
commented
Oct 10, 2025
Close as there is a new alternative PR #4501 |
Description
From v3.0.0, PPL introduces commands that may increase data volume. To prevent out-of-memory problem, the system automatically enforces a
LogicalSystemLimitoperator for such commands.plugins.query.system_limit: The size configures the maximum of rows in the subsearch to data-intensive operations against (e.g. join, lookup). The default value is: 50000. Value range is from 0 to 2147483647 (Int.MaxValue).Update
Now, all PPL join/lookup/expand commands (data-bloat) will be affected by this PR. In future, we can add more command argument to control specific command.
For Join, when join type is
LogicalSystemLimitoperator to left side (main-search)LogicalSystemLimitoperator to right side (sub-search)For Lookup
LogicalSystemLimitoperator to right side (sub-search)For expand
LogicalSystemLimitoperator to right side (sub-search)The results of impacted search (for example, the lookup table of lookup command, right side of inner join, etc.)
cannot exceed the limitation (50000 rows by default). If the actual number of rows in lookup table or right side
of inner join is greater then the system limit, only the number of rows specified by the configuration will be searched.
You can set the configuration to the maximum integer value (2147483647) if you are certain resources are not a concern.
Related Issues
Resolves#3731
Check List
--signoff.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.