You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 7, 2025. It is now read-only.
Preserve order of targets in QueryTarget, IngestTarget (#897)
A user in the configuration of a query/ingest processor can define
targets:
```yaml
my_index:
target: [ elastic-conn, clickhouse-conn ]
```
We subsequently take those values and populate `QueryTarget` and
`IngestTarget` arrays based on it, however the code did not preserve the
order of the targets. The order is important for A/B testing case and
`rules.go` had to incorrectly allow an unsupported scenario for
everything to work correctly.
Fix the issue by preserving the same order in `QueryTarget`,
`IngestTarget` as in the original `target` user configuration.
`rules.go` workaround can be now removed.
errAcc=multierror.Append(errAcc, fmt.Errorf("index %s has invalid dual query target configuration - when you specify two targets, ClickHouse has to be the primary one and Elastic has to be the secondary one", indexName))
errAcc=multierror.Append(errAcc, fmt.Errorf("index %s has invalid dual query target configuration - when you specify two targets, ClickHouse has to be the primary one and Elastic has to be the secondary one", indexName))
0 commit comments