-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Temporary kibana runtime fields #159182
Comments
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
@nettnikl Did you have a chance to look at ESQL which is currently under development, I think this could cover your use case? https://www.elastic.co/de/blog/introduction-to-esql-new-query-language-flexible-iterative-analytics |
Hi! This indeed looks like it is we're looking for. But to say for sure, it has to be tested ofc - the blog doesnt explicitely mention in which version it would be included - is it available for the 7.x version, or only in some beta versions on 8.x branch? |
Looping in @ninoslavmiskovic for those kind of questions |
@nettnikl we are currently working on ESQL and I would to share the video from ElasticON with a demo of ESQL : https://youtu.be/JxisIO8q8UU Stayed tuned on our blog and social media for public announcements on releases. |
thx @ninoslavmiskovic closing since it's an enhancement in the works |
Thanks for the information and the link. Looks very promising! |
Describe the feature:
Allowing to specify runtime fields for a singular search query in the KQL search query bar or the fields list on the left side.
This can be done with the current language for runtime fields, or (preferably) in an easier syntax.
Describe a specific use case for the feature:
As i understand, Runtime fields are not stored, because they are meant for cases which are exceptional/one-time use.
The text was updated successfully, but these errors were encountered: