You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (Jira)" <ji...@apache.org> on 2021/04/17 16:57:00 UTC
[jira] [Resolved] (JENA-601) Provide better support for compressed
input formats
[ https://issues.apache.org/jira/browse/JENA-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne resolved JENA-601.
--------------------------------
Resolution: Done
RIOT handles compression on InputStreams.
HTTP handles compressed HTTP responses.
> 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.3.4#803005)