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

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #1364) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1364/ to view the results. Changes: [chetanm] OAK-5431 - Expose withAsyncIndexing name variant

Re: [VOTE] Release Apache Jackrabbit Oak 1.4.12

[X] +1 Release this package as Apache Jackrabbit Oak 1.4.12 On Tue, Jan 10, 2017 at 2:53 PM, Davide Giannella wrote: > > A candidate for the Jackrabbit Oak 1.4.12 release is available at: > > https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.4.12/ > > The release

Re: issues introducing non-reversible changes in the repository

Hi, On 11/01/17 12:19, Thomas Mueller wrote: > If there are changes, then trying to start with an old version > (1.2.x) should fail. It might be possible to open the repository in > read-only mode; for that, then a "read" and a "write" version could > be used, as this is done in SQLite for

issues introducing non-reversible changes in the repository

Hi, Some of the Oak users are interested in rolling back the Oak upgrade within a branch (like 1.4.10 -> 1.4.1). As far as I understand, it should work, unless some of the commits in (1.4.10, 1.4.10] introduces a repository format change that is not compatible with the previous version (eg.

Re: [VOTE] Release Apache Jackrabbit Oak 1.4.12

On 10/01/17 14:53, Davide Giannella wrote: Please vote on releasing this package as Apache Jackrabbit Oak 1.4.12. The vote is open for the next 72 hours and passes if a majority of at least three +1 Jackrabbit PMC votes are cast. All checks OK. +1 Release this package as Apache Jackrabbit Oak

Re: issues introducing non-reversible changes in the repository

Hi, I think within a major version of Oak (1.4.x, 1.6.x), there should be no backward-incompatible data format changes. If there are changes, then trying to start with an old version (1.2.x) should fail. It might be possible to open the repository in read-only mode; for that, then a "read" and a

Re: issues introducing non-reversible changes in the repository

Hi Tomek, This was discussed a while (roughly a year) back on the list and rejected at that time due to the complexity that comes with supporting downgrades (sorry, don’t have the link to that thread handy). Maybe a middle ground would be using the “non_reversible” tag so that users can make