On 18/08/2023 07:38, Gaspar Bartalus wrote:
Hi,
We would like to execute queries (construct) and updates (insert/delete
data) in one transaction.
Very similar I think to what Andy described here:
https://github.com/w3c/sparql-dev/issues/83
Something that has not quite ever managed to bubble up my todo list!
By exposing transaction control, there will have to be some defensive
features like timeouts because otherwise an errant client could disrupt
a server.
Andy
Gaspar
On Thu, Aug 17, 2023 at 7:54 PM Marco Neumann <[email protected]>
wrote:
Caspar, while you are looking into the extensions how would you like to use
transactions in your use case?
Marco
On Thu, 17 Aug 2023 at 13:44, Gaspar Bartalus <[email protected]> wrote:
Hi Lorenz,
Thanks for the quick response. That sounds indeed very promising.
Looking forward to knowing more details about the fuseki extension
mechanism, or a transaction module in particular.
Gaspar
On Thu, Aug 17, 2023 at 9:17 AM Lorenz Buehmann <
[email protected]> wrote:
Hi,
that is an open issue in the SPARQL standard and Andy already opened a
ticket [1] regarding this maybe w.r.t. an upcoming SPARQL 1.2
I think mixed query types are still not possible via standard Fuseki in
a single transaction, but indeed an extension like you're planning
should be possible. Andy is already working on a newer Fuseki extension
mechanism (it's basically already there) where you can plugin so-called
Fuseki modules. This would be the way I'd try to add this extension to
Fuseki.
Indeed, Andy knows better and can give you more specific code or
pointers - maybe he even has such a module or code part implemented
somewhere.
Regards,
Lorenz
[1] https://github.com/w3c/sparql-dev/issues/83
On 16.08.23 17:20, Gaspar Bartalus wrote:
Hi,
We’ve been using jena-fuseki to store and interact with RDF data by
running
queries over the http endpoints.
We are now facing the challenge to use transactional operations on
the
triple store, i.e. running multiple sparql queries (both select and
update
queries) in a single transaction.
I would like to ask what your suggestion might be to achieve this.
The idea we have in mind is to extend jena-fuseki with new http
endpoints
for handling transactions.
Would this be technically feasible, i.e. could we reach the internal
transaction API (store API?) from jena-fuseki?
Would you agree with this approach conceptually, or would you
recommend
something different?
Thanks in advance,
Gaspar
PS: Sorry for the duplicate, I have the feeling that my other email
address
is blocked somehow.
--
Lorenz Bühmann
Research Associate/Scientific Developer
Email [email protected]
Institute for Applied Informatics e.V. (InfAI) | Goerdelerring 9 |
04109
Leipzig | Germany
--
---
Marco Neumann
