jaegertracing/jaeger-clickhouse 0.11.0

Release 0.11.0

on GitHub

This release cleans up/deduplicates the internal SQL scripts used for creating tables, while adding two new optional features that can be enabled via YAML configuration. Existing users should not see any changes to behavior or schemas.

The new config options are:

• init_tables: An explicit option to indicate whether whether the plugin should automatically attempt to create tables in ClickHouse. This simplifies performing table initialization via a separate external process, or adding custom sql scripts to run in addition to the built-in ones. By default, this option replicates existing behavior, being enabled if init_sql_scripts_dir is empty, or disabled if init_sql_scripts_dir is provided.
• tenant: This allows running multiple separate Jaeger instances against a shared DB/tables. Existing users that don't specify a tenant should see no change to behavior.
  Specifying this option adds a tenant column to each of the tables, populating it with the provided value for all reads/writes. By default the partitioning is configured to be per-tenant.
  The existing per-DB multitenant option continues to be available as well, so you can mix-and-match both methods in the same ClickHouse instance as needed. However you cannot mix tenant and non-tenant instances in the same DB since they use slightly different schemas.
  For more information and config examples, see the updated multitenancy guide.