-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Transform] Replace legacy elasticsearch client #84932
Merged
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
13a130f
[Transform] replace legacy elasticsearch client
darnautov fcbc2c4
[Transform] delete custom legacy client definition, update transforms…
darnautov 4b6696c
[Transform] fix start and stop transform endpoints
darnautov e7b9331
Merge remote-tracking branch 'upstream/master' into transform-new-es-…
darnautov c597ebd
[Transform] fix privileges and stats endpoints
darnautov 3df72cc
Merge remote-tracking branch 'upstream/master' into transform-new-es-…
darnautov 6505b30
Merge remote-tracking branch 'upstream/master' into transform-new-es-…
darnautov 7f1bbe9
[Transform] fix forbidden
darnautov 605b016
[Transform] revert continue statement, add a comment
darnautov 4e44a09
[Transform] update privileges.ts using security namespace
darnautov fd5e988
[Transform] fix error wrappers
darnautov e667fb9
Merge remote-tracking branch 'upstream/master' into transform-new-es-…
darnautov 9b06f7e
[Transform] add functional test for preview error validation
darnautov 4099aa7
[Transform] extract error message from the root cause
darnautov 307252b
[Transform] remove error translation
darnautov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
144 changes: 0 additions & 144 deletions
144
x-pack/plugins/transform/server/client/elasticsearch_transform.ts
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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'm not sure this is guaranteed to match all errors raised from elasticsearch.
Also, the
root_cause
may not have the most relevant information for the error.In ML we pass the whole es error through to the client and display it when the user clicks the more info button.
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.
We also have a
extractErrorMessage
function in thepublic
code of transforms which we bring over from the ML plugin, maybe we can do the same on the server side (assuming there's also a server side function for the ML plugin)?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.
It's definitely worth improving error reporting, but in this PR I focused on preserving the initial error message shape.
I'll create an issue to provide more detailed errors in the transform UI.