13.52. Release 0.191

Fix regression that could cause high CPU usage for join queries when dictionary processing for joins is enabled.
Fix for bits between 33 and 63.
The query.low-memory-killer.enabled config property has been replaced with query.low-memory-killer.policy. Use total-reservation to continue using the previous policy of killing the largest query. There is also a new policy, , which kills the query that is using the most memory on nodes that are out of memory (blocked).
Add support for grouped join execution. When both sides of a join have the same table partitioning and the partitioning is addressable, partial data can be loaded into memory at a time, making it possible to execute the join with less peak memory usage. The colocated join feature must be enabled with the colocated-joins-enabled config property or the colocated_join session property, and the concurrent_lifespans_per_task session property must be specified.
Allow connectors to report the amount of physical written data.

Resource Groups Changes

Add query type to the exact match source selector in the DB resource group selectors.

Add support for grouped join execution for Hive tables when both sides of a join have the same bucketing property.
Report physical written data for the legacy RCFile writer, optimized RCFile writer, and optimized ORC writer. These writers thus support writer scaling, which can both reduce the number of written files and create larger files. This is especially important for tables that have many small partitions, as small files can take a disproportionately longer time to read.