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.

Sign up for GitHub

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

Jump to bottom

Incomplete responses in _resolve endpoint #996

Open
mieciu opened this issue Nov 14, 2024 · 0 comments · May be fixed by #989
Open

Incomplete responses in _resolve endpoint #996

mieciu opened this issue Nov 14, 2024 · 0 comments · May be fixed by #989
Assignees
@mieciu
Labels
bug Something isn't working

Comments

@mieciu
Copy link
Member

mieciu commented Nov 14, 2024 •
edited
Loading

There are several issues with how we handle the _resolve endpoint:

  • it doesn't show indices that live in Elasticsearch
  • it doesn't take "targets" into account

Ideally, we should ensure that we show all the data sources so that people can create Data Views/Index Patterns with all the sources they have.
@mieciu mieciu added the bug Something isn't working label Nov 14, 2024
@mieciu mieciu self-assigned this Nov 14, 2024
@mieciu mieciu linked a pull request Nov 15, 2024 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mieciu mieciu

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Don't remove Elasticsarch indices/datastreams from _resolve endpoint QuesmaOrg/quesma
1 participant
@mieciu