Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Console] Fields autocomplete suggestions are shown for all indices #184584

Closed
yuliacech opened this issue May 31, 2024 · 1 comment · Fixed by #186479
Closed

[Console] Fields autocomplete suggestions are shown for all indices #184584

yuliacech opened this issue May 31, 2024 · 1 comment · Fixed by #186479
Assignees
Labels
Feature:Console Dev Tools Console Feature Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@yuliacech
Copy link
Contributor

Currently, the autocomplete suggestions for fields/field are displaying fields for all indices. This is caused by the fact that the property indices is not set in the context. The property index is set to the current index but the function mapping.getMappings is expecting context.indices. This might be a regression from the change in the definitions generation script (here).

To reproduce, use these 2 requests and check the autocomplete suggestions.

PUT field_test/_doc/1
{
  "test": 1
}

GET field_test/_search
{
  "query": {
    "match": {
      "": "TEXT"
    }
  }
}
Screenshot 2024-05-31 at 14 01 53
@yuliacech yuliacech added Feature:Console Dev Tools Console Feature Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more labels May 31, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-management (Team:Kibana Management)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Console Dev Tools Console Feature Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants