Shouldn't also
1.8
1.8
be a minimum of 17 given the Jena version 5.0.0-rc1?
Best regards,
Øyvind
On Tue, Mar 12, 2024, 14:54 Andy Seaborne wrote:
>
>
> On 12/03/2024 13:02, Anna P wrote:
> > Hi Lorenz,
> > Thank you for your reply. Yes, I used maven to build the project. Here
> are
> >
What does the content of the tdb2 folder look like?
I think compact by default never deletes the old data, but you have
parameters for making it delete the old content on completion.
`--deleteOld` can be supplied to the tdb2.tdbcompact command line tool and
`?deleteOld=true` can be supplied to
Hi Adrian,
>From the git history I can see that we were using Elasticsearch 6.4.3 and
Fuseki 3.10.0 when we experimented with it and had it running.
AFAIK Both Lucene and Elasticsearch indexes the data for you as the
triplestore updates, without having to do anything, using a normal
Hi Adrian,
We tried the elastic-search module when it was available and had your
use-case in mind with facets. But as far as I remember I don't think it was
possible to use aggregations (at least from the sparql side of things).
I understood the elasticsearch-module as an alternative to the
I haven't tried it, but it looks like it is implemented, and you can
configure a SHACL service on datasets, in the assembler for Fuseki.
https://jena.apache.org/documentation/shacl/#integration-with-apache-jena-fuseki
You can then use the api and post shapes as files for validating datasets:
Hi,
This is also something I've thought about, since we have a dated
elasticsearch integration for creating facets from endpoints, and we use
aggregated sparql queries for counting which sometimes becomes slow-ish,
and has to be turned off for larger datasets.
An idea I had around 3 in how it
/#/manage for admin actions.
Best regards,
Øyvind Gjesdal
On Fri, Oct 21, 2022 at 12:27 PM Mikael Pesonen
wrote:
>
> jena-fuseki-4.3.2 works in same setup, 4.6.0 and 4.6.1 don't. Any idea?
>
> On 17/10/2022 16.45, Mikael Pesonen wrote:
> >
> > Also /opt/xx/jena is link to /o
Hi Pawel,
I think this could be due to the text:query being evaluated late in the
query, and other statements first computing many results, before the text
query limits it down. Maybe the contains filter gets applied earlier?
Would reordering the statements, expanding the property path and/or
I've recently completed some upgrades using the fuseki binaries, first with
major versions, from different 3.X to 4.4 and then again from 4.4 to 4.5.
* I noticed that on the upgrades my tdb2 databases returned no results in
sparql after upgrading, but they both had similar file size in the
I have a working setup (on fuseki 3.14) where I can see different results
using AND/OR, and where "~" fuzzy operator also works.
Differences from your config seem to be that I haven't configured much for
the index, only the directory and entity map. Would testing if a minimal
config works and
Looking at our very similar config (based on the fuseki examples) only
difference I see (except from the additional library) is that our config
uses TDB, and your config uses TDB2. I believe tdbloader2 generates tdb1
data ( I could be wrong), since I remember using it pre tdb2 release, so
there
11 matches
Mail list logo
