[
https://issues.apache.org/jira/browse/JENA-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838941#comment-13838941
]
Andy Seaborne commented on JENA-602:
------------------------------------
Can we decouple this from the UI? The upload functionality isn't specific to
the UI - scripts can use it as well.
Unfortunately, you can't require the graph name is first - the order of entries
in the multipart is arbitary (it depends on the order in the HTML form in my
experience). What we can do is IF the name is seen first, we can route the
incoming direct to a place and otherwise fall back to the current code.
We can document that feature for scripts.
Just make the changes in trunk - we can merge later - otherwise we end up with
a dependency on a piece of work that is ongoing.
> 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)
