Re: [rdf4j-dev] NativeStore initialization with strange error in log

[Jeen Broekstra <jeen.broekstra@xxxxxxxxx>]

Yeah, I've noticed this too. Like Havard said, it's nothing to worry about: it's just the native store noticing there is no cache file yet and then (re)creating it. I agree though that in the case of a newly created store, we should somehow suppress that error as it may freak people out. 

Jeen

On Tue, Oct 1, 2019 at 6:34 AM Håvard Ottestad <hmottestad@xxxxxxxxx> wrote:

There isn’t anything wrong here. The native store now has a context cache curtesy of Jeen.

While initializing is tries the read and verify the cache. If it fails for any reason, corrupt files or missing files, then it throws an exception and the cache is regenerated.

There isn’t any support for handling the initial initialization in any special way. This could probably be improved.

Håvard

> On 30 Sep 2019, at 22:18, Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:
>
_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/rdf4j-dev