Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
NativeStore forceSync parameter not configurable and not consistently applied #749
The NativeStore has a
However, the parameter is not exposed in the NativeStoreConfig, not read or configured by the NativestoreConfigFactory, and not configurable via either the CLI Console or the RDF4J Workbench.
In addition, it is not consistently used and enforced in all internal sync operations in the NativeStore.
To fix, we should make sure the parameter is user-configurable (in the Config class, the native store templates, and the Console and Workbench), and that it is consistently used for all files involved in native store disk access, upon commit.
A possible follow-up issue is re-evaluation its performance impact. The assessment that it slows things down was done when Sesame 2.0 was first released, and a lot has changed in both the native store implementation and Java NIO performance, as well.