Skip to content

[Filter manager] Stop loading index patterns via saved object, use service instead #91036

Closed

Description

This is a bug in the value suggestions endpoint of the filter manager, where we are using this line of code to load the index pattern:

const indexPattern = await findIndexPatternById(context.core.savedObjects.client, index);

The bug manifests in the following way:

  1. Create a test index with a multi-mapped field, which is the default for any text. So for example:
PUT test-index/_doc/1
{
  "value": "My text value is multi-mapped"
}
  1. Create an index pattern for the above
  2. Go to Discover and search for value.keyword in the filter manager. Nothing will be suggested because it fails to load the index pattern field cache.

I think the only way to truly test this issue is to remove the field cache from all of the functional test archives. For example, I only ran into this problem because I removed the field cache from test/functional/fixtures/es_archiver/discover/data.json

To test this functionally, grep for discover filter editor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

Feature:Data ViewsData Views code and UI - index patterns before 8.0Feature:Filtersimpact:lowAddressing this issue will have a low level of impact on the quality/strength of our product.loe:smallSmall Level of Effort

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions