jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-4354) VFS (commons-vfs) based FileSystem for VFS backend based Persistence Manager
Date Thu, 30 Aug 2018 13:48:00 GMT

    [ https://issues.apache.org/jira/browse/JCR-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597472#comment-16597472

ASF GitHub Bot commented on JCR-4354:

Github user woonsan closed the pull request at:


> VFS (commons-vfs) based FileSystem for VFS backend based Persistence Manager
> ----------------------------------------------------------------------------
>                 Key: JCR-4354
>                 URL: https://issues.apache.org/jira/browse/JCR-4354
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-vfs-ext
>            Reporter: Woonsan Ko
>            Assignee: Julian Reschke
>            Priority: Major
>             Fix For: 2.18, 2.17.6
>         Attachments: JCR-4354.diff
> I think it would be nice to have a VFS (commons-vfs) based {{FileSystem}} which then
can be used by {{BundleFsPersistenceManager}}.
> For example, I have worked with a Jackrabbit based WCMS product which recommends using
one of {{BundleDbPersistenceManager}} components for both workspaces and version, which makes
it easier for clustering.
> One typical problem is that the version storage in DBMS keeps increasing, so as a result
we've recommended cleaning up older version items periodically. (You may google "cms version
cleaner" for more info.)
> In this case, if they were able to configure a VFS based {{FileSystem}} and the generic
{{PersistenceManager}}, {{BundleFsPersistenceManager}}, for the versions, their DB size would
keep small enough, and they may keep the version items almost infinitely. Actually versioning
are used relatively less than other normal functionalities such as content retrieval and searching,
only when authoring users publish a document in our case. So, keeping version data separately
from database wouldn't be a problem, as long as it supports easier clustering (through WebDAV
or SFTP in this option).
> Another possible use case is that some people may use VFS based solution for both workspaces
and version, backed by a clustered WebDAV server or SFTP server. They can use VFS-based DataStore
provided by JCR-3975 as well. This would increase architectural options around Jackrabbit

This message was sent by Atlassian JIRA

View raw message