[TEST] Add release notes for 0.254 #16165
Closed
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.
Missing Release Notes
Abhisek Gautam Saikia
Akhil Umesh Mehendale
Mayank Garg
WAITING_FOR_PREREQUISITES
Tal Galili
Tim Meehan
Vic Zhang
guhanjie
Extracted Release Notes
/connector/hive
./connector/hive
./connector/hive
./connector/hive
.PER_QUERY_MEMORY_LIMIT
and instead add configuration propertyexperimental.query-limit-spill-enabled
and session propertyquery_limit_spill_enabled
. When this property is set totrue
, and the spill strategy is notPER_TASK_MEMORY_THRESHOLD
, then we will spill whenever a query uses more than the per-node total memory limit in combined revocable and non-revocable memory, in addition to whenever the memory pool exceeds the spill threshold. This fixes an issue where using thePER_QUERY_MEMORY_LIMIT
spilling strategy could prevent the oom killer from running when the memory pool was full. The issue is still present for thePER_TASK_MEMORY_THRESHOLD
spilling strategy.PER_QUERY_MEMORY_LIMIT
and instead add configuration propertyexperimental.query-limit-spill-enabled
and session propertyquery_limit_spill_enabled
. When this property is set totrue
, and the spill strategy is notPER_TASK_MEMORY_THRESHOLD
, then we will spill whenever a query uses more than the per-node total memory limit in combined revocable and non-revocable memory, in addition to whenever the memory pool exceeds the spill threshold. This fixes an issue where using thePER_QUERY_MEMORY_LIMIT
spilling strategy could prevent the oom killer from running when the memory pool was full. The issue is still present for thePER_TASK_MEMORY_THRESHOLD
spilling strategy.PER_QUERY_MEMORY_LIMIT
and instead add configuration propertyexperimental.query-limit-spill-enabled
and session propertyquery_limit_spill_enabled
. When this property is set totrue
, and the spill strategy is notPER_TASK_MEMORY_THRESHOLD
, then we will spill whenever a query uses more than the per-node total memory limit in combined revocable and non-revocable memory, in addition to whenever the memory pool exceeds the spill threshold. This fixes an issue where using thePER_QUERY_MEMORY_LIMIT
spilling strategy could prevent the oom killer from running when the memory pool was full. The issue is still present for thePER_TASK_MEMORY_THRESHOLD
spilling strategy.PER_QUERY_MEMORY_LIMIT
and instead add configuration propertyexperimental.query-limit-spill-enabled
and session propertyquery_limit_spill_enabled
. When this property is set totrue
, and the spill strategy is notPER_TASK_MEMORY_THRESHOLD
, then we will spill whenever a query uses more than the per-node total memory limit in combined revocable and non-revocable memory, in addition to whenever the memory pool exceeds the spill threshold. This fixes an issue where using thePER_QUERY_MEMORY_LIMIT
spilling strategy could prevent the oom killer from running when the memory pool was full. The issue is still present for thePER_TASK_MEMORY_THRESHOLD
spilling strategy.table-finish-operator-memory-tracking-enabled
configuration property totrue
.hive.partition-cache-validation-percentage
configuration parameter.16039
.All Commits
WAITING_FOR_PREREQUISITES
(Mayank Garg)