[
https://issues.apache.org/jira/browse/JENA-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838974#comment-13838974
]
Rob Vesse commented on JENA-602:
--------------------------------
Though I suppose we could make the change so that the query string is preferred
as the source of graph name and we try the transactional update when it is
received that way and the dataset is transactional. This preserves backwards
compatibility and doesn't involve changing the current UI.
The new UI can then take advantage of the new interface and always puts the
graph name in the query string.
> 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)
