[Maps][File upload] Remove usage of max file size advanced setting 1GB limit in geo file upload #93261
Assignees
Labels
[Deprecated-Use Team:Presentation]Team:Geo
Former Team Label for Geo Team. Now use Team:Presentation
enhancement
New value added to drive a business result
Feature:File Upload
v8.2.0
Comments
thomasneirynck
added
discuss
[Deprecated-Use Team:Presentation]Team:Geo
|
Pinging @elastic/kibana-gis (Team:Geo) |
nreese
changed the title
|
fileUpload:maxFileSize advanced setting is used by CSV file upload and geo file upload. Lets de-couple removal of fileUpload:maxFileSize advanced setting and removing usage of fileUpload:maxFileSize so geo file upload can be unbounded. The scope of this issue should be limited to only removing maps usage of fileUpload:maxFileSize and not the removal fileUpload:maxFileSize advanced setting. |
maksimkovalev
added a commit
to maksimkovalev/kibana
that referenced
this issue
Mar 14, 2022
nreese
pushed a commit
that referenced
this issue
Mar 16, 2022
…B limit in geo file upload (#127639) * #93261 - Usage of maxFileSize in geo upload form is removed * 93261 - refactoring * 93261 - fixed translation checks * 93261 - documentation updates Co-authored-by: Kibana Machine <[email protected]>
maksimkovalev
added a commit
to maksimkovalev/kibana
that referenced
this issue
Mar 18, 2022
…B limit in geo file upload (elastic#127639) * elastic#93261 - Usage of maxFileSize in geo upload form is removed * 93261 - refactoring * 93261 - fixed translation checks * 93261 - documentation updates Co-authored-by: Kibana Machine <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discussed first here: #92620 (review)
The
maxFileSizeadvanced-setting seems arbitrary, especially in the context of maps, since:- preview only loads first 10k features
- ingest is streamed, so the file is not held in memory
Was suggested that this setting makes more sense as a sys-admin level safety break in
kibana.yml, rather than a UX-level advanced settingSince this is already a setting, as a first step we could just remove the 1GB limit
@nreese @jgowdyelastic @peteharverson @rudolf
The text was updated successfully, but these errors were encountered: