Caideyipi opened a new pull request, #18661: URL: https://github.com/apache/iotdb/pull/18661
## Description - Preserve the rejected operator-memory batch size and free-memory snapshot in a typed 719 exception. Result-column diagnostics now show the actual failed request, and the suggested additional memory uses the same numbers. In the reported case, 1,048,840 - 702,452 = 346,388 bytes, rather than treating the last 760-byte expression reservation as the failed batch. - If matched source columns have already been expanded and the existing source-column capacity estimate is zero, show an estimated column-equivalent shortage based on the rejected batch and the observed average column size. Do not claim that unexpanded source columns exist in this case. - Keep the original positive source-column overage wording and the schema-fetch path unchanged. Add corresponding English and Chinese messages. ## Verification - DataNode incremental compile (offline): passed. - MPPQueryContextTest: 5 tests, 0 failures, 0 errors, 0 skipped. Includes matched == expanded, matched == expanded + 1, and the reported 760 / 1,048,840 / 702,452-byte discrepancy. - Spotless and git diff --check: passed. Chinese DataNodeQueryMessages compiled with javac -encoding UTF-8. - Full-reactor test attempt was limited by Windows JVM native-memory allocation during full DataNode recompilation. No cluster-level reproduction was run here. ## Key changed classes - OperatorMemoryNotEnoughException carries the failed pool request and contemporaneous free-memory value without changing status code 719. - LocalExecutionPlanner records those values at allocation failure; MPPQueryContext uses them when formatting result-column diagnostics. -- 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]
