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

Search Strategy - return runtime fields when passed Data View id #111762

Closed
Tracked by #166068
stephmilovic opened this issue Sep 9, 2021 · 3 comments
Closed
Tracked by #166068

Search Strategy - return runtime fields when passed Data View id #111762

stephmilovic opened this issue Sep 9, 2021 · 3 comments
Labels
Feature:Search Querying infrastructure in Kibana Icebox impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:medium Medium Level of Effort NeededFor:Security Solution SIEM, Endpoint, Timeline, Analyzer, Cases Project:Fields Access field values from fields response, not source Project:RuntimeFields Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.

Comments

@stephmilovic
Copy link
Contributor

We are using ISearchStrategy in security solution and need to get runtime fields. Right now I need to request the runtime field script and pipe it through my front-end to pipe it to the back-end to pass to ISearchStrategy. I have the index-pattern id. It would be nice if when indexPattern.id is passed to ISearchStrategy, it automatically returns the runtime fields.
@stephmilovic stephmilovic added Team:AppServices Project:RuntimeFields Project:Fields Access field values from fields response, not source labels Sep 9, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServices)

@stephmilovic stephmilovic changed the title [Kibana] Search Strategy - return runtime fields when passed Data View id Sep 9, 2021
@lukasolson lukasolson added the Feature:Search Querying infrastructure in Kibana label Sep 9, 2021
@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Sep 27, 2021
@stephmilovic stephmilovic mentioned this issue Sep 29, 2021
Closed
3 tasks
@lukasolson lukasolson added the NeededFor:Security Solution SIEM, Endpoint, Timeline, Analyzer, Cases label Apr 20, 2022
@exalate-issue-sync exalate-issue-sync bot removed the loe:small Small Level of Effort label Apr 20, 2022
@exalate-issue-sync exalate-issue-sync bot added the loe:medium Medium Level of Effort label May 23, 2022
@petrklapka petrklapka added Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. and removed Team:AppServicesSv labels Nov 23, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

@kertal kertal mentioned this issue Sep 8, 2023
Open
@kertal
Copy link
Member

kertal commented Oct 30, 2023

Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change. Feel free to re-open if you think it should be melted sooner.

@kertal kertal closed this as not planned Won't fix, can't repro, duplicate, stale Oct 30, 2023
@kertal kertal added the Icebox label Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature:Search Querying infrastructure in Kibana Icebox impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:medium Medium Level of Effort NeededFor:Security Solution SIEM, Endpoint, Timeline, Analyzer, Cases Project:Fields Access field values from fields response, not source Project:RuntimeFields Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@kertal @lukasolson @stephmilovic @elasticmachine @petrklapka