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.
I try to setup the Compatibility Report
The Documentation states that as config, it is enough to have two targets for a index configured.
My Config looks like this:
processors:
- name: query-processor
type: quesma-v1-processor-query
config:
indexes: # the list below is just an example,
ab_testing_logs:
target:
- clickhouse-instance
'*': # DO NOT remove, always required
target:
- elasticsearch-instance
- clickhouse-instance
- name: ingest-processor
type: quesma-v1-processor-ingest
config:
indexes: # the list below is just an example,
ab_testing_logs:
target:
- clickhouse-instance
'*': # DO NOT remove, always required
target:
# - elasticsearch-instance
- clickhouse-instance
In the Log there is the Message: Error scanning for ab_testing_logs table
Is there anything else needed to trigger the creation of the ab_testing_logs table?
I try to setup the Compatibility Report
The Documentation states that as config, it is enough to have two targets for a index configured.
My Config looks like this:
In the Log there is the Message:
Error scanning for ab_testing_logs tableIs there anything else needed to trigger the creation of the ab_testing_logs table?