Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
picodata
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Container Registry
Model registry
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
core
picodata
Commits
96cb3e5a
Commit
96cb3e5a
authored
10 months ago
by
Yaroslav Dynnikov
Browse files
Options
Downloads
Patches
Plain Diff
doc: changelog for 24.4: config
parent
fde74cd2
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!1063
Rosik/changelog 24.4
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CHANGELOG.md
+20
-15
20 additions, 15 deletions
CHANGELOG.md
with
20 additions
and
15 deletions
CHANGELOG.md
+
20
−
15
View file @
96cb3e5a
...
...
@@ -15,23 +15,8 @@ with the `YY.MINOR.MICRO` scheme.
Tiers can span multiple failure domains and a single cluster can have
multiple tiers. Going forward it will be possible to specify which
tier a table belongs to.
-
New option
`picodata run -c`
for specifying any configuration parameters in
the same naming scheme as in the config.yaml file.
-
New option
`picodata run --tier`
specifies whether an
instance belongs to a tier.
-
New configuration parameters:
-
`instance.memtx.checkpoint_count`
-
`instance.memtx.checkpoint_interval`
-
`instance.vinyl.memory`
-
`instance.vinyl.cache`
-
`instance.iproto.max_concurrent_messages`
-
`instance.log.format`
-
Changed configuration parameter names:
-
`instance.log`
->
`instance.log.destination`
-
`instance.log_level`
->
`instance.log.level`
-
`instance.memtx_memory`
->
`instance.memtx.memory`
-
New subcommand
`picodata config default`
for generating contents of the
config.yaml file with default parameter values.
-
New rpc entrypoint:
`.proc_get_config`
which returns the effective
picodata configuration.
...
...
@@ -73,6 +58,26 @@ with the `YY.MINOR.MICRO` scheme.
[sql_case]: https://docs.picodata.io/picodata/24.4/reference/sql/case/
[sql_trim]: https://docs.picodata.io/picodata/24.4/reference/sql/trim/
### Configuration
- Provide a new way of configuring instances via config file in a yaml
format, see [Reference — Configuration file]. It extends the variety
of previously available methods — environment variables and
command-line arguments
- New option `picodata run --config` provides a path to the config file
- New option `picodata run -c` overrides single parameter using the same
naming
- New command `picodata config default` generates contents of the
config file with default parameter values
- New RPC API `.proc_get_config` returns the effective configuration
[Reference — Configuration file]:
https://docs.picodata.io/picodata/24.4/reference/config/
### Compatibility
- The current version is NOT compatible with prior releases. It cannot
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment