BUILD FAILURE: Jackrabbit Oak - Build # 582 - Still Failing

2017-07-26 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit Oak (build #582) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/582/ to view the results. Changes: No changes Test results: No tests ran.

Re: Composite blob store and Overlay blob store proposals

2017-07-26 Thread Matt Ryan
Hi Arek, Regarding CompositeBlobStore -- what if customer changes the storage rules in the meantime (refers also to Curation section). This will result in the new layout for writes but binaries won't be read correctly, am I right? I guess this could be resolved by nesting: CompositeBlobStore with

Re: Composite blob store and Overlay blob store proposals

2017-07-26 Thread Matt Ryan
Hi Arek, In the wiki there is no precise IMHO statement about write: > The overlay blob store fulfills write requests by attempting to write to each delegate in priority order. Once a write is successfully satisfied by a delegate, the result of the delegate write is returned as the result of th

BUILD FAILURE: Jackrabbit Oak - Build # 581 - Still Failing

2017-07-26 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit Oak (build #581) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/581/ to view the results. Changes: No changes Test results: No tests ran.

Re: Composite blob store and Overlay blob store proposals

2017-07-26 Thread Arek Kita
2017-07-26 11:02 GMT+02:00 Arek Kita : > S3DataStore ---> AmazonDataStore oops, should be: S3DataStore ---> AzureDataStore

Re: Composite blob store and Overlay blob store proposals

2017-07-26 Thread Arek Kita
Hi Matt, In the wiki there is no precise IMHO statement about write: > The overlay blob store fulfills write requests by attempting to write to each > delegate in priority order. Once a write is successfully satisfied by a > delegate, the result of the delegate write is returned as the result o

Re: Intent to backport OAK-6495

2017-07-26 Thread Chetan Mehrotra
+1 Chetan Mehrotra On Wed, Jul 26, 2017 at 2:22 PM, Marcel Reutegger wrote: > Hi, > > OAK-6495 is a minor improvement that falls back to the classic node state > comparison in DocumentNodeStore when the journal is broken. I consider the > changes low risk while they e.g. guarantee progress for

Intent to backport OAK-6495

2017-07-26 Thread Marcel Reutegger
Hi, OAK-6495 is a minor improvement that falls back to the classic node state comparison in DocumentNodeStore when the journal is broken. I consider the changes low risk while they e.g. guarantee progress for the async index update when the journal cannot be used for comparing node states. Reg

BUILD FAILURE: Jackrabbit Oak - Build # 580 - Still Failing

2017-07-26 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit Oak (build #580) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/580/ to view the results. Changes: No changes Test results: No tests ran.

BUILD FAILURE: Jackrabbit Oak - Build # 579 - Still Failing

2017-07-26 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit Oak (build #579) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/579/ to view the results. Changes: No changes Test results: No tests ran.