Sweep: customize development ClickHouse config, update instructions #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR helped me work through a few things, including the fact that we can have two databases for each schema. I've placed the ClickHouse config and database schema (import files instead of copy/paste) in the
clickhouse-infodirectory.We're not bundling
clickhouseand have instructions for the user to get the binary in the root directory, which I believe is common practice in open source.Set the logging to output to that directory, too, and set it to "debug" mode so developers can see anything wrong.
Mostly I want myself and others to easily be able to remember what the process is and spend as little mental CPU as possible when first getting into the repo or getting back to the repo after a period.