You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Rob Vesse (JIRA)" <ji...@apache.org> on 2013/12/04 15:18:37 UTC

[jira] [Created] (JENA-602) Fuseki upload should avoid having to cache the data into memory where possible

Rob Vesse created JENA-602:
------------------------------

             Summary: Fuseki upload should avoid having to cache the data into memory where possible
                 Key: JENA-602
                 URL: https://issues.apache.org/jira/browse/JENA-602
             Project: Apache Jena
          Issue Type: Improvement
          Components: Fuseki
    Affects Versions: Fuseki 1.0.0
            Reporter: Rob Vesse


Currently when uploading data files to Fuseki it always caches the data in-memory even if the underlying dataset is transactional.  The reason stated in code is that since a form multipart request is used there is no way of knowing which graph the data is destined for because you may see the graph name after the data.

With the ongoing Fuseki UI refactor it may be worth rethinking this, what we could do is require that any graph name is a query string parameter thus guaranteeing up front access to it and that only the data is POSTed in the form multipart request.

If this change was made we could then support transactional uploads since you'd always know the graph to write to in advance and this would make file uploads significantly faster for systems like TDB.



--
This message was sent by Atlassian JIRA
(v6.1#6144)