-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[clickhouse/exporter] Update create schema config option #33694
[clickhouse/exporter] Update create schema config option #33694
Conversation
Please rebase. I'm not sure why it depends on #33693 |
7824a59
to
3936b42
Compare
Rebased. Need to fix the next PR but this one should be good now 👍 |
Failing test is unrelated, I've opened #33715 to address the failure. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I don't think this requires a changelog, but code owners and provide better input there.
Co-authored-by: Dmitrii Anoshin <anoshindx@gmail.com>
Co-authored-by: Dmitrii Anoshin <anoshindx@gmail.com>
616c3c3
to
dc1f681
Compare
[clickhouse/exporter] Update create schema config option (open-telemetry#33694) **Description:** A follow-up to open-telemetry#32282 that changes `create_schema` from `*bool` to `bool`, while also properly using the default config / factory. **Testing:** - Updated tests --------- Co-authored-by: Dmitrii Anoshin <anoshindx@gmail.com>
…onfig option. (#33614) ### DEPENDS ON #33693, #33694 **Description:** Sets `async_insert` to true by default to enable [asynchronous inserts](https://clickhouse.com/docs/en/optimize/asynchronous-inserts). Because this value is being given a default, I have added a config option under the same name. Keep in mind that if `async_insert` is provided in `endpoint` or `connection_params` it will take precedence and ignore this new config option. This is similar to how the `database` config option behaves. The goal is to provide better insert performance by default, since not all users will know to set it in their DSN URL. This also opens the discussion to ___**whether or not this is a breaking change**___. Depending on the deployment's telemetry throughput, this could be an unexpected change that leads to [`TOO_MANY_PARTS`](https://clickhouse.com/docs/knowledgebase/exception-too-many-parts) errors. I don't expect this to be the case however, but I welcome any discussion about this concern. This PR is being resubmitted with suggestions from @crobert-1 and @dmitryax applied. Here are the extra changes with these suggestions applied: - Extracted unrelated changes into separate PRs - Updated `async_insert` to avoid using a `bool` pointer - Updated tests to be able to support these non-pointer-yet-still-optional test cases **Testing:** Ran integration tests. Also added an abundance of tests to check the behavior of `async_insert` when present in `endpoint`, `connection_params`, and exporter config. **Documentation:** - Updated README for all related changes Unrelated change, also updated README's SQL samples to use `sql` instead of `clickhouse` for the code samples to enable proper syntax highlighting. ClickHouse SQL is compatible with plain SQL.
EXTRACTED FROM #33614
DEPENDS ON #33693
Description:
A follow-up to #32282 that changes
create_schema
from*bool
tobool
, while also properly using the default config / factory.Testing: