When a geo_point field is added to fieldEncodings, actually two fields get added:
my_field.lat
my_field.lon
SchemaToColumns however tried to find my_field in fieldEncodings (which was missing; only my_field.lat and my_field.lon were there). This resulted in creating (incorrect, unused) columns lat, lon since internalPropertyName was empty.
Fix the problem by accessing my_field.lat and my_field.lon keys in fieldEncodings instead (which should be there).
Add new integration test that checks Quesma's ingest of Kibana sample flights, Kibana sample ecommerce. The tests without "PUT mapping" caught the fixed issue (this is how I found it).
When a
geo_point
field is added tofieldEncodings
, actually two fields get added:my_field.lat
my_field.lon
SchemaToColumns
however tried to findmy_field
infieldEncodings
(which was missing; onlymy_field.lat
andmy_field.lon
were there). This resulted in creating (incorrect, unused) columnslat
,lon
sinceinternalPropertyName
was empty.Fix the problem by accessing
my_field.lat
andmy_field.lon
keys infieldEncodings
instead (which should be there).Add new integration test that checks Quesma's ingest of Kibana sample flights, Kibana sample ecommerce. The tests without "PUT mapping" caught the fixed issue (this is how I found it).