-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Closed
Labels
:Analytics/ES|QLAKA ESQLAKA ESQL>enhancementTeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)Meta label for analytical engine team (ESQL/Aggs/Geo)
Description
Description
Given the following lookup index
"settings": {
"index": {
"mode": "lookup"
}
},
"mappings": {
"properties": {
"id1": {
"type": "integer"
}
}
and a query FROM employees | LOOKUP JOIN test1 ON languages | KEEP emp_no, languages the error message presented invalid [test1] resolution in lookup mode to [0] indices:
- is slightly misleading: the index
test1DOES exist and the confusion comes from[0] indicesmessage which imo it suggests that there are notest1indices. If I uselookup join whateverandwhateverindex doesn't exist the error message isUnknown index [whatever] - doesn't say what is the actual problem:
languagesfield doesn't exist in indextest1. - if
test1has index mode set aslogsdbor no specific index mode, the same error message is presented, which doesn't say much about the real problem.
Actually, we have some sort of validation that refers to missing fields.
For query FROM employees | LOOKUP JOIN test1 on id1 we get Unknown column [id1] in left side of join.
For query FROM employees | LOOKUP JOIN test1 ON id1*`` we get 1:39: Unknown column [id1*] in left side of join\nline 1:39: Unknown column [id1*] in right side of join
Metadata
Metadata
Assignees
Labels
:Analytics/ES|QLAKA ESQLAKA ESQL>enhancementTeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)Meta label for analytical engine team (ESQL/Aggs/Geo)