This is an automated email from the ASF dual-hosted git repository.
alamb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/arrow-datafusion.git
The following commit(s) were added to refs/heads/master by this push:
new e8ea218b3 [MINOR] Update docs with newly added configuration values
(#3877)
e8ea218b3 is described below
commit e8ea218b3850f5ebf0272ffc122d51c1372ee196
Author: Andrew Lamb <[email protected]>
AuthorDate: Wed Oct 19 06:21:42 2022 -0400
[MINOR] Update docs with newly added configuration values (#3877)
---
docs/source/user-guide/configs.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/docs/source/user-guide/configs.md
b/docs/source/user-guide/configs.md
index 6794067bf..079cdacd1 100644
--- a/docs/source/user-guide/configs.md
+++ b/docs/source/user-guide/configs.md
@@ -40,6 +40,8 @@ Environment variables are read during `SessionConfig`
initialisation so they mus
| datafusion.execution.batch_size | UInt64 | 8192 |
Default batch size while creating new batches, it's especially useful for
buffer-in-memory batches since creating tiny batches would results in too much
metadata memory consumption.
|
| datafusion.execution.coalesce_batches | Boolean | true | When
set to true, record batches will be examined between each operator and small
batches will be coalesced into larger batches. This is helpful when there are
highly selective filters or joins that could produce tiny output batches. The
target batch size is determined by the configuration setting
'datafusion.execution.coalesce_target_batch_size'. |
| datafusion.execution.coalesce_target_batch_size | UInt64 | 4096 | Target
batch size when coalescing batches. Uses in conjunction with the configuration
setting 'datafusion.execution.coalesce_batches'.
|
+| datafusion.execution.time_zone | Utf8 | UTC | The
session time zone which some function require e.g. EXTRACT(HOUR from SOME_TIME)
shift the underline datetime according to the time zone,
|
+| then extract the hour |
| datafusion.explain.logical_plan_only | Boolean | false | When
set to true, the explain statement will only print logical plans.
|
| datafusion.explain.physical_plan_only | Boolean | false | When
set to true, the explain statement will only print physical plans.
|
| datafusion.optimizer.filter_null_join_keys | Boolean | false | When
set to true, the optimizer will insert filters before a join between a nullable
and non-nullable column to filter out nulls on the nullable side. This filter
can add additional overhead when the file format does not fully support
predicate push down.
|
