https://issues.apache.org/bugzilla/show_bug.cgi?id=57572
--- Comment #1 from Nick Burch <[email protected]> --- As a general guide, SXSSF relies on the common (in-memory) XSSF code for the bulk of the file format handling. The only exceptions to that are the sheet contents (buffered), and shared strings table (optional on-disk storage, see patches, not yet committed). Normally, this trade-off works - lots of things can be easily supported without massive re-writes, by using the existing XSSF code, and the other parts of the .xlsx file format are normally much much smaller It looks like that in your case, one of these assumptions breaks down... If having that many comments is a requirements, sadly it's going to need some more work, most likely from yourselves as you're the only ones affected. At a quick glance, it would seem your options are: * Provide an alternate XSSFVMLDrawing (and friends?) implementation which works in a streaming manner, much as SXSSFSheet does * Provide an alternate XSSFVMLDrawing (and friends?) implementation which uses an on-disk storage for random access, and a low-memory write, much as the proposed shared strings table support does Jump on the dev list if you need help with starting down either route! -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
