I left that option disabled anticipating something as fancy as this could cause troubles
Though, I now face another error and already regretting to have started to user Excel again
2024-08-23 14:20:13,921 ERROR Excel Writer 3:1723:0:1722:0:1710 Execute failed: Tried to allocate an array of length 233,650,834, but the maximum length for this record type is 100,000,000.
If the file is not corrupt and not large, please open an issue on bugzilla to request
increasing the maximum allowable size for this record type.
You can set a higher override value with IOUtils.setByteArrayMaxOverride()
Fun thing is, thee Excel Reader has no problem reading that sheet.
PS: I believe the cause is rooted in the first sheet which uses formulas that reference entire columns. This might be bug as I’d not expect, when sheet names are read, that the content is also parsed.
I am actually required to delete the sheet as locating it to the end does not resolve it.
the second problem is fixed in 5.4 and 5.3.2 (AP-22911). Due to the way the XLSX file format is defined, it is not always possible to read only parts of it… It’s just not a good data exchange format if processing speed is a concern. It’s convenient because it can be very compact and basically every computer has a viewer installed (Excel), but Parquet for example is so much more efficient to process.
Anyway, the original problem is known but we did not yet have the time to address it due to its low priority. It’s annoying, but you can click it away and it’s not clearly reproducible.
While I can’t guarantee it will work for you, and it’s not a definitive solution, I encountered a similar problem and found that substituting the ‘-’ in the sheet name with ‘_’ (underscore) resolved it for me.
Br