Ability to change history path by changing env #6840
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
For changelog. Remove if this is non-significant change.
Category (leave one):
Short description (up to few sentences):
Possibility to change the location of clickhouse history file using
CLICKHOUSE_HISTORY_FILE
env.Detailed description (optional):
Sometimes you may need to use several history files (for different clusters),
Or use history file stored in some network location.
Or just disable writing history by using /dev/null instead of history file.
Now it's possible using CLICKHOUSE_HISTORY_FILE env variable (you can put it to your
~/.bashrc
or set for particular run).Before that the only possibility to change that was editing /etc/clickhouse-client/config.xml
implements #6622