HyukjinKwon commented on PR #58597: URL: https://github.com/apache/spark/pull/58597#issuecomment-5582132156
Thanks for the very thorough review. On reflection, the global cap here targets data that is within the submitting application's own trust boundary, and the one genuinely unbounded allocation site (AttributeGroup) is better addressed narrowly on its own, if at all, rather than via a cross-cutting configurable cap that also rejects Spark's own intermediate results (e.g. HashingTF's default 262144) and adds a per-row hook in VectorUDT. Closing this one; I may follow up narrowly on AttributeGroup separately. Appreciate the detailed analysis. -- 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]
