[jira] [Commented] (JENA-2270) Improve Fuseki data upload functionality.
[
https://issues.apache.org/jira/browse/JENA-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487452#comment-17487452
]
ASF subversion and git services commented on JENA-2270:
---
Commit 257602c98cdde023a2b21172c5c4d81a293841b2 in jena's branch
refs/heads/main from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=257602c ]
Merge pull request #1187 from afs/jena2270-upload
JENA-2270: Improve Fuseki data upload functionality.
> 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 {{}} 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)
[jira] [Commented] (JENA-2270) Improve Fuseki data upload functionality.
[
https://issues.apache.org/jira/browse/JENA-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487450#comment-17487450
]
ASF subversion and git services commented on JENA-2270:
---
Commit 66cc7ece693ebf2c64a860587760b57ac53574cf in jena's branch
refs/heads/main from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=66cc7ec ]
JENA-2270: Remove HTML_FileUpload
> 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 {{}} 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)
[jira] [Commented] (JENA-2270) Improve Fuseki data upload functionality.
[
https://issues.apache.org/jira/browse/JENA-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487449#comment-17487449
]
ASF subversion and git services commented on JENA-2270:
---
Commit 7bdc3a177ba62205e0146232b54cd631dbb09f2f in jena's branch
refs/heads/main from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=7bdc3a1 ]
JENA-2270: Upload data service; share with GSP_RW
> 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 {{}} 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)
[jira] [Commented] (JENA-2270) Improve Fuseki data upload functionality.
[
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 {{}} 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)
[jira] [Commented] (JENA-2270) Improve Fuseki data upload functionality.
[
https://issues.apache.org/jira/browse/JENA-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486377#comment-17486377
]
Martynas Jusevičius commented on JENA-2270:
---
{{multipart/form-data}} is useful when multiple files are uploaded at once.
[GSP specifies it for
{{POST}}|https://www.w3.org/TR/sparql11-http-rdf-update/#http-post]:
{quote}When used with POST this operation MUST be understood as a request that
the origin server perform an RDF merge of the graphs - that the documents
submitted with the multipart form are a serialization of - into the RDF graph
content identified by the request or encoded IRI. In such a case, if the
{{Content-Type}} is not provided, implementations MAY attempt to determine it
from the file's extension rather than respond with {{400 Bad Request}}.{quote}
> 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 {{}} 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)
[jira] [Commented] (JENA-2270) Improve Fuseki data upload functionality.
[
https://issues.apache.org/jira/browse/JENA-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486350#comment-17486350
]
Andy Seaborne commented on JENA-2270:
-
No work in the UI, all server side refinement.
I've added a JIRA component tag "Fuseki UI" so tickets can mark this.
The UI isn't triggering a path that went to the old "upload" endpoint.
The {{file-upload}} JS component does use multipart uploads for files but it
seems the GSP endpoint already supports this. The GSP endpoint supports regular
POST/PUT to the dataset when no {{?default}} or {{?graph=}} is present.
The ticket is about clearing up the code in the server.
Fuseki has "dispatch by content-type" on the dataset URL although the UI uses
{{/data}}.
The UI does not allow the complicated case of "many files, different graph
names" in one upload which the full {{application/multipart}} does. The name
field can be after the file contents (odd but legal) so the receiver does not
know the destination at the start of each part and it is buffered in memory.
For everyone's sanity, users and implementers, sending a TriG file for this
case is cleaner.
_Update:_
{{file-upload}} does not send multiple files in one go, nor did the old UI.
They both do multiple parallel requests.
The server log has one request per file, and the request overlap.
The only difference is that pre-4.4 uses the dataset URL, and now the UI uses
{{/datasets/data}}.
> 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 {{}} 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)
[jira] [Commented] (JENA-2270) Improve Fuseki data upload functionality.
[
https://issues.apache.org/jira/browse/JENA-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486192#comment-17486192
]
Bruno P. Kinoshita commented on JENA-2270:
--
>The UI "add data" tab uses GSP style to load data.
So that means there is no work in the UI? Is it only removing code that's not
used anymore?
> Improve Fuseki data upload functionality.
> -
>
> Key: JENA-2270
> URL: https://issues.apache.org/jira/browse/JENA-2270
> Project: Apache Jena
> Issue Type: Improvement
>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 {{}} 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)
