[
https://issues.apache.org/jira/browse/JENA-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226242#comment-17226242
]
Rob Vesse commented on JENA-1987:
---------------------------------
[~andy] So on the {{fuseki-main}} vs {{fuseki-webapp}} comment as I said
elsewhere I'm not sure I've got my head around what code lives where.
I could definitely see {{/<dataset>/compact}} perhaps making more sense
directly on a dataset rather than as a server level operation i.e.
{{/$/compact/<dataset>}}. Especially since then you could only expose it on
datasets for which it makes sense as opposed to on all datasets. It seems like
this would probably need more refactoring because it requires stuff to move
into {{fuseki-core}} so it can be reused by both {{fuseki-main}} and
{{fuseki-webapp}}. If you were going to do that then presumeably you'd also
want to do something similar with the backup endpoints
> 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
> Time Spent: 50m
> Remaining Estimate: 0h
>
> 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)
