Skip to content

enhancement: show more parameters when using show parameters command #9446

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lmatz opened this issue Apr 26, 2023 · 3 comments
Open

enhancement: show more parameters when using show parameters command #9446

lmatz opened this issue Apr 26, 2023 · 3 comments
Assignees
Labels
help wanted Issues that need help from contributors no-issue-activity type/enhancement Improvements to existing implementation.

Comments

@lmatz
Copy link
Contributor

lmatz commented Apr 26, 2023

dev=> show parameters;
           Name           |     Value      
--------------------------+----------------
 barrier_interval_ms      | 1000
 checkpoint_frequency     | 10
 sstable_size_mb          | 256
 block_size_kb            | 64
 bloom_false_positive     | 0.001
 state_store              | hummock+memory
 data_directory           | hummock_001
 backup_storage_url       | memory
 backup_storage_directory | backup
 telemetry_enabled        | true
(10 rows)

I suggest we list all the configurations in https://github.com/risingwavelabs/risingwave/blob/main/src/common/src/config.rs
and make this command a single source of truth.

@lmatz lmatz added type/enhancement Improvements to existing implementation. help wanted Issues that need help from contributors labels Apr 26, 2023
@github-actions github-actions bot added this to the release-0.20 milestone Apr 26, 2023
@BugenZhao
Copy link
Member

Maybe related: #8850, #8851

@github-actions
Copy link
Contributor

This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.

Copy link
Contributor

github-actions bot commented Jul 3, 2024

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Issues that need help from contributors no-issue-activity type/enhancement Improvements to existing implementation.
Projects
None yet
Development

No branches or pull requests

4 participants