[ https://issues.apache.org/jira/browse/JENA-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487073#comment-17487073 ]
Andy Seaborne commented on JENA-2270: ------------------------------------- Do you use the Upload service with a specific named graph? Or send multi-part to the GSP? The [key text|https://www.w3.org/TR/sparql11-http-rdf-update/#http-post] is: bq. an RDF merge of the enclosed RDF payload enclosed into the RDF graph content identified by the request or encoded IRI. {{HTML_FileUpload}} does not comply with that part of the spec. It tries to merge the content based to a named graph based on the filename. It ignores the query string naming. You can try the development build when this is merged. > Improve Fuseki data upload functionality. > ----------------------------------------- > > Key: JENA-2270 > URL: https://issues.apache.org/jira/browse/JENA-2270 > Project: Apache Jena > Issue Type: Improvement > Components: Fuseki > Affects Versions: Jena 4.4.0 > Reporter: Andy Seaborne > Assignee: Andy Seaborne > Priority: Minor > > Continues JENA-2248. > The upload code has become messy with duplication. > Functionality for HTML file upload {{<input type="file">}} has a dependency > on code using {{javax}}, and not {{jakarta}}. > {{HTML_FileUpload}} is dated and it buffers its input. > This is a step towards having the option to remove HTML file upload > capability. > A new general data uploader for sending data to a dataset will cover the > functionality better. > The only use of HTML file upload not covered is when the graph name is in the > multipart content. This predates SPARQL Graph Store Protocol which is a > better approach because the graph name is available at the start and so the > data can transactionally stream to the right destination. HTML file upload > can, in theory, supply the graph name after the data. > The UI "add data" tab uses GSP style to load data. -- This message was sent by Atlassian Jira (v8.20.1#820001)