This is an automated email from the ASF dual-hosted git repository. yzheng pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/polaris.git
The following commit(s) were added to refs/heads/main by this push:
new 2eed88556 Add doc for behavior change configuration (#3677)
2eed88556 is described below
commit 2eed88556abda41f11f7a02ab749d3c1002d94af
Author: Yong Zheng <[email protected]>
AuthorDate: Sat Feb 7 15:45:28 2026 -0600
Add doc for behavior change configuration (#3677)
---
site/content/in-dev/unreleased/configuration.md | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/site/content/in-dev/unreleased/configuration.md
b/site/content/in-dev/unreleased/configuration.md
index 0d3dd7314..1572b73e1 100644
--- a/site/content/in-dev/unreleased/configuration.md
+++ b/site/content/in-dev/unreleased/configuration.md
@@ -137,6 +137,12 @@ read-only mode, as Polaris only reads the configuration
file once, at startup.
| `polaris.features."AZURE_RETRY_JITTER_FACTOR"`
| `0.5` | Jitter factor (0.0 to 1.0)
applied to retry delays for Azure API requests. The jitter is applied as a
random percentage of the computed exponential backoff delay. For example, 0.5
means up to 50%% random jitter will be added to each retry delay. Helps prevent
thundering herd when multiple requests fail simultaneously.
[...]
| `polaris.features."TABLE_METADATA_CLEANUP_BATCH_SIZE"`
| `10` | Metadata batch size for tasks
that clean up dropped tables' files.
[...]
|
`polaris.features.realm-overrides."my-realm"."SKIP_CREDENTIAL_SUBSCOPING_INDIRECTION"`
| `true` | "Override" realm features, here the
skip credential subscoping indirection flag.
[...]
+| `polaris.features."VALIDATE_VIEW_LOCATION_OVERLAP"`
| `true` | If true, validate that view
locations don't overlap when views are created.
[...]
+| `polaris.features."STORAGE_CONFIGURATION_MAX_LOCATIONS"`
| `-1` | How many locations can be
associated with a storage configuration, or -1 for unlimited locations.
[...]
+| `polaris.features."ENTITY_CACHE_SOFT_VALUES"`
| `false` | Whether or not to use soft
values in the entity cache.
[...]
+| `polaris.features."TABLE_OPERATIONS_MAKE_METADATA_CURRENT_ON_COMMIT"`
| `true` | If true,
BasePolarisTableOperations should mark the metadata that is passed into
`commit` as current, and reuse it to skip a trip to object storage to
re-construct the committed metadata again.
[...]
+| `polaris.features."ALLOW_NAMESPACE_CUSTOM_LOCATION"`
| `false` | If set to true, allow
namespaces with completely arbitrary locations. This should not affect
credential vending.
[...]
+| `polaris.features."SCHEMA_VERSION_FALL_BACK_ON_DNE"`
| `true` | If set to true, exceptions
encountered while loading the VERSION table which appear to be caused by the
VERSION table not existing will be interpreted as meaning that the schema
version is currently 0.
[...]
| `polaris.authentication.type`
| `internal` | The type of authentication to
use. Three built-in types are supported: `internal`, `external`, and `mixed`.
[...]
| `polaris.authentication.authenticator.type`
| `default` | Define the Polaris
authenticator type.
[...]
| `polaris.authentication.token-service.type`
| `default` | Define the Polaris token
service type.
[...]
