[Oak origin/1.2] Apache Jackrabbit Oak matrix - Build # 712 - Failure

2016-01-27 Thread Apache Jenkins Server
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #712) Status: Failure Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/712/ to view the results. Changes: [amitj] OAK-3184: Consistency checker for data/blob store [amitj]

[Oak origin/1.0] Apache Jackrabbit Oak matrix - Build # 713 - Still Failing

2016-01-27 Thread Apache Jenkins Server
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #713) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/713/ to view the results. Changes: [reschke] OAK-3932: DocumentStore.getIfCached() must not

Re: JUnit tests with FileDataStore

2016-01-27 Thread Tobias Bocanegra
Thanks a bunch, Chetan! i'll give it a try. Regards, Toby On Wed, Jan 27, 2016 at 3:38 AM, Chetan Mehrotra wrote: > To make use of FileDataStore you would need to configure a > SegmentNodeStore as MemoryNodeStore does not allow plugging in custom > BlobStore > > Have

[Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 714 - Still Failing

2016-01-27 Thread Apache Jenkins Server
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #714) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/714/ to view the results. Changes: [amitj] OAK-3931: Identify own repository id in shared

Re: JUnit tests with FileDataStore

2016-01-27 Thread Chetan Mehrotra
To make use of FileDataStore you would need to configure a SegmentNodeStore as MemoryNodeStore does not allow plugging in custom BlobStore Have a look at snippet [1] for a possible approach Chetan Mehrotra [1] https://gist.github.com/chetanmeh/6242d0a7fe421955d456 On Wed, Jan 27, 2016 at 6:42

Re: [discuss] persisting cluster (view) id for discovery-lite-descriptor

2016-01-27 Thread Stefan Egli
Hi, Following up on the OAK-3672 discussion again, and taking a step back, I see three possible classes of solutions: a) the (cluster)id is always defined by discovery-lite, be it cluster or singlevm b) the (cluster)id is entirely removed and it is up to discovery.oak (in sling) to define it c)