xuang7 opened a new pull request, #3743:
URL: https://github.com/apache/texera/pull/3743

   ### **Purpose**
   This PR resolves #3742 by adding contextual guidance and reference for 
upload parameters in the admin settings page. These changes improve the Admin → 
General Settings → Dataset section, helping administrators configure upload 
parameters with better information and preventing misconfigurations that could 
lead to errors or suboptimal upload behavior.
   
   ### **Changes**
   Config:
   - Standardize variable names and units to MiB (mebibytes), consistent with 
actual behavior.
   
   Reference Documentation:
   - Add an info icon with tooltip (“Configuration Guidelines”) and a Learn 
more link to AWS S3 multipart limits (opens in a new tab).
   
   Helper text enhancement:
   - Add helper text lines showing:
     - Estimated part count for the current max file size and part size.
     - Recommended minimum part size to keep parts ≤ 10,000 (and ≥ 5 MiB).
     - In-flight data per file ≈ concurrent parts × part size (MiB).
   - Apply thousands separators to large numbers for readability.
   
   ### **Demonstration**
   Updated interface (helper text + info icon):
   
   <img width="968" height="377" alt="newui" 
src="https://github.com/user-attachments/assets/d951f05a-d2e8-42a5-aff2-e86d021ff7ed";
 />
   
   Tooltip details (info icon):
   
   <img width="971" height="511" alt="tooltip" 
src="https://github.com/user-attachments/assets/23eeb8db-d360-40a2-a6a1-2ccfc44af25b";
 />
   
   Error message when parts exceed limits:
   
   
https://github.com/user-attachments/assets/28b5b519-702e-4d30-9370-3ed302ea83f6
   
   
   Auto-adjustment for out-of-range inputs:
   
   
https://github.com/user-attachments/assets/c8472f6c-7d76-4c35-b52d-0e094469657a
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to