-
Notifications
You must be signed in to change notification settings - Fork 102
Start of fixes for core/search #1947
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
Conversation
c4fb915
to
ebd6572
Compare
622cfa0
to
0f35a3b
Compare
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.
Looks good so far!
specification/_types/Errors.ts
Outdated
@@ -49,7 +49,7 @@ export class ErrorCause | |||
|
|||
export class ShardFailure { | |||
index?: IndexName | |||
node?: string | |||
node?: string | null |
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.
Does null
for this field exist in the recordings? I can't relate this to one of the Java client errors (which actually doesn't error out on null
for optional fields).
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.
Yeah this was in one of the recordings not a fix for Java specifically.
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.
I went looking for the test this is from and couldn't find it so reverted this change for now.
0f35a3b
to
0c4848b
Compare
0c4848b
to
43effe8
Compare
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
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.
LGTM
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-7.17 7.17
# Navigate to the new working tree
cd .worktrees/backport-7.17
# Create a new branch
git switch --create backport-1947-to-7.17
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick --mainline 1 dacbd3cf71ea2b3331169befe0e82d72c5a06e52
# Push it to GitHub
git push --set-upstream origin backport-1947-to-7.17
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-7.17 Then, create a pull request where the |
Co-authored-by: Seth Michael Larson <[email protected]>
Co-authored-by: Seth Michael Larson <[email protected]>
Part of #1878