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

[Lens] Use search source for field existence #90271

Closed
flash1293 opened this issue Feb 4, 2021 · 2 comments
Closed

[Lens] Use search source for field existence #90271

flash1293 opened this issue Feb 4, 2021 · 2 comments
Labels
Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure technical debt Improvement of the software architecture and operational architecture

Comments

@flash1293
Copy link
Contributor

The field existence API used to divide fields into "available" and "empty" fields directly uses the Elasticsearch client. This can lead to issues because index pattern capabilities can converge over time (e.g. with runtime fields #90175)

By using the search source service from the data plugin, it should be possible to leverage the higher level API to reduce the amount integrations the API has to do itself.
@flash1293 flash1293 added technical debt Improvement of the software architecture and operational architecture Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens labels Feb 4, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@flash1293 flash1293 mentioned this issue Feb 4, 2021
Closed
43 tasks
@flash1293
Copy link
Contributor Author

Not relevant anymore as this is done via field caps now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure technical debt Improvement of the software architecture and operational architecture
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@flash1293 @elasticmachine