[
https://issues.apache.org/jira/browse/JENA-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838970#comment-13838970
]
Rob Vesse edited comment on JENA-602 at 12/4/13 3:16 PM:
---------------------------------------------------------
We can require that the graph name appear first if we don't include it in the
POSTed data. It is perfectly acceptable to have a request that has both a
querystring component in the request URI and a POST body.
What I am suggesting is that the interface becomes {{POST
/foo/upload?graph=http%3A%2F%2Fexample.org%2Fgraph}}
i.e. the graph name moves to the query string which we can always read before
the request body and the actual data to be uploaded remains included in the
POSTed body as form-multipart
was (Author: rvesse):
We can require that the graph name appear first if we don't include it in the
POSTed data. It is perfectly acceptable to have a request that has both a
querystring component in the request URI and a POST body.
What I am suggesting is that the interface becomes {{POST
/foo/upload?graph=http%3A%2F%2Fexample.org%2Fgraph}} i.e. the graph name moves
to the query string which we can always read before the request body and the
actual data to be uploaded remains included in the POSTed body as form-multipart
> 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)
