Re: Querying URL with square brackets

> If you want a page for every book, don't use fragment URIs. Use > http://example.org/book/1 or http://example.org/book/1#this instead of > http://example.org/book#1. yes yes I agree with this. I only tried to present an example of yet another "quirk" between raw data and browsers (where this

Re: Querying URL with square brackets

> > in the case that I want to use these URLs with a web browser. > > I don't understand what the trouble with the above example is? The problem with # is that browsers treat them as the start of a local reference. When you open http://example.org/book#1 the server only receives

Re: Querying URL with square brackets

> What do you mean by human-readable here? For large technical systems it's > simply not feasible to encode meaning into the URI and I might even > consider it an anti-pattern. This is my problem. I do NOT want to encode any meaning into URLs, but I do want them to be human readable simply

Re: Querying URL with square brackets

Thank you a lot. FILTER(STR(?id) = "...") works, as suggested by Andy. I do recognize though that it is a hack, and that URLs should probably not have a [. But now I have trouble understanding UTF8 addresses. I would use random alphanumeric URLs everywhere if I could, or I would %-encode

Querying URL with square brackets

I have a few URLs containing square brackets like http://example.org/foo[1]bar I can create a TDB2 dataset without much problems, with warnings but no errors. I can also query these nodes "indirectly", that is if I query them by some property and not by URI. My problem is that I cannot query

ML archive no longer available

The "help and support"[1] page links to jena.markmail.org which unfortunately is no longer available (it has shut down). [1] https://jena.apache.org/help_and_support/

Re: Implicit default-graph-uri

> Subject: Re: Implicit default-graph-uri > > > > On 16/11/2023 11:35, Laura Morales wrote: > > I would like to configure Fuseki such that I can use 2 datasets from 2 > > different locations, as if they were a single dataset. > > This is my config.ttl: > > > &

Re: Implicit default-graph-uri

I also tried tdb:unionDefaultGraph like this fuseki:dataset [ a ja:RDFDataset ; tdb2:unionDefaultGraph true ; ja:namedGraph [ ... ] ; ja:namedGraph [ ... ] ; ] but it's not making any difference. I always get 0 triples when querying, unless I add

Implicit default-graph-uri

I would like to configure Fuseki such that I can use 2 datasets from 2 different locations, as if they were a single dataset. This is my config.ttl: <#> a fuseki:Service ; fuseki:endpoint [ fuseki:operation fuseki:query ] ; fuseki:dataset [ a ja:RDFDataset ;

Re: OOM Killed

> Could you try Java17? I did try Java 17 (default jre available from Debian) but I didn't notice any difference. I only ran 2 tests with Java 17 though, because the job takes a long time to fail/finish. I only noticed a significant difference when tweaking the GC options. However I did

Re: OOM Killed

> Have you tried different garbage collectors? WOAH I didn't even consider that before you mentioned it! I did this JVM_ARGS="-XX:+UseSerialGC -Xmx4G" ./fuseki-server ... and RAM usage of the java process peaked at 12GB $ cat /proc/108344/status | grep VmHWM VmHWM: 11916368 kB

Re: OOM Killed

Well, I think the OOM trigger that prompted Linux to kill Fuseki was the fact that I had a very small swap space (1GB). After adding a new swap partition (256GB) I don't see any errors anymore (OOM or heap space). On my PC with 16GB RAM, it used 2-3GB of swap and took approximately the same

Re: CVE-2023-32200: Apache Jena: Exposure of execution in script engine expressions.

Is there a demonstration of the exploit? I'd like to try it > Sent: Tuesday, July 11, 2023 at 6:44 PM > From: "Andy Seaborne" > To: annou...@apache.org, users@jena.apache.org > Subject: CVE-2023-32200: Apache Jena: Exposure of execution in script engine > expressions. > > Severity: important >

Re: OOM Killed

I've started Fuseki ./fuseki-server --loc=database --localhost --port=7000 /query and then I've started my script, with 16 threads (each one making a request to Fuseki). I did not set -Xmx, but I saw in htop that 4GB was chosen automatically. I did this on my PC with 16GB RAM, 2C4T CPU.

Re: OOM Killed

s are there? How many cores? > > - Which form of Fuseki are you using? > > what does >java -XX:+PrintFlagsFinal -version \ > | grep -i 'M..HeapSize` > > say? > > How are you sending the queries to the server? > > On 09/07/2023 20:33, Laura

Re: OOM Killed

- database contains around 2.5M triples and is ~4GB in size on disk

OOM Killed

I'm running a job that is submitting a lot of queries to a Fuseki server, in parallel. My problem is that Fuseki is OOM-killed and I don't know how to fix this. Some details: - Fuseki is queried as fast as possible. Queries take around 50-100ms to complete so I think it's serving 10s of

Filter nodes by type

This query returns two types of nodes SELECT ?node WHERE { ?node ?prop ?val } {'node': {'type': 'uri', 'value': ''}} {'node': {'type': 'triple', 'value': '' }} Is it possible to filter by type (I need only type=uri)?

Re: Faster TDB2 build?

Just a personal curiosity... are you building it on a SSD or HDD? What is your "triples loaded per second" rate? > Sent: Sunday, September 12, 2021 at 2:39 AM > From: "Cristóbal Miranda" > To: users@jena.apache.org > Subject: Faster TDB2 build? > > Hi, > > I'm running tdb2.tdbloader on

Re: riot --base option does not work with single letter URI schema

> It looks like a MS Windows drive letter, which then isn't handled very > gracefully. I'm not using Windows though.

Re: riot --base option does not work with single letter URI schema

> What version of Jena are you using? They all seem to work for me with 3.15.0 $ riot --version Jena: VERSION: 4.1.0 Jena: BUILD_DATE: 2021-05-31T20:32:25+

Re: riot --base option does not work with single letter URI schema

No no I mean "schema" indeed. Let me give a better example. These work: riot --base="isbn:" --syntax=ttl --output=nt <( echo "<0123> ." ) riot --syntax=ttl --output=nt <( echo "base <0123>

riot --base option does not work with single letter URI schema

This command riot --base="x:" --syntax=ttl --output=nt <( echo " ." ) returns this triple . instead of . Riot version 4.1.0.

sparql --loc=

Is there a reason why the "sparql" command in Jena (4.1.0) does not support the --loc option? Or is it just not implemented?

Re: Fuseki: how can I inject standard prefixes to every query?

What I mean is really simple. Basically I'd like to send queries like this to Fuseki: SELECT ?l WHERE { ?s rdfs:label ?l } this is not a valid query because it does not define the rdfs prefix. But I'd like to prepend some standard prefixes to every incoming request before they are

Fuseki: how can I inject standard prefixes to every query?

The idea is to prepend some standard prefixes at every incoming query, before it's executed, such that I don't have to write them every time.

Fuseki web UI not showing Table results when using RDF-star

I've just noticed that after inserting this kind of data :alice :knows :bob {| :since 2010 |} the web UI does not show any results in the Table tab when a query returns a "type":"triple".

Re: In-memory Fuseki keeps growing memory indefinitely even if idle

I can actually confirm that this was happening to me as well on a VM with 4GB RAM and TDB store (thus not in-memory). As more and more queries were made, RAM filled up, then the SWAP filled up, and at that point I had to reboot the machine. My solution was just to restart the server with a

Re: Does Jena use duck typing?

th Functions and Operators. > > But maybe I don't understand what's behind the question. > > On 19/07/2021 07:02, Laura Morales wrote: > > How is Jena able to index and search/compare properties with different data > > types? > > For example if I have this graph > &

RDF* multiple edges

In RDF*, would these two be considered different edges or one single edge? :alice :lives :NYC {| :from 2000; :to 2002 |} :alice :lives :NYC {| :from 2010; :to 2020 |}

Re: Does Jena use duck typing?

ing "abc"^^xsd:string. > > The specs say to prefer writing output without ^^xsd:string. > > In Turtle and related syntaxes: > > 42 is an xsd:integer == "42"^^xsd:integer > > 42.99 is an xsd:decimal > > 42e0 is an xsd;double. > > "2021-07-16" is

Does Jena use duck typing?

When I insert new triples into a Jena/Fuseki store, are *all* the quoted literals treated as strings by default unless I specify the type explicitly (eg. xsd:dateTime)? Or does Jena use duck typing to determine the best type fit for storing the value? What about numbers instead? Will Jena store

Re: Terms context

> Can you use subproperties? > > One point of RDF is to avoid collisions do data can be merged safely. I don't think subproperties are the answer. My problem is that the meaning of a property is defined within the boundaries of the whole vocabulary, whereas I'd like the meaning to be defined

Terms context

I have problems with the fact that, in English, words can have multiple meanings and can also be used as verbs, nouns, etc. In RDF, I feel like I'm compelled to define a term and its one meaning that is unique across the entire vocabulary. If I want to use the same term to mean two or more

[RDF*] How to model multiple uses of relations

In property graphs it's possible to use a relation multiple times, for example Foobar -[president_of {from: 1950, to:1954}]-> Japan Foobar -[president_of {from: 1962, to:1966}]-> Japan where "from" and "to" are to properties of the "president_of" relation. This is an old problem that

Is it possible to use UTF8 IRIs in Turtle?

Is there a way to write UTF8 IRIs with Turtle without all the %-encoded characters? I mean like this or or ex:"alice smith"? The only way that I know to write those characters is like this , ie. by writing the encoded URI myself. Is there any syntax that I can use to write UTF8 characters

Re: Turtle* same term twice

ot; > To: users@jena.apache.org > Subject: Re: Turtle* same term twice > > > > On 21/12/2020 11:34, Laura Morales wrote: > > Pardon, a couple of things that are not completely clear to me: > > > > - is:a :b :c {| :d "object" |}a valid Turtle syntax? I've never

Re: Turtle* same term twice

t; > > > On 21/12/2020 07:47, Lorenz Buehmann wrote: > > > > On 20.12.20 17:19, Andy Seaborne wrote: > >> > >> > >> On 20/12/2020 09:20, Lorenz Buehmann wrote: > >>> > >>> On 19.12.20 2

Turtle* same term twice

Is this << :a :b :c >> :d ; :e . the equivalent of this? << :a :b :c >> :d . << :a :b :c >> :e . Will Fuseki/Jena store them and treat them the same exact way?

Turtle* multiple terms at once

All the examples online about RDF* use a one-triple term, like this (taken from Fuseki docs) << :john foaf:name "John Smith" >> dct:source . I wonder if there is any way in Turtle* to apply the same properties to multiple terms at once? Something like this

Re: Indexing datatypes

> Andy can confirm, but AFAIK everything is indexed in Jena. > And a number is stored as such . Sorry how does/can it index this? :alice :age 21; :age "twenty-one" . By converting everything to strings?

Indexing datatypes

I'm able to configure Fuseki for fulltext search with Lucene, but I don't see any other type of indexes in the documentation. If there is a property that is (ab)used to link multiple datatypes, say for example Turtle -- :alice :age 21; :age "twenty-one" . How is this stored by

Re: Does Jena support RDF*?

> This is an alternative to RDF* , AFAIK . > If someone is interested, I can document the structure of the secondary TDB > database. I don't want to abuse your time but yes, this would be helpful. Even just a sketch of it, just to get the idea.

Re: Does Jena support RDF*?

> What's your interest in RDF*? There seems to have been this endless debate about triplestores vs property graphs since as far as I can remember. This new standard apparently promises to be the best of both world by supporting RDF plus what they call "richer types" (aka nodes, vertexes).

Does Jena support RDF*?

I've only recently discovered the existence of RDF* and Turtle*. Looks like they were introduced around 2019. Does Jena have support for these in the current release?

Re: Fuseki - Grant permissions to all by default

> I was able to find the Shiro.ini in fuseki2 code, but not in fuseki1. Can > you please point me to its location in earlier version? The current release of Fuseki is 3.13; I doubt Fuseki 1 is still supported and maybe it didn't even have Shiro at all. If you start the server without a

Re: Fuseki - Grant permissions to all by default

have multiple instances of it running, that means a new run > folder for every run and manually editing Shiro for each run too. > > On Sun, 15 Dec, 2019, 12:13 PM Laura Morales, wrote: > > > I think you're talking about the shiro.ini file but I don't think the > > q

Re: Fuseki - Grant permissions to all by default

I think you're talking about the shiro.ini file but I don't think the question is very clear. What is the problem with editing one file manually? > Sent: Sunday, December 15, 2019 at 7:32 AM > From: "Amandeep Srivastava" > To: Users@jena.apache.org > Subject: Fuseki - Grant permissions to

Re: TDB optimization query

This (http://mail-archives.apache.org/mod_mbox/jena-users/201712.mbox/%3CCAHM9nqQfOnyhBQj=jr-i9ieqhiv7vflfnleoycmhsupdd7n...@mail.gmail.com%3E) is an old thread, somewhat related to this question. > Sent: Tuesday, November 12, 2019 at 1:29 PM > From: "Amandeep Srivastava" > To:

Re: TDB optimization query

tdb2.tdbloader has a --loader=parallel option, you could try with that. From my past experience, the decreasing loading speed is caused by IO saturation. Do you have an HDD or an SSD? > Sent: Tuesday, November 12, 2019 at 1:29 PM > From: "Amandeep Srivastava" > To: Users@jena.apache.org >

Re: No such type:

$ cat run/config.ttl @prefix :<#> . @prefix fuseki: . @prefix rdf: . @prefix rdfs: . @prefix tdb: . @prefix ja:

No such type:

I'm trying to enable full text search on a Fuseki v3.12 instance but I get the error shown below. The assembler is pretty much a copycat of the documentation, with a Lucene text index. The assembler contains the prefix "text: ". Is this a bug? $ java -cp

Re: [ANN] Apache Jena 3.13.0

> JENA-1731: Fuseki endpoint configuration Is updating 3.12 to 3.13 going to break server configuration? I wonder if there is a description of the new configuration?

Re: [ANN] Apache Jena 3.13.0

Thank you devs for working on Fuseki. > Sent: Sunday, September 29, 2019 at 10:56 AM > From: "Andy Seaborne" > To: "users@jena.apache.org" > Subject: [ANN] Apache Jena 3.13.0 > > The Apache Jena development community is pleased to > announce the release of Apache Jena 3.13.0. > > This release

Fuseki vs Rya

Now that Rya has been promoted to top-level project, I'd like to hear your comments about Fuseki vs Rya. Pros of both, when and why I should use one or the other. Thanks!

Re: Riot warning for Unicode NFC IRIs

> Both Wikipedia and DBpedia can not handle NFKC: > https://en.wikipedia.org/wiki/Ranma_1⁄2 The wikipedia link is https://en.wikipedia.org/wiki/Ranma_%C2%BD

Re: Riot warning for Unicode NFC IRIs

Valid URIs are basically ASCII strings. I don't think you can stick any other character in there. > Sent: Friday, September 20, 2019 at 9:11 AM > From: "Sebastian Hellmann" > To: users@jena.apache.org > Subject: Riot warning for Unicode NFC IRIs > > Hi all, > > I really don't understand these

Re: "not in a transaction", but only sometimes

> > <#dataset> rdf:type tdb:DatasetTDB ; > > tdb:location "DB" ; > > tdb:unionDefaultGraph true ; > > . > > The dataset can have a ja:context setting and that can be the one for > query union graph. Not "?default-graph-uri=" which is protocol and per >

Re: "not in a transaction", but only sometimes

> :dataset a ja:RDFDataset ; >ja:namedGraph [ ja:graphName "http;//example/name" ; >ja:graph :graph1 ] ; >ja:namedGraph ... a quick test of this one with ?default-graph-uri=urn:x-arq:UnionGraph on Fuseki 3.12.0 seems to run just fine (actually, it seems to respond

Re: "not in a transaction", but only sometimes

> set union mode on the dataset I mean you're talking about this <#dataset> rdf:type tdb:DatasetTDB ; tdb:location "DB" ; tdb:unionDefaultGraph true ; . > or (3.13.0) the service for default to query all graphs. is this referring to "?default-graph-uri=" or

Re: "not in a transaction", but only sometimes

> Presumably this is more than one TDB database. yes, a few 10s > What works is when graphs are in the same database. this is not easy for me to switch to. My problem is that I'm pulling multiple sources (RDF) from different places, and I want all of them together to be my default graph. If I

Re: "not in a transaction", but only sometimes

suggest to me how to setup a working UnionModel with Fuseki 3.12.0? Thanks! > Sent: Wednesday, September 11, 2019 at 10:46 AM > From: "Laura Morales" > To: users@jena.apache.org > Cc: users@jena.apache.org > Subject: Re: "not in a transaction", but only someti

Re: "not in a transaction", but only sometimes

> Forgot to mention: Fuseki 3.12 I fear guys that you've introduced a new regression in 3.12.0 regarding the UnionModel/transactions/TDB. I've spent hours debugging my code and Fuseki configuration, until I noticed that my dev server was 3.6.0 but in the prod server I had installed 3.12.0 (the

Re: "not in a transaction", but only sometimes

Forgot to mention: Fuseki 3.12, and this is the error [2019-09-10 17:02:32] QueryIteratorCheck WARN Open iterator: TripleMapper/255 [2019-09-10 17:02:32] Fuseki WARN [7] RC = 500 : Not in a transaction org.apache.jena.tdb.transaction.TDBTransactionException: Not in a transaction at

"not in a transaction", but only sometimes

Just out of curiosity, has someone else here experienced a query that returns "not in a transaction" only sometimes? I have a simple dataset like this :dataset a ja:RDFDataset ; ja:defaultGraph :union :union a ja:UnionModel ; ja:subModel :graph1 #TDB ja:subModel

Re: % character in mailto: URI

> Is not a legal mailto: URI? Or does it > need to be encoded somehow? That is not a legal URI, strictly speaking. Look up https://en.wikipedia.org/wiki/Percent-encoding I've never in my life seen an email address with a percent sign, but if you *must* use it then you have to encode it, it

Re: Long URIs

Everything else being equal, no. Not in any noticeable way. > Sent: Wednesday, August 28, 2019 at 5:37 PM > From: "Piotr Nowara" > To: users@jena.apache.org > Subject: Long URIs > > Hi, > > does in your experience using very long URIs (like more than 100 > characters) affect SPARQL performance?

Re: RE: Sensible size limit for SPARQL update payload to Fuseki2?

> from SPARQLWrapper import SPARQLWrapper > > # a lot longer > myString = "INSERT DATA {}" > > def insertFromString(url, sparql): > endpoint = SPARQLWrapper(url) > endpoint.setQuery(sparql) > endpoint.method = 'POST' > endpoint.query() > >

Re: Sensible size limit for SPARQL update payload to Fuseki2?

Basically, this request should work? POST /database HTTP/1.1 Host: example.com Content-Type: application/sparql-update INSERT DATA { < 100 MB of triples > } > Sent: Wednesday, August 07, 2019 at 10:44 AM > From: "Andy Seaborne" > To: users@jena.apache.org > Subject: Re:

Re: RE: Sensible size limit for SPARQL update payload to Fuseki2?

I don't know myself how to configure jetty, even less with Fuseki. I hope for you somebody else on the list does. Regarding LOAD however, you should be able to use HTTP URIs. > Sent: Tuesday, August 06, 2019 at 7:01 PM > From: "Pierre Grenon" > To: "'users@jena.apache.org'" > Subject: RE:

Re: Sensible size limit for SPARQL update payload to Fuseki2?

Your best option is to look at the Fuseki logs for the exact error. I've personally never POSTed so much data to Fuseki, but I feel like it should not be be a problem unless something is timing out the connection, or truncating the POST data, or your triples contain syntax errors. Another

Re: RE: Sensible size limit for SPARQL update payload to Fuseki2?

uess I was lazy and hoping for an easy answer if this clogged up Fuseki > > in > > known ways and whether that might be addressed through config (memory, > > thread, whatnots). > > > > Will double check a few things and report then. > > > > With many than

Re: Sensible size limit for SPARQL update payload to Fuseki2?

How long is your query?? Personally I'm not aware of any such limitations, especially when POSTing, but other people here definitely know better than me if there is one or not. If there is a limit, let's say even just 1MB, you need a *very* long query to break it. 500 is a general "internal

Re: possible to run a TDB2 DB with a fuseki GUI and still have commandline query access?

; Hmm. What about submitting queries against the SPARQL endpoint, using a > different client? Would that work? If I do that, would there be any loss of > functionality compared to what I could get by using the tdbquery tool? > > --Jeff > > On Tue, Jul 23, 2019, 8:15 PM Laura Morales wrote

Re: possible to run a TDB2 DB with a fuseki GUI and still have commandline query access?

As far as I know it's not possible to run the CLI commands on a live dataset. You have to stop Fuseki first. > Sent: Wednesday, July 24, 2019 at 4:28 AM > From: "Jeff Lerman" > To: users@jena.apache.org > Subject: possible to run a TDB2 DB with a fuseki GUI and still have > commandline query

Re: About fuseki2 load performance by java API

> tdb2.tdbloader --loader=parallel > > but it still becomes random IO (moves disk heads) > > I haven't tried it extensively on an HDD - I'd be interested in hearing > what happens. oh nice! I completely missed it. I've tried it with a 67GB .nt file from LinkedGeoData on the same 750GB HDD but

Re: RE: About fuseki2 load performance by java API

I had a similar problem when trying to load wikidata on my laptop with 8GB RAM, i7 CPU, 750GB HDD. It started fine but then slowed to a crawl after about 100 million triples. I don't think CPU or RAM are the problem, it's probably to do with disk queues or caches or something like that. IIRC

Re: What detail steps are required to Restore a TDB from the back-up file

To restore from Fuseki web UI, in the "manage datasets" page there are buttons for creating new stores as well as for selecting your files containing the triples ("upload data"). >From the CLI you can type "tdbloader --help" for the list of options. Example: "tdbloader --loc mydb data.nt" will

Re: How does one restore a TDB Back-up file created via Apache Jena Fuseki...

Backups are automatically saved inside $FUSEKI_BASE/backups/ as .nq files. You either reload those files from the same web interface or create a new TDB store using tdbloader(2). Or you can probably load them into another existing TDB store using tdbupdate. BTW you can also backup from the CLI

Fw: Import rules from another GenericRuleReasoner file

@include . reference: https://jena.apache.org/documentation/inference/#rules > Sent: Friday, July 05, 2019 at 1:21 PM > From: "Laura Morales" > To: jena-users-ml > Subject: Import rules from another GenericRuleReasoner file > > I have a file that contains rul

Import rules from another GenericRuleReasoner file

I have a file that contains rules for a GenericRuleReasoner. Is it possible to import another file containing more rules, from the former?

Re: RDFDataset dump inferred triples only

ase and complete to a file and use > sort(1) and comm(1). > > If there are bnodes, some (slow!) query with a GRAPH/FILTER (NOT) EXISTS > might do it. > > Andy > > On 02/07/2019 11:12, Dave Reynolds wrote: > > On 02/07/2019 11:09, Laura Morales wrote: > >>

Re: RDFDataset dump inferred triples only

Can I do this with one of the Jena command line tools? > Sent: Tuesday, July 02, 2019 at 11:34 AM > From: "Dave Reynolds" > To: users@jena.apache.org > Subject: Re: RDFDataset dump inferred triples only > > On 02/07/2019 09:19, Laura Morales wrote: > > H

RDFDataset dump inferred triples only

How can I dump to a .nt files *only* the inferred triples in a RDFDataset? In other words, I have a RDFDataset with a GenericRuleReasoner InfModel, and I would like to export all the inferred triples to a file.

Fw: GenericRuleReasoner live rule update

Thank you so much! > Sent: Tuesday, June 25, 2019 at 10:39 AM > From: "Laura Morales" > To: jena-users-ml > Subject: GenericRuleReasoner live rule update > > Is it possible to live-reload GenericRuleReasoner rules? That is without > restarting Fuseki?

GenericRuleReasoner live rule update

Is it possible to live-reload GenericRuleReasoner rules? That is without restarting Fuseki?

Fw: Cannot setup GenericRuleReasoner

It seems to work if I replace the rule [ okrule: (?s a ex:Person) -> (?s ex:works "OK") ] with this rule [ okrule: (?s rdf:type ex:Person) -> (?s ex:works "OK") ] is this a bug? > Sent: Tuesday, June 25, 2019 at 9:40 AM > From: "Laura Mor

Cannot setup GenericRuleReasoner

What's wrong with this configuration? It doesn't seem to infer any triples when I query the dataset (Fuseki 3.6.0). It doesn't show any errors either. config.ttl PREFIX : <#> PREFIX fuseki: PREFIX

Re: INSERT if not exists

Thank you very much! (For my future reference: https://www.w3.org/TR/rdf-sparql-query/#emptyGroupPattern) > Sent: Monday, June 17, 2019 at 10:55 AM > From: "Andy Seaborne" > To: users@jena.apache.org > Subject: Re: INSERT if not exists > > On 16/06/2019 21:01, Laur

INSERT if not exists

I would like to add a new node if and only if another node with the same properties does not exists. Something like this: INSERT { ex:item-X a ex:Item; ex:serial "XYZ" . } if and only if there is not already another node with (ex:serial "XYZ") After trial and

Fuseki graph constraints

Does Fuseki support graph constraints? Something like the equivalent of "composite primary keys" in SQL?

Re: Fuseki union of two TDB(2) datasets

> JENA-1667 I think my problem is exactly the same one described by Ashley Sommer in JENA-1663.

Re: tdb2.tdbsync

yes yes of course I can reload everything, that's what I do already. I simply thought it might be quite handy, for instance, if I had a folder containing an arbitrary number of rdf files, and as these files change I could call a tdb2.tdbsync tool that automatically updates a tdb dataset with

tdb2.tdbsync

This is only a potential suggestion, not an issue. I think it could be handy to have a tdb2.tdbsync tool for synchronizing a TDB dataset with a rdf file(s). Something to use like this: tdb2.tdbsync --loc dataset data.nt, and will automatically delete/insert tuples to maintain the dataset

Re: Fuseki union of two TDB(2) datasets

Thank you! > Sent: Thursday, June 13, 2019 at 1:05 AM > From: "ajs6f" > To: users@jena.apache.org > Subject: Re: Fuseki union of two TDB(2) datasets > > Filed as https://issues.apache.org/jira/browse/JENA-1721. > > ajs6f

Re: Fuseki union of two TDB(2) datasets

> > PS: this only works with TDB1 right? Any way to make it work with TDB2? > > No. Works for anything and mixtures: > > Change the tdb:GraphTDB and tdb:DatasetTDB > to tdb2:GraphTDB2 and tdb2:DatasetTDB2 TDB1 works, but with TDB2 all I get is a waning: "500 : Not in a transaction". This is the

Re: Fuseki union of two TDB(2) datasets

> > The reason why I would like to be able to do this, instead of merging one > > dataset into another, is simply because the two datasets come from > > different origins. > > With an overlap of named graphs? Potentially yes, but for my particular case I can work around it by renaming my

Re: Fuseki union of two TDB(2) datasets

> From the Java side, there is UnionDatasetGraph, which would be able to give > you a view over two datasets, but I'm not sure we ever wrote an assembler for > that. I don't see one in the codebase, although it shouldn't be too hard. > There are DatasetDescriptionAssembler and

Re: Fuseki union of two TDB(2) datasets

Basically I have a Fuseki server with 1 TDB dataset containing multiple graphs, like this (stripped down configuration): <#service> rdf:type fuseki:Service ; fuseki:dataset <#dataset> ; . <#dataset> rdf:type tdb:DatasetTDB ; tdb:location "DB" ;

Fuseki union of two TDB(2) datasets

Can I configure Fuseki to use the union of two TDB or TDB2 datasets as the default union graph?

  1   2   3   4   5   >