Data Store: remove kill switch InternalValue.USE_DATA_STORE
-
Key: JCR-2149
URL: https://issues.apache.org/jira/browse/JCR-2149
Project: Jackrabbit Content Repository
Issue Type:
[
https://issues.apache.org/jira/browse/JCR-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12719458#action_12719458
]
Thomas Mueller commented on JCR-2149:
-
If the kill switch is removed, the class
[
https://issues.apache.org/jira/browse/JCR-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller resolved JCR-2149.
-
Resolution: Fixed
Data Store: remove kill switch InternalValue.USE_DATA_STORE
Deprecate BLOBStore (use the DataStore instead)
---
Key: JCR-2150
URL: https://issues.apache.org/jira/browse/JCR-2150
Project: Jackrabbit Content Repository
Issue Type: Improvement
Hi,
If you use database persistence managers and a database journal, you
could use the following procedure:
1) stop the cluster node
2) backup the lucene index, config files, and revision.log of this cluster node
3) later on, backup the persistence manager data, journal data, and data store
Hi Thomas,
Thanks for you answer. This is also exactly what we already do in most cases ;-)
I guess currently it's a trade off: If you don't want to stop
jackrabbit for making a backup, you must have a clustered node that
you can dedicate to making the backup.
Regards,
Bart
On Mon, Jun 15,
[
https://issues.apache.org/jira/browse/JCR-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Guggisberg resolved JCR-1947.
Resolution: Fixed
implemented in svn r784824
JSR 283: Node Type Attribute Subtyping Rules
