You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (Jira)" <ji...@apache.org> on 2021/12/29 17:53:00 UTC
[jira] [Comment Edited] (JENA-2230) Assembler for GeoSPARQL
[ https://issues.apache.org/jira/browse/JENA-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17466547#comment-17466547 ]
Andy Seaborne edited comment on JENA-2230 at 12/29/21, 5:52 PM:
----------------------------------------------------------------
Hi Greg,
I'm not sure the best way to hook into update in this case. In other places there is a dataset that wraps the base dataset so it sees "add(quad)" etc. e.g. That might be the way here.
The changes intercepted in jena-text (which is quite old so there may be equivalent general ways elsewhere):
[https://github.com/apache/jena/blob/main/jena-text/src/main/java/org/apache/jena/query/text/changes/DatasetGraphTextMonitor.java]
DatasetGraphText is the query/search machinery.
DatasetGraphTextMonitor is a DatasetGraphWrapper But this does get entangled with transactions because a change may not happen for real.
To simplify that, the transaction support could be MRSW (Multiple reader OR Single Writer), not "AND Single Writer".
We can create some space for ourselves - the documentation for the assembler can initially say "read-only".
The other case is updating the TDB database offline. All we can do is say "delete the spatial.index" and it will be rebuilt on start-up. That isn't too bad. jena-text doesn't solve the situation either. It has an index rebuild command line tool.
was (Author: andy.seaborne):
Hi Greg,
I'm not sure the best way to hook into update in this case. In other places there is a dataset that wraps the base dataset so it sees "add(quad)" etc. e.g. That might be the way here.
The changes intercepted in jena-text (which is quite old so there may be equivalent general ways elsewhere):
[https://github.com/apache/jena/blob/main/jena-text/src/main/java/org/apache/jena/query/text/changes/DatasetGraphTextMonitor.java]
DatasetGraphText is the query/search machinery.
DatasetGraphTextMonitor is a DatasetGraphWrapper But this does get entangled with transactions because a change may not happen for real.
To simplify that, the transaction support could be MRSW (Multiple reader OR Single Writer), not "AND Single Writer".
We can create some space for ourselves - the documentation for the assembler can initially say "read-only".
The other case is updating the TDB database offline. All we can do is say "delete the spatial.index" and it will be rebuilt on start-up. That isn't too bad.
> Assembler for GeoSPARQL
> -----------------------
>
> Key: JENA-2230
> URL: https://issues.apache.org/jira/browse/JENA-2230
> Project: Apache Jena
> Issue Type: New Feature
> Components: GeoSPARQL
> Affects Versions: Jena 4.3.2
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Major
> Fix For: Jena 4.4.0
>
>
> An assembler for the GeoSPARQL engine.
> This is for {{jena-geosparql}}, making it a loadable module for Jena and usable with any Fuseki server.
> jena-fuseki-geosparql and its command line are unchanged.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)