Fixing quesma common table dynamic mapping case

[pdelewski]

This PR fixes the issue where quesma_common_table is used, and the mapping contains additional fields that were not present during ingestion.

processors:
  - name: my-query-processor
    type: quesma-v1-processor-query
    config:
      indexes:
        kibana_sample_data_ecommerce:
          target: [ my-clickhouse-data-source ]
          useCommonTable: true
          schemaOverrides:
            fields:
              "geoip.location":
                type: geo_point

Before :

After :

Additionally, it introduces:

• The AlterDDL struct to represent ALTER statements in object form instead of as a string. My plan is to do more refactoring around this in subsequent PR(s).
• A FieldOrigin property, which provides information about the source of the field's metadata.

[nablaone]

+1

[nablaone]

What will happen?

1. Sth puts a mappings (with field foo)
2. Quesma restarts
3. Sth starts ingesting (no foo field)

[pdelewski]

What will happen?

1. Sth puts a mappings (with field foo)
2. Quesma restarts
3. Sth starts ingesting (no foo field)

Right now, foo column created. That of course might cause a problem of creation columns that will be empty.

[pdelewski]

I will try other idea to fix it

[pdelewski]

Closing as duplicate