[
https://issues.apache.org/jira/browse/JENA-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840040#comment-13840040
]
Andy Seaborne commented on JENA-602:
------------------------------------
How about using the GSP POST operation, which already means append and has a
query string {{?graph=}} or {{?default}} for the destination.
i.e. change {{SPARQL_REST_RW}} to handle multipart including multi-file
multipart.
{{SPARQL_Upload}} can be left as the general purpose uploader that will work
for any HTML form where the order of the fileds or use of the query string is
not controllable.
> 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)
