-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[ML] Adding configurable file size to file data visualizer #62752
[ML] Adding configurable file size to file data visualizer #62752
Conversation
Pinging @elastic/ml-ui (:ml) |
cc @droberts195 |
related to #61735 |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
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.
Tested and LGTM.
I found a couple of pages in the docs which need edits:
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 ⚡️
…2752) * [ML] Adding configurable file size to file data visualizer * updating translated strings
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, added just one question about the error message.
@@ -81,7 +80,7 @@ interface FileCouldNotBeReadProps { | |||
} | |||
|
|||
export const FileCouldNotBeRead: FC<FileCouldNotBeReadProps> = ({ error, loaded }) => { | |||
const message = error.body.message; | |||
const message = error?.body?.message || ''; |
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.
Could we make use of getErrorMessage()
from plugins/ml/common/util/errors.ts
here?
Adds the ability to override the default file size limit of 100MB to a maximum of 500MB.
A new ML specific setting can be added to the
kibana.yml
file to achieve this.500MB has been choses as the max as it is currently the largest size the browser (tested with chrome and firefox) can handle when reading the file's contents to a string.
It would be possible to avoid creating this string and to create the uploadable chunks of documents straight from the read byte array, but this work will need to be done in a follow up PR.
Checklist
Delete any items that are not applicable to this PR.
For maintainers