[ 
https://issues.apache.org/jira/browse/JENA-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17505108#comment-17505108
 ] 

Andy Seaborne commented on JENA-601:
------------------------------------

bz2 is supported already :: JENA-1554.

But beware - decompressing bz2 is significantly slower than gz in a JVM 
(possibly because bz2 is pure java). So such so that downloading a bigger gz 
file and using that can be faster to load data.

An external decompressor will be running in parallel and may well be faster.

Also see the discussion zstd :: JENA-2181.

Apache Commons Compress uses an external JNI library for zstd decompression 
which requires external native library so we'd need multiarch jars)

What other compression formats are common? 

JENA-2181 and the PR discussion shows where in the code to add them if you want 
to put in a pull request.

> Provide better support for compressed input formats
> ---------------------------------------------------
>
>                 Key: JENA-601
>                 URL: https://issues.apache.org/jira/browse/JENA-601
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: RIOT
>    Affects Versions: Jena 2.11.0
>            Reporter: Rob Vesse
>            Priority: Major
>
> Currently Jena has little or not support for compressed input formats.  There 
> are the odd cases where some consideration is given e.g.
> - {{RDFLanguages.filenameToLang()}} strips off {{.gz}} extensions to help it 
> correctly detect file types
> - HTTP responses can deal with compressed responses by virtue of Apache 
> HttpClient
> What would be nice is to have a better strategy for handling compressed 
> inputs.  For example having a registry of known compression extensions e.g. 
> {{.gz}}, {{.bz2}}, {{.deflate}} which ARQ would strip off when trying to 
> deduce format from the filename.
> It would also be useful if the various locator implementations took 
> compression into account when opening input streams as I'm fairly sure if you 
> asked ARQ to open a {{foo.nt.gz}} file it would just open a raw input stream 
> and then the reading would fail.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to