Expand description
This module defines the structure of the configuration file risingwave.toml
.
RwConfig
corresponds to the whole config file and each other config struct corresponds to a
section in risingwave.toml
.
Modules§
Macros§
Structs§
- The section
[batch]
inrisingwave.toml
. - The subsections
[batch.developer]
. - the section
[storage.cache]
inrisingwave.toml
. - The subsection
[storage.data_file_cache]
and[storage.meta_file_cache]
inrisingwave.toml
. - The section
[meta]
inrisingwave.toml
. - The subsections
[meta.developer]
. - For non-user-facing components where the CLI arguments do not override the config file.
- The subsections
[storage.object_store]
. RwConfig
corresponds to the whole config filerisingwave.toml
. Each field corresponds to a section.- The subsections
[storage.object_store.s3]
. - The subsections
[storage.object_store.s3.developer]
. - The section
[server]
inrisingwave.toml
. - The section
[storage]
inrisingwave.toml
. - The section
[streaming]
inrisingwave.toml
. - The subsections
[streaming.developer]
. - The section
[system]
inrisingwave.toml
. All these fields are used to initialize the system parameters persisted in Meta store. Most fields are for testing purpose only and should not be documented. - Unrecognized fields in a config section. Generic over the config section type to provide better error messages.
Enums§
- the section
[storage.cache.eviction]
inrisingwave.toml
.
Constants§
- Use the maximum value for HTTP/2 connection window size to avoid deadlock among multiplexed streams on the same connection.
- Use a large value for HTTP/2 stream window size to improve the performance of remote exchange, as we don’t rely on this for back-pressure.
Traits§
Functions§
Derive Macros§
- Sections in the configuration file can use
#[derive(OverrideConfig)]
to generate the implementation of overwriting configs from the file.