Re: query performance on named graph vs. default graph

> On Mar 24, 2024, at 5:08 PM, Andy Seaborne wrote: > > > > On 21/03/2024 00:21, Jim Balhoff wrote: >> Hi Lorenz, >> These both do speed things up quite a bit, but it prevents matching patterns >> that cross graphs in the case where I include m

Re: query performance on named graph vs. default graph

t; FROM NAMED > FROM NAMED > FROM NAMED ... > FROM NAMED > { > GRAPH ?g { > ... > } > } > > or > > SELECT * > { > VALUES ?g { ... } > GRAPH ?g { > ... > } > } > > > does that work better? > > On 19.03.24

Re: query performance on named graph vs. default graph

Hi Andy, > On Mar 19, 2024, at 5:02 AM, Andy Seaborne wrote: >> > > Hi Jim, > > What happens if you use GRAPH rather than FROM? > > WHERE { > GRAPH { > ?cell rdfs:subClassOf cell: . > ?cell part_of: ?organ . > ?organ rdfs:subClassOf organ: . >

query performance on named graph vs. default graph

Hi, I’m running a particular query in a Fuseki server which performs very differently if the data is in a named graph vs. the default graph. I’m wondering if it’s expected to have a large performance hit if a named graph is specified. The dataset consists of ~462 million triples; it’s this

Re: In using RIOT I encounter the "64000" entity expansions error.

> On Oct 6, 2023, at 3:46 AM, Andy Seaborne wrote: > > > On 28/06/2023 09:26, Damion Dooley wrote: >> I’m using RIOT to parse a large food ontology in owl rdf/xml format. > > Damion, > > Is that data publicly available? > > There's a new RDF/XML parser for Jena in the pipeline and I'd like

Re: read-only Fuseki TDB2

> On Sep 18, 2023, at 11:09 AM, Andy Seaborne wrote: > > > > On 18/09/2023 15:35, Jim Balhoff wrote: >> Thanks, I think that’s basically what I’ve got. The only operation I have >> enabled is 'fuseki:query’. But Fuseki still complains if the filesystem is >

Re: read-only Fuseki TDB2

eed: > https://jena.apache.org/documentation/fuseki2/fuseki-configuration.html#read-only-service > > On Mon, Sep 18, 2023 at 2:43 PM Jim Balhoff wrote: >> >> Hi, >> >> Is it possible to run a Fuseki server using a read-only TDB2 directory? I’d >> like to run a qu

Re: read-only Fuseki TDB2

g/manual-of-hdt-integration-with-jena/ will > suit your need. > Cheers > Peter > > On Mon, 18 Sept 2023, 13:43 Jim Balhoff, wrote: > >> Hi, >> >> Is it possible to run a Fuseki server using a read-only TDB2 directory? >> I’d like to run a query-only S

read-only Fuseki TDB2

Hi, Is it possible to run a Fuseki server using a read-only TDB2 directory? I’d like to run a query-only SPARQL endpoint, no updates. However I get an exception at startup if the filesystem is read-only. Does Fuseki need to acquire the lock even if updates are turned off? Thank you, Jim

Re: Best practice to combine simple queries

I use ParameterizedSparqlString to build my SPARQL queries. > On Apr 12, 2020, at 5:54 PM, Mike Welch > wrote: > > Thanks Jim, I did a bit of perf comparison (detail below). Now my question > is: how do I use the Jena SelectBuilder interfaces to formulate such a > query? Calling

Re: OWL2 Support in Jena

keys. It’s written in Scala but you can use it in Java programs. Best regards, Jim Balhoff > On May 25, 2017, at 4:34 AM, Rob Vesse <rve...@dotnetrdf.org> wrote: > > Like all open source projects, we rely upon the volunteers to do the work. > Unlike higher profile projects e.

Re: OWL property chains

, but straightforward to write. Jim > On Dec 20, 2016, at 4:13 PM, Dave Reynolds <dave.e.reyno...@gmail.com> wrote: > > Hi, > > On 20/12/16 19:23, Jim Balhoff wrote: > >> Do any of the Jena reasoners support OWL property chains? > > No,

OWL property chains

Hi, Do any of the Jena reasoners support OWL property chains? The OWLMicroReasoner seems to support most of what I need except for property chains. I’m wondering if it is possible to extend this reasoner with a property chain rule, or if I should just include the rules I need in a

Re: controlling JSON-LD output

On Aug 12, 2014, at 10:20 AM, Andy Seaborne a...@apache.org wrote: On 11/08/14 20:03, Jim Balhoff wrote: Hi, I am trying to output a Model as JSON-LD. It's working fine, but now I would like to make some changes to how the output is structured. For example, I'd like to define a @reverse

Re: controlling JSON-LD output

On Aug 13, 2014, at 4:19 PM, Andy Seaborne a...@apache.org wrote: Jim, Thanks for trying. It's probably a question for jsonld-java directly. Jena is using jsonld-java and maybe the writer is being too simplistic. If there improvements, then I'm very willing to add them but when I

controlling JSON-LD output

Hi, I am trying to output a Model as JSON-LD. It's working fine, but now I would like to make some changes to how the output is structured. For example, I'd like to define a @reverse property in the @context so that I can output certain triples in the reverse direction. Is it possible to