Versions (relevant - OpenSearch/Dashboard/Server OS/Browser):
Describe the issue :
elastic:main ← ThomThomson:controls/caseInsensitive
opened 09:09PM - 28 Apr 22 UTC
## Summary
Fixes https://github.com/elastic/kibana/issues/129675
Fixes https:/… /github.com/elastic/kibana/issues/127325
This PR accomplishes 3 things:
## Case Insensitive Options Search
Options List controls created against a field which has both a keyword and a text mapping will search using a `match_phrase_prefix` query instead of the terms `include` query. This means that the search term and the terms to search through will be analyzed. By default, fields mapped this way use an analyzer which supports **case insensitive search** via transforming the tokens into lowercase.
**How to test this**
To test this, you can create an options list control against any of the fields mapped text / keyword in the ecommerce demo data. The `customer_full_name` is one of the best fields for this. There may be some weirdness using this with the `category` field because it exists within an array within the document. For this reason, there may be false positives in the search.
## Case Insensitive Field Search
This PR makes searching for field names case insensitive to make it easier for authors to find their fields.
## Run past timeout
This PR also introduces a new option which allows individual Options List controls to ignore the autocomplete timeout. This should be used if a the Control's field has high cardinality and some values are not showing up when searched for. This will slow the query down, but will ensure that all fields are returned.
@KOTungseth, this could use a copy review - and potentially a popover or a little question mark icon to better explain what's going on.
<img width="419" alt="Screen Shot 2022-04-28 at 4 40 06 PM" src="https://user-images.githubusercontent.com/14276393/165871219-f7618116-cac6-4d66-ad49-cef9321f6189.png">
### Checklist
Delete any items that are not applicable to this PR.
- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
Configuration :
elastic:main ← ThomThomson:controls/caseInsensitive
opened 09:09PM - 28 Apr 22 UTC
## Summary
Fixes https://github.com/elastic/kibana/issues/129675
Fixes https:/… /github.com/elastic/kibana/issues/127325
This PR accomplishes 3 things:
## Case Insensitive Options Search
Options List controls created against a field which has both a keyword and a text mapping will search using a `match_phrase_prefix` query instead of the terms `include` query. This means that the search term and the terms to search through will be analyzed. By default, fields mapped this way use an analyzer which supports **case insensitive search** via transforming the tokens into lowercase.
**How to test this**
To test this, you can create an options list control against any of the fields mapped text / keyword in the ecommerce demo data. The `customer_full_name` is one of the best fields for this. There may be some weirdness using this with the `category` field because it exists within an array within the document. For this reason, there may be false positives in the search.
## Case Insensitive Field Search
This PR makes searching for field names case insensitive to make it easier for authors to find their fields.
## Run past timeout
This PR also introduces a new option which allows individual Options List controls to ignore the autocomplete timeout. This should be used if a the Control's field has high cardinality and some values are not showing up when searched for. This will slow the query down, but will ensure that all fields are returned.
@KOTungseth, this could use a copy review - and potentially a popover or a little question mark icon to better explain what's going on.
<img width="419" alt="Screen Shot 2022-04-28 at 4 40 06 PM" src="https://user-images.githubusercontent.com/14276393/165871219-f7618116-cac6-4d66-ad49-cef9321f6189.png">
### Checklist
Delete any items that are not applicable to this PR.
- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
Relevant Logs or Screenshots :