Closed googollee closed 7 months ago
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
From the previous comment, I think it should be easy to fix by changing Timestamp
to TimeUnix
in https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/v0.90.0/exporter/clickhouseexporter/factory.go#L126. But as there is no unit test to check creating SQLs, I'd like to leave it to owners to find a way to test first.
@Frapschen Can you have a look at it?
I'd like to leave it to owners to find a way to test first.
To detect SQL problems like that we need to start a clickhouse server to test the SQLs, I want to use Testcontainers to start a clickhouse container and start our exporter based on it. any thought? @googollee @JaredTan95 @hanjm
This should be fixed by https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/29573. @Frapschen PTAL
I'd like to leave it to owners to find a way to test first.
To detect SQL problems like that we need to start a clickhouse server to test the SQLs, I want to use Testcontainers to start a clickhouse container and start our exporter based on it. any thought? @googollee @JaredTan95 @hanjm
@Frapschen Looks good, try it. If the CI not support docker, then add a special go tag for local test only.
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Component(s)
exporter/clickhouse
What happened?
Description
With
0.90.0
collector, when starting with clickhouse exporter, collector can't create metrics tables in clickhouse. It works well with0.89.0
version, so this bug should be introduced by https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/29095.Steps to Reproduce
docker run --rm -v \
pwd`/otel.yaml:/etc/otelcol-contrib/config.yaml --network host ghcr.io/open-telemetry/opentelemetry-collector-releases/opentelemetry-collector-contrib:0.90.0`Expected Result
The collector image should work well with the configuration.
Actual Result
Collector version
v0.90.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04") Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
Log output
Additional context
No response