Skip to content

[ES|QL] LOOKUP JOIN: Query lookup index with ES|QL #230140

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

Open
wants to merge 6 commits into
base: feature/lookup-join-ux
Choose a base branch
from

Conversation

darnautov
Copy link
Contributor

Summary

Part of #207330

⚠️ Note for reviewers: This PR is targeting the feature branch

  • Adds a query bar for querying a lookup index
image
  • Replaces the searchSource with a search call using the ES|QL query builder

@darnautov darnautov self-assigned this Jul 31, 2025
@darnautov darnautov requested review from a team as code owners July 31, 2025 22:08
@elasticmachine
Copy link
Contributor

💔 Build Failed

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #22 / Air-gapped environment with pre-bundled packages @ess @serverless @skipInServerlessMKI Bootstrap Prebuilt Rules installs required Fleet packages required for detection engine to function

Metrics [docs]

‼️ ERROR: no builds found for mergeBase sha [f9014f1]

cc @darnautov

@@ -45,10 +52,20 @@ export const CustomPanel = () => {

return (
<EuiFlexGroup alignItems={'center'} gutterSize={'s'}>
<EuiFlexItem grow>
{dataView ? (
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you should check for indexCreated$ instead, I would hide the search bar, refresh button, and the discover button if the index is not created, as there is nothing to query yet.

{dataView ? (
<EuiSearchBar
defaultQuery={''}
onChange={({ queryText, query, error }) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
onChange={({ queryText, query, error }) => {
onChange={({ queryText }) => {

Or should we display this error? What kind of errors can this component return?

)
.pipe(
catchError((e) => {
// query might be invalid, so we return an empty response
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we display feedback to the user to differentiate valid querys with no results from wrongly formatted querys?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants