[
https://issues.apache.org/jira/browse/JENA-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067614#comment-14067614
]
Andy Seaborne commented on JENA-744:
------------------------------------
java bug 4262583 was fixed at java5.
I have used tdbloader with >4G files (on Ubuntu and Centos).
The problem seems to be in creating the gzip file.
One thing to try is decompress with the local OS gzip (must be n-quads or
n-triples) and steram to tdbloader:
{noformat}
gzip -d < DATA.nq.gz | tdbloader --loc ... -- -
{noformat}
> Error importing from large gzip
> -------------------------------
>
> Key: JENA-744
> URL: https://issues.apache.org/jira/browse/JENA-744
> Project: Apache Jena
> Issue Type: Bug
> Components: TDB
> Reporter: Michael Kozakov
> Fix For: Jena 2.12.0
>
> Attachments: gzip.png
>
>
> gzip has a documented bug:
> http://www.freebsd.org/cgi/man.cgi?query=gzip#end
> "According to RFC 1952, the recorded file size is stored in a 32-bit inte-
> ger, therefore, it can not represent files larger than 4GB. This
> limita-
> tion also applies to -l option of gzip utility."
> As a result, a 28gb compressed gz shows that the uncompressed size is 1.6gb.
> (screenshot attached)
> It seems like tdbloader relies on this information to know when to stop
> importing, and as a result, the imported database is incomplete. As a
> walkaround, I have to extract the archive before using tdbloader to import
> the database, otherwise it will be missing the majority of items.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
