From ae932e33479b1f1e7763a8e4dad698519aba8483 Mon Sep 17 00:00:00 2001 From: Manfred Moser Date: Tue, 1 Mar 2022 11:04:44 -0800 Subject: [PATCH] Clean up source formatting only --- .../sphinx/admin/properties-query-management.rst | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/src/main/sphinx/admin/properties-query-management.rst b/docs/src/main/sphinx/admin/properties-query-management.rst index 5ac378041ec7..194f11239849 100644 --- a/docs/src/main/sphinx/admin/properties-query-management.rst +++ b/docs/src/main/sphinx/admin/properties-query-management.rst @@ -12,14 +12,14 @@ Query management properties Configures the algorithm to organize the processing of all of the stages of a query. You can use the following execution policies: -* ``phased`` schedules stages in a sequence to avoid blockages because of - inter-stage dependencies. This policy maximizes cluster resource utilization +* ``phased`` schedules stages in a sequence to avoid blockages because of + inter-stage dependencies. This policy maximizes cluster resource utilization and provides the lowest query wall time. -* ``all-at-once`` schedules all of the stages of a query at one time. As a - result, cluster resource utilization is initially high, but inter-stage - dependencies typically prevent full processing and cause longer queue times +* ``all-at-once`` schedules all of the stages of a query at one time. As a + result, cluster resource utilization is initially high, but inter-stage + dependencies typically prevent full processing and cause longer queue times which increases the query wall time overall. -* ``legacy-phased`` has similar functionality to ``phased``, but can increase +* ``legacy-phased`` has similar functionality to ``phased``, but can increase the query wall time as it attempts to minimize the number of running stages. ``query.hash-partition-count`` @@ -29,8 +29,8 @@ stages of a query. You can use the following execution policies: * **Default value:** ``100`` * **Session property:** ``hash_partition_count`` -The number of partitions to use for processing distributed joins and -aggregations. +The number of partitions to use for processing distributed operations, such as +joins, aggregations, partitioned window functions and others. ``query.max-execution-time`` ^^^^^^^^^^^^^^^^^^^^^^^^^^^^