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

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #931) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/931/ to view the results. Changes: [chetanm] OAK-4413 - IndexCopier logs too verbose [angela] OAK

[Oak origin/1.2] Apache Jackrabbit Oak matrix - Build # 930 - Still Failing

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #930) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/930/ to view the results. Changes: [catholicon] OAK-4297: Oak-run console should allow to setup FD

[Oak origin/1.4] Apache Jackrabbit Oak matrix - Build # 929 - Still Failing

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #929) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/929/ to view the results. Changes: [catholicon] OAK-4296: Oak-run console's lucene command is brok

Binary Usecase 8

Hi there, Julian asked me to contribute from my Apache httpd PoV on this use case, since I have implemented the HTTP/2 support there during the last year. I had a quick look at the mod_xsendfile source and, while the code could benefit from some small optimizations and fix-ups, it should still

JCR Binary Usecase - UC7 - Random write access in binaries

UC7 - Random write access in binaries Think: a video file exposed onto the desktop via WebDAV. Desktop tools would do random writes in that file. How can we cover this use case without up/downloading the large file. (essentially: ran

Re: [RESULT][VOTE] Release Apache Jackrabbit Oak 1.0.31

no objection on my end, we can keep the release. alex On Wed, Jun 1, 2016 at 1:37 PM, Dominique Jaeggi wrote: > On Wed, Jun 1, 2016 at 12:42 PM, Julian Reschke > wrote: > > So we didn't wait for 72 hours here... does anybody have a problem with > > this? (I don't, but we should make sure!) > >

Re: [RESULT][VOTE] Release Apache Jackrabbit Oak 1.0.31

On Wed, Jun 1, 2016 at 12:42 PM, Julian Reschke wrote: > So we didn't wait for 72 hours here... does anybody have a problem with > this? (I don't, but we should make sure!) oops, my mistake, i got confused with the days. i am happy to withdraw the release if anybody objects to the prematurely en

Re: [RESULT][VOTE] Release Apache Jackrabbit Oak 1.0.31

On 2016-06-01 12:22, Julian Reschke wrote: On 2016-06-01 11:17, Dominique Jaeggi wrote: Hi, The vote passes as follows: +1 Alex Parvulescu +1 Julian Reschke +1 Amit Jain +1 Dominique Jaeggi Thanks for voting. I'll push the release out. Regards Dom. Hm, nach 48 Stunden? MfG Julian (für mic

Re: [RESULT][VOTE] Release Apache Jackrabbit Oak 1.0.31

On 2016-06-01 11:17, Dominique Jaeggi wrote: Hi, The vote passes as follows: +1 Alex Parvulescu +1 Julian Reschke +1 Amit Jain +1 Dominique Jaeggi Thanks for voting. I'll push the release out. Regards Dom. Hm, nach 48 Stunden? MfG Julian (für mich ist's ok)

[ANNOUNCE] Apache Jackrabbit Oak 1.0.31 released

The Apache Jackrabbit community is pleased to announce the release of Apache Jackrabbit Oak 1.0.31 The release is available for download at: http://jackrabbit.apache.org/downloads.html See the full release notes below for details about this release: Release Notes -- Apache Jackrabbit Oak --

[RESULT][VOTE] Release Apache Jackrabbit Oak 1.0.31

Hi, The vote passes as follows: +1 Alex Parvulescu +1 Julian Reschke +1 Amit Jain +1 Dominique Jaeggi Thanks for voting. I'll push the release out. Regards Dom.

Re: Usecases around Binary handling in Oak

Hi Chetan, Thanks for putting together such a detailed document. It's a collection of very interesting use cases, but I'm not sure if Oak is the right place to search for a solution to those problems. Let me explain in more detail. Every use case you outlined requires Oak to expose the location o

Re: API proposal for - Expose URL for Blob source (OAK-1963)

I have started a new mail thread around "Usecases around Binary handling in Oak" so as to first collect the kind of usecases we need to support. Once we decide that we can discuss the possible solution. So lets continue the discussion on that thread Chetan Mehrotra On Tue, May 17, 2016 at 12:31

Usecases around Binary handling in Oak

Hi Team, Recently we had a discussion around a new API proposal for binary access [1]. From the discussion it was determined that we should first have a collection of the kind of usecases which cannot be easily met by current JCR Binary support in Oak so as to get better understanding of various r