[Filters] Use terms query by default on keyword field

[erms77]

Kibana version:
7.6.1

Elasticsearch version:
7.6.1

Server OS version:
Centos 7

Browser version:
Chrome : 81.0.4044.138

Browser OS version:
Windows 10 v1903

Original install method (e.g. download page, yum, from source, etc.):
docker run image from docker.elastic.co

Describe the bug:
When adding a filter (button "add filter" in visualization) kibana uses the syntax match_phrase but if the target field has a keyword type mapping the filter match_phrase does not work.

Steps to reproduce:

1. On a vizualitation, create a filter on a keyword type mapping field.

Expected behavior:
Kibana should use a term query when the target field is typed keyword ?

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

[jimczi]

if the target field has a keyword type mapping the filter match_phrase does not work.

Can you share the error that you're seeing ? It shouldn't be a problem to run a match_phrase query on a keyword field, this is supported at the ES level.

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[lukasolson]

I've updated the description of this issue to suggest using the "terms" query by default if the field in question is a keyword field.

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[kertal]

Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change.