Skip to content
This repository was archived by the owner on Nov 7, 2025. It is now read-only.
This repository was archived by the owner on Nov 7, 2025. It is now read-only.

Compatibility Report Table ab_testing_logs not created #1525

@marcohald

Description

@marcohald

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions