Too many fields end up in attributes for kibana_sample_data_ecommerce index

[avelanarius]

When running the latest main (410069d) and the configuration from the kibana-sample-data example, too many fields end up in the attributes, instead of a separate column. With the current version of Quesma it makes it impossible to query the data for those fields.

Some initial investigation why order_id ends up in attributes: we incorrectly create Nullable(String) column for it, but the data is of type Int64 . And the reason why we create Nullable(String) is because we receive a "PUT /:index/_mapping" that tells us that order_id should be a keyword (so a String).

[pdelewski]

Problems discovered for ecommerce:

• in mapping order_id, customer_id are strings (we create Nullable(String)) but in ingest there are numbers
• products.discount_amount is created as an array of int64, however there are floats
• lat, lon are created as Nullable(Strings) but there are floats

[mieciu]

@avelanarius I think we're good to call this one done today, right?