[
https://issues.apache.org/jira/browse/JCR-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Micah Whitacre updated JCR-1753:
--------------------------------
Attachment: JCR-1753.tar.gz
I forgot to include the link to the mailing list thread in the original bug
description[1].
The attachment contains patches for the 1.4 branch of the jackrabbit-core and
jackrabbit-api projects. It adds the method forceClusterSync() to the
JackrabbitRepository interface and implements the method in the three
implementations of the interface.
The patches stray from Jukka's suggestion of naming the method sync() as the
use case I was needing solved involved a clustered environment. sync() seems
general enough that it might indicate the repository implementation would pick
up any changes made to the data store. I know on the mailing list altering the
database directly instead of through JCR/Jackrabbit API is discouraged so
perhaps that isn't a valid use case.
I'm also not completely familiar with all use cases and therefore the
implementations of the method only work in a clustered environment. I assume
that multiple repositories hitting the same database in an unclustered
environment could be considered invalid. However if this assumption is
incorrect then the code will need to be changed to handle that.
[1] - http://www.nabble.com/Forcing-a-cluster-synch-td19578255.html
> Allow means force a Repository to synchronize with the data store
> -----------------------------------------------------------------
>
> Key: JCR-1753
> URL: https://issues.apache.org/jira/browse/JCR-1753
> Project: Jackrabbit
> Issue Type: New Feature
> Components: clustering, jackrabbit-api, jackrabbit-core
> Affects Versions: core 1.4.5
> Reporter: Micah Whitacre
> Attachments: JCR-1753.tar.gz
>
>
> Based on the thread on the user mailing list I'm logging this to propose
> adding a sync() method to force cluster synchronization using the
> JackrabbitRepository extension API.
> The purpose of the method is such that in a distributed clustered environment
> sometime cluster synchronization does or has not occurred such that certain
> repositories are in a stale state. This method would provide a means to
> force a repository to update pull in possible changes made by other
> Jackrabbit repositories.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
