Aklakan opened a new issue, #3473: URL: https://github.com/apache/jena/issues/3473
### Version 5.5.0, 5.6.0-SNAPSHOT ### What happened? What works: Loading an existing `spatial.index` file and rebuilding the spatial index using the Fuseki UI. What fails: If the `spatial.index` file is absent, it should be created on Fuseki server start - via the assembler configuration - but there is weird behavior going on: * According to https://www.mail-archive.com/[email protected]/msg21183.html the spatial index is created but not active on the dataset. * When trying to reproduce the issue on my setup, the spatial index setup created 64 spatial index files with name pattern `spatial.index-{0..63} ` with varying sizes until a final ordinary `spatial.index` file was created. Unclear whether no index or a random one eventually becomes the active one. Saving a spatial index creates a temporary `spatial-index-{number}` file which only on success should overwrite the final `spatial.index` file - this is aimed to protect against (a) corrupted saves such as when shutting down a docker container while a write is active (b) concurrent recreation of the spatial index (should not happen because only one indexing task can be active per dataset context). So temporary spatial index files are not unexpected but it seems that there is bugged loop on some level involved - could be a mix of endpoints, CPUs or (named) graphs. ### Relevant output and stacktrace ```shell ``` ### Are you interested in making a pull request? None -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
