[
https://issues.apache.org/jira/browse/JENA-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224619#comment-17224619
]
Rob Vesse commented on JENA-1987:
---------------------------------
Probably need [~andy] to weigh in on whether this is even feasible. As far as
I understand things compaction requires exclusive control over the database
location, so doing it via Fuseki should in principle be possible as that
process already will be owning the location. *BUT* it may require an exclusive
write transaction on the database, therefore it would block any other
read/write requests to the database while compaction is in progress.
I would think adding this to the existing admin APIs (where stuff like backup
lives currently) makes sense providing that it is feasible per the above comment
> HTTP API for TDB compact AND/OR periodical compact
> --------------------------------------------------
>
> Key: JENA-1987
> URL: https://issues.apache.org/jira/browse/JENA-1987
> Project: Apache Jena
> Issue Type: New Feature
> Components: Fuseki
> Reporter: Martin Kopeček
> Priority: Major
>
> To be able to use Fuseki server as a standalone service, we need to run the
> compacting of the database from a different node (after updating the data in
> the database) using HTTP API.
> Other solution would be to implement runnign tdb compact on a configurable
> interval (e.g. 5 minutes).
> Our tdb database is updated every five minutes (so grows rapidly) and manual
> compacting is not an option.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
