Dear Andy,
Thanks for looking into this!
I’ve added the relevant info to the GitHub issue.
Best regards,
Samuel
On 2024/02/07 20:41:49 Andy Seaborne wrote:
> Recorded as https://github.com/apache/jena/issues/2254
>
> On 06/02/2024 23:06, Andy Seaborne wrote:
> > Hi Samuel,
> >
> > This is
Recorded as https://github.com/apache/jena/issues/2254
On 06/02/2024 23:06, Andy Seaborne wrote:
Hi Samuel,
This is when the server exists for some reason?
(If it's an internal exception, there should be a stack trace in the log
file.)
What operating system are you running on?
What's in
Hi Samuel,
This is when the server exists for some reason?
(If it's an internal exception, there should be a stack trace in the log
file.)
What operating system are you running on?
What's in the new Data-0002 directory?
It does look like some defensive measures are needed to not choose to
Hi everybody,
I recently noticed that when Fuseki (4.10.0) is stopped during a compaction
task (started via the HTTP endpoint `/$/compact/{name}?deleteOld=true`)
then it uses the new and still incomplete database (e.g. Data-0002 instead of
the original non-compacted Data-0001) when it is
