This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/arrow-datafusion.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 358c46291c Publish built docs triggered by 
d7ca9773f697db0f12f22c60ac7dc142fbefe5d1
358c46291c is described below

commit 358c46291c84325528fb28dc4ce8ddd69c9d9f82
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Thu Apr 20 12:13:55 2023 +0000

    Publish built docs triggered by d7ca9773f697db0f12f22c60ac7dc142fbefe5d1
---
 _sources/user-guide/configs.md.txt | 2 +-
 searchindex.js                     | 2 +-
 user-guide/configs.html            | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/_sources/user-guide/configs.md.txt 
b/_sources/user-guide/configs.md.txt
index dc21c81942..4b754bcd8a 100644
--- a/_sources/user-guide/configs.md.txt
+++ b/_sources/user-guide/configs.md.txt
@@ -63,7 +63,7 @@ Environment variables are read during `SessionConfig` 
initialisation so they mus
 | datafusion.optimizer.allow_symmetric_joins_without_pruning | true       | 
Should DataFusion allow symmetric hash joins for unbounded data sources even 
when its inputs do not have any ordering or filtering If the flag is not 
enabled, the SymmetricHashJoin operator will be unable to prune its internal 
buffers, resulting in certain join types - such as Full, Left, LeftAnti, 
LeftSemi, Right, RightAnti, and RightSemi - being produced only at the end of 
the execution. This is not typical in  [...]
 | datafusion.optimizer.repartition_file_scans                | true       | 
When set to true, file groups will be repartitioned to achieve maximum 
parallelism. Currently supported only for Parquet format in which case multiple 
row groups from the same file may be read concurrently. If false then each row 
group is read serially, though different files may be read in parallel.         
                                                                                
                           [...]
 | datafusion.optimizer.repartition_windows                   | true       | 
Should DataFusion repartition data using the partitions keys to execute window 
functions in parallel using the provided `target_partitions` level              
                                                                                
                                                                                
                                                                                
                  [...]
-| datafusion.optimizer.repartition_sorts                     | true       | 
Should DataFusion execute sorts in a per-partition fashion and merge afterwards 
instead of coalescing first and sorting globally. With this flag is enabled, 
plans in the form below "SortExec: [a@0 ASC]", " CoalescePartitionsExec", " 
RepartitionExec: partitioning=RoundRobinBatch(8), input_partitions=1", would 
turn into the plan below which performs better in multithreaded environments 
"SortPreservingMergeExec: [a@ [...]
+| datafusion.optimizer.repartition_sorts                     | true       | 
Should DataFusion execute sorts in a per-partition fashion and merge afterwards 
instead of coalescing first and sorting globally. With this flag is enabled, 
plans in the form below `text "SortExec: [a@0 ASC]", " CoalescePartitionsExec", 
" RepartitionExec: partitioning=RoundRobinBatch(8), input_partitions=1", ` 
would turn into the plan below which performs better in multithreaded 
environments `text "SortPreserving [...]
 | datafusion.optimizer.skip_failed_rules                     | true       | 
When set to true, the logical plan optimizer will produce warning messages if 
any optimization rules produce errors and then proceed to the next rule. When 
set to false, any rules that produce errors will cause the query to fail        
                                                                                
                                                                                
                     [...]
 | datafusion.optimizer.max_passes                            | 3          | 
Number of times that the optimizer will attempt to optimize the plan            
                                                                                
                                                                                
                                                                                
                                                                                
                 [...]
 | datafusion.optimizer.top_down_join_key_reordering          | true       | 
When set to true, the physical plan optimizer will run a top down process to 
reorder the join keys                                                           
                                                                                
                                                                                
                                                                                
                    [...]
diff --git a/searchindex.js b/searchindex.js
index be9dac5142..5c1e800c0b 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["contributor-guide/architecture", 
"contributor-guide/communication", "contributor-guide/index", 
"contributor-guide/quarterly_roadmap", "contributor-guide/roadmap", 
"contributor-guide/specification/index", 
"contributor-guide/specification/invariants", 
"contributor-guide/specification/output-field-name-semantic", "index", 
"user-guide/cli", "user-guide/configs", "user-guide/dataframe", 
"user-guide/example-usage", "user-guide/expressions", "user-guide/faq", "use 
[...]
\ No newline at end of file
+Search.setIndex({"docnames": ["contributor-guide/architecture", 
"contributor-guide/communication", "contributor-guide/index", 
"contributor-guide/quarterly_roadmap", "contributor-guide/roadmap", 
"contributor-guide/specification/index", 
"contributor-guide/specification/invariants", 
"contributor-guide/specification/output-field-name-semantic", "index", 
"user-guide/cli", "user-guide/configs", "user-guide/dataframe", 
"user-guide/example-usage", "user-guide/expressions", "user-guide/faq", "use 
[...]
\ No newline at end of file
diff --git a/user-guide/configs.html b/user-guide/configs.html
index 3301314499..82c2381f1d 100644
--- a/user-guide/configs.html
+++ b/user-guide/configs.html
@@ -448,7 +448,7 @@ Environment variables are read during <code class="docutils 
literal notranslate"
 </tr>
 <tr class="row-even"><td><p>datafusion.optimizer.repartition_sorts</p></td>
 <td><p>true</p></td>
-<td><p>Should DataFusion execute sorts in a per-partition fashion and merge 
afterwards instead of coalescing first and sorting globally. With this flag is 
enabled, plans in the form below “SortExec: [a&#64;0 ASC]”, “ 
CoalescePartitionsExec”, “ RepartitionExec: partitioning=RoundRobinBatch(8), 
input_partitions=1”, would turn into the plan below which performs better in 
multithreaded environments “SortPreservingMergeExec: [a&#64;0 ASC]”, “ 
SortExec: [a&#64;0 ASC]”, “ RepartitionExec: parti [...]
+<td><p>Should DataFusion execute sorts in a per-partition fashion and merge 
afterwards instead of coalescing first and sorting globally. With this flag is 
enabled, plans in the form below <code class="docutils literal 
notranslate"><span class="pre">text</span> <span 
class="pre">&quot;SortExec:</span> <span class="pre">[a&#64;0</span> <span 
class="pre">ASC]&quot;,</span> <span class="pre">&quot;</span> <span 
class="pre">CoalescePartitionsExec&quot;,</span> <span 
class="pre">&quot;</span>  [...]
 </tr>
 <tr class="row-odd"><td><p>datafusion.optimizer.skip_failed_rules</p></td>
 <td><p>true</p></td>

Reply via email to