I query Elasticsearch datasource and it returns a document with approx. 100 key/value pairs. So in essence it is a single row with many many columns.
I want to represent the data as a 2 column table, therefore i apply Transpose data transformation and the columns get converted into rows, which is fantastic.
The problem is that the 2nd column automatically gets assigned a numeric string as its name which cannot be overriden (if i try, my custom name gets prefixed to the hardcoded value).
This is a big problem, because i plan to apply custom Unit for the values under the 2nd column by using Field Override feature.
While the Field Override will work OK with the current hardcoded Unix timestamp value, once the new data (with new Unix timestamp) is fetched from Elastic, the Field Override will still be referencing to the column name that was originaly hardcoded, thus ruining the whole thing.
What would be the solution?
