Skip to content

Commit 1102c1b

Browse files
fix issue with docs
1 parent 6acb8ef commit 1102c1b

File tree

1 file changed

+3
-15
lines changed

1 file changed

+3
-15
lines changed

docs/changelog/131559.yaml

Lines changed: 3 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -2,21 +2,9 @@ pr: 131559
22
summary: Add support for LOOKUP JOIN on multiple fields
33
area: ES|QL
44
type: enhancement
5-
issues: []
5+
issues: [ ]
66
highlight:
77
title: Add support for Lookup Join on Multiple Fields
8-
body: "Add support for Lookup Join on Multiple Fields\n\n```\nFROM index1\n| LOOKUP\
9-
\ JOIN lookup_index on field1, field2\n```\n\nRemoved some checks to allow lookup\
10-
\ join on multiple fields. Added a new\ninterface LookupEnrichQueryGenerator,\
11-
\ that can be used to get total\nnumber of queries and queries by position. The\
12-
\ rest of the methods from\nQueryGenerator are not needed by AbstractLookupService.\
13-
\ \n\nThat allowed the creation of a new class ExpressionQueryList implements\n\
14-
LookupEnrichQueryGenerator, which is responsible for creating the AND\nquery for\
15-
\ the different fields. We will likely need to enhance it in the\nfuture to support\
16-
\ expressions that include OR and NOT as well. \n\nTransportRequest is enhanced\
17-
\ to now support `List<MatchConfig>`\nmatchFields instead of `String matchField`.\
18-
\ This is how we pass the\nmatch fields around now. If we are communicating with\
19-
\ an cluster that\ndoes not support LookupOnMultipleFields and it is needed by\
20-
\ the query we\nwill fail the query. This can happen during rolling upgrade or\
21-
\ CCS."
8+
body: "Add support for Lookup Join on Multiple Fields e.g. FROM index1\n| LOOKUP\
9+
\ JOIN lookup_index on field1, field2"
2210
notable: true

0 commit comments

Comments
 (0)