-
Notifications
You must be signed in to change notification settings - Fork 25.5k
Resolve indices using original index pattern #134218
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
Changes from 6 commits
e0f5989
9e56546
e172c13
62cb8e9
d653020
21ccd63
24b7a4c
b1e75f4
3029bfb
58c8230
ee777a4
06bfcfa
3c9a40b
cf31115
e9a0e29
880f169
444217d
e5254ec
685830f
adaa593
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -377,24 +377,24 @@ public void testSearchesAgainstNonMatchingIndices() throws Exception { | |
// an error is thrown if there is a concrete index that does not match | ||
{ | ||
String q = "FROM nomatch*,cluster-a:nomatch"; | ||
String expectedError = "Unknown index [cluster-a:nomatch,nomatch*]"; | ||
String expectedError = "Unknown index [nomatch*,cluster-a:nomatch]"; | ||
expectVerificationExceptionForQuery(q, expectedError, requestIncludeMeta); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Here and in 3 below cases the error message index now matches the original input (notice that the order was different). There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this ordering stable - i.e. is it going to always match original order, no matter how many patterns and clusters we have? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Correct, error uses |
||
} | ||
|
||
// an error is thrown if there are no matching indices at all - local with wildcard, remote with wildcard | ||
{ | ||
String q = "FROM nomatch*,cluster-a:nomatch*"; | ||
String expectedError = "Unknown index [cluster-a:nomatch*,nomatch*]"; | ||
String expectedError = "Unknown index [nomatch*,cluster-a:nomatch*]"; | ||
expectVerificationExceptionForQuery(q, expectedError, requestIncludeMeta); | ||
} | ||
{ | ||
String q = "FROM nomatch,cluster-a:nomatch"; | ||
String expectedError = "Unknown index [cluster-a:nomatch,nomatch]"; | ||
String expectedError = "Unknown index [nomatch,cluster-a:nomatch]"; | ||
expectVerificationExceptionForQuery(q, expectedError, requestIncludeMeta); | ||
} | ||
{ | ||
String q = "FROM nomatch,cluster-a:nomatch*"; | ||
String expectedError = "Unknown index [cluster-a:nomatch*,nomatch]"; | ||
String expectedError = "Unknown index [nomatch,cluster-a:nomatch*]"; | ||
expectVerificationExceptionForQuery(q, expectedError, requestIncludeMeta); | ||
} | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prior behavior returned empty result for empty index resolution.
Now this is complaining about empty index resolution (consistent with
FROM empty-pattern-*
case)