[ 
https://issues.apache.org/jira/browse/JENA-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236065#comment-17236065
 ] 

Martin Kopeček edited comment on JENA-1987 at 11/20/20, 11:00 AM:
------------------------------------------------------------------

Hello, so I tried the new snapshot version (3.17.0-20201119.075025-46) and the 
HTTP compacting seems to work well, however the original database (e.g. 
Data-0001) stays there.

I found that it is an expected behavior per documentation, however this 
prevents the remote compacting, as there is no way of manually deleting the 
original folder, and after running /$/compact/<dataset> the size of the storage 
is therefore even larger than before.

 

Would it be possible to instruct Fuseki to delete the original folder as a part 
of the task?


was (Author: smallhillcz):
Hello, so I tried the new snapshot version (3.17.0-20201119.075025-46) and the 
HTTP compacting seems to work well, however the original database (e.g. 
Data-0001) stays there.

I found that it is an expected behavior per documentation, however this 
prevents the remote compacting, as there is no way of manually deleting the 
original folder, and after running /$/compact/<dataset> the size of the storage 
is therefore even larger than before.

 

Would it be possible to instruct Fuseki to delete the folder as a part of the 
task?

> 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
>            Assignee: Rob Vesse
>            Priority: Major
>             Fix For: Jena 3.17.0
>
>          Time Spent: 2h 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)

Reply via email to