lens esql generation

[ppisljar]

Summary

updates lens so it uses ESQL when requesting data from elasticsearch rather than DSL when that is possible.

nothing should change for the user, everything should work exactly as before

but when going to inspector you will be able to see that in some cases we will send out ESQL request.

the feature is only enabled when the lens.enable_esql feature flag is enabled.

at the moment this covers very few cases, but rather builds the necessary infrastructure so we can keep improving this over time:

• user has to be in UTC timezone
• user needs to use set of lens operations that are supported

how to test:

1. put this in your kibana.dev.yaml:

feature_flags.overrides:
  lens.enable_esql: true

2. go to advanced settings and set timezone to UTC
3. go to lens, configure a chart (for example a metric chart showing average of products.price
4. go to inspector -> requests and you can see that we sent out ESQL query
5. visually nothing should change

todo:

• make sure CI is green when the feature flag is enabled

[stratoula]

This looks great Peter, LGTM!

[afharo]

Is this the first use of the Feature Flags service? Nice! 🙌

[afharo]

Please, remember to remove this before merging

[ppisljar]

this was just added in the commit named revert before merging to check once again that CI is passing when this flag is on

[afharo]

Thanks for confirming! I'm sure that Core won't be needed when this is removed :)

Core review won't be needed when the changes to kibana.yml are removed

[ppisljar]

as expected rollup and search sessions tests fail when turning the flag on, everything else passes

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 0165357

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
data	608	623	+15
lens	1810	1811	+1
total			+16

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
data	2598	2600	+2
expressions	1772	1774	+2
total			+4

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
dashboard	601.9KB	601.9KB	+13.0B
dataVisualizer	720.0KB	720.0KB	+13.0B
esql	229.7KB	229.7KB	+13.0B
lens	1.6MB	1.6MB	+6.7KB
maps	3.0MB	3.0MB	+13.0B
securitySolution	21.4MB	21.4MB	+13.0B
total			+6.7KB

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
data	25	26	+1

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
data	420.2KB	423.6KB	+3.3KB
expressions	101.4KB	101.7KB	+302.0B
total			+3.6KB

Unknown metric groups

API count

id	before	after	diff
data	3213	3215	+2
expressions	2244	2246	+2
total			+4

History

• 💔 Build #271462 failed b4555d3
• 💚 Build #271393 succeeded dd72779
• 💚 Build #270478 succeeded 1e12b49
• 💔 Build #270427 failed c5c6108
• 💛 Build #270317 was flaky e90b6af
• 💚 Build #270252 succeeded f92dbf4

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 196049 locally

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 196049 locally

[ppisljar]

💚 All backports created successfully

Status	Branch	Result
✅	8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation