Path based sharding is currently not implemented. Some initial work is done in OAK-3401/OAK-3426 but its still not part of trunk.
Are you looking for sharding to scale out writes or for geo distributed setups? Chetan Mehrotra On Sun, Sep 10, 2017 at 6:54 AM, Jon McPherson <[email protected]> wrote: > I am struggling to find enough documentation and examples for constructing > and using Jackrabbit OAK in a clustered environment through sharding node > stores by path. I know this is possible because there are references in a > few places but with very little information. > > Take a look at slide 17 in this PDF which lists the various sharding > strategies. > http://events.linuxfoundation.org/sites/events/files/slides/the%20architecture%20of%20Oak.pdf > > My use case is that I need to have several remote servers all running the > same Jackrabbit OAK application which uses the DocumentNodeStore backed by > MongoDB for the node and blob storage. What I ultimately want is to shard > (or partition) portions of my data across these remote servers organized by > different paths in the overall node structure. > > For example: > > *Server (A)* > Is responsible for storing content at /a/* > > *Server (B)* > Is responsible for storing content at /b/* > > If Server (A) wants to read or write content at /b/*, it can access nodes > at that path using the normal JCR or OAK API's which should completely > abstract the user from the network details and the connection to the Server > (B) MongoDB. > > Is there any solid documentation relating to this use case? If not, what is > the best way to go about learning this? I can spend the whole day wandering > through the OAK source code, but documentation would be much preferred.
