[Discover|7.3.1|UI/UX] Weird behavior for Kibana Discover table and selected columns

[jesusgn90]

Kibana version:

7.3.1

Elasticsearch version:

7.3.1

Server OS version:

CentOS 7

Browser version:

Google Chrome 72.0.3626.121

Browser OS version:

Ubuntu 18.04

Original install method (e.g. download page, yum, from source, etc.):

Yum

Describe the bug:

Discover table keeps columns from different index patterns, this is wrong.

Steps to reproduce:

Having two different index patterns, let's say temperature and twitter, each one has its own fields and they are not related at all.

1. Open Discover
2. Select a field to add a column. The field exists in the first index pattern but it doesn't on the second index pattern.
3. Change the index pattern.
4. The column is still applied.

Expected behavior:

Remove selected columns on index pattern change if those columns don't exist on the selected index pattern.

Screenshots (if relevant):

[elasticmachine]

Pinging @elastic/kibana-app

[timroes]

I'll leave the previous issue as a reference here: #4909

I think some years has passed since then, and we can reevaluate what's best behavior nowadays and might give this a second thought, what we what.