-
Notifications
You must be signed in to change notification settings - Fork 228
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
remote_storage: none leads to config validation failure #246
Labels
bug
Something isn't working
Comments
Thank you! It will be fixed in next version. |
@widders did you try the latest 1.1.0+ clickhouse-backup release? I tried to reproduce your issue with following config
I close issue, feel free to make comment or reopen if necessary |
Merged
Slach
added a commit
that referenced
this issue
Oct 24, 2021
# v1.2.0 INCOMPATIBLE CHANGES - REST API `/backup/status` now return only latest executed command with status and error message IMPROVEMENTS - Added REST API `/backup/list/local` and `/backup/list/remote` to allow list backup types separately - Decreased background backup creation time via REST API `/backup/create`, during avoid list remote backups for update metrics value - Decreased backup creation time, during avoid scan whole `system.tables` when set `table` query string parameter or `--tables` cli parameter - Added `last` and `filter` query string parameters to REST API `/backup/actions`, to avoid pass to client long JSON documents - Improved `FTP` remote storage parallel upload / download - Added `FTP_CONCURRENCY` to allow, by default MAX_CPU / 2 - Added `FTP_DEBUG` setting, to allow debug FTP commands - Added `FTP` to CI/CD on any commit - Added race condition check to CI/CD BUG FIXES - environment variable `LOG_LEVEL` now apply to `clickhouse-backup server` properly - fix #280, incorrect prometheus metrics measurement for `/backup/create`, `/backup/upload`, `/backup/download` - fix #273, return `S3_PART_SIZE` back, but calculates it smartly - fix #252, now you can pass `last` and `filter` query string parameters - fix #246, incorrect error messages when use `REMOTE_STORAGE=none` - fix #283, properly handle error message from `FTP` server - fix #268, properly restore legacy backup for schema without database name - fix #287
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With remote_storage set to 'none' all functions exit with: "error 'none' is unsupported compression format"
I tracked it to line 201 of config/config.go where the check on remote_storage was removed in commit ab56371
The text was updated successfully, but these errors were encountered: