Hi Paul,
I have optimized the implementation of archive:extract-to. Archive contents will now be directly output to the local file system [1,2].
Best, Christian
[1] http://files.basex.org/releases/latest/ [2] https://github.com/BaseXdb/basex/commit/8de6dceb2b7f9c56afa6c258a5f2a3c094fe...
On Tue, Oct 30, 2018 at 3:07 PM Han (US), Paul P Paul.P.Han@boeing.com wrote:
Hello,
We encountered the below error when using this API: archive:extract-to($tempDirPath, file:read-binary($zipFilePath)). The zip file size is 51396593 and the inflated file size is 2796146027. Please let me know if you need additional information. We expect our data files to be at least 10 times bigger than these numbers.
POST failed with response 400: Improper use? Potential bug? Your feedback is welcome: Contact: basex-talk@mailman.uni-konstanz.de Version: BaseX 9.0.2 Java: Oracle Corporation, 1.8.0_121 OS: Linux, amd64 Stack Trace: java.lang.ArrayIndexOutOfBoundsException: Maximum array size reached. at org.basex.util.Array.newSize(Array.java:238) at org.basex.util.Array.newSize(Array.java:227) at org.basex.io.out.ArrayOutput.write(ArrayOutput.java:32) at java.io.OutputStream.write(OutputStream.java:116) at org.basex.query.func.archive.ArchiveIn.read(ArchiveIn.java:77) at org.basex.query.func.archive.ArchiveExtractTo.item(ArchiveExtractTo.java:40)