arpitjain099 opened a new pull request, #65778: URL: https://github.com/apache/doris/pull/65778
### What problem does this PR solve? `getByteUint` used strict `>` for each unit threshold, so a value that lands exactly on a boundary drops to the next smaller unit. A 1 TB data quota shows up as "1024.000 GB", 1 GB as "1024.000 MB", and so on. This is visible in SHOW DATA and in the "data size exceeds quota[...]" error from Database.checkDataSizeQuota, and round quotas like SET DATA QUOTA 1T hit it directly. The sibling method `getUint` already uses `>=` for the same kind of formatting, so this just makes `getByteUint` consistent with it. Changed the four comparisons to `>=` so exact multiples of 1024 roll up to the right unit. ### Release note None ### Check List Added boundary cases (1 KB, 1 MB, 1 GB, 1 TB) to DebugUtilTest. The existing non-boundary assertions are unchanged. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
