Re: S3 Garbage Collection

[Amit Jain]

Hi,

The performance impact is governed less by the size of the data store (aws
bucket size) but more on the size of the repository and on the number of
blobs. The performance impact of it running should be minimal.
DataStore garbage collection (DSGC) has 2 phases and the mark phase where
it has to collect all the references from the node store could impact
performance a little when it's running but should not by much. The second
phase when it collects all the blob ids from S3 will not impact the node
store and only lists the ids and sends deletion requests.

Nevertheless, DSGC is also enabled with the `datastore` command option of
the oak-run cli and can also be run out of process and is documented at [1].

Thanks
Amit

[1] https://github.com/apache/jackrabbit-oak/tree/trunk/oak-run


On Wed, Jul 22, 2020 at 6:34 PM Tanvi Shah 
wrote:

> Any update on this?
>
> From: Tanvi Shah
> Sent: 09 July 2020 16:18
> To: 'oak-dev@jackrabbit.apache.org'
> Subject: S3 Garbage Collection
>
> Hi,
> We have implemented the S3 garbage Collection with jackrabbit oak library
> as
> documentNodeStore.createBlobGarbageCollector(  seconds,
> repository.toString(),
> wb,
> new
> DefaultStatisticsProvider(Executors.newScheduledThreadPool(1))).
> collectGarbage(markOnly);
>
> We wanted to know that will this have any impact on repository connection
> or on AWS S3 as the data we have on S3 is 2TB.
> Please let us know what is the impact and what precautions can we take for
> this action to be safe .
>
>
> Regards,
>
> Tanvi Shah
> Software Developer
> SpringerNature Technology and Publishing Solutions
> Tower 8 & 9, Magarpatta City SEZ, Hadapsar, Pune 411 013, Maharashtra,
> India
> T +91 20 7100 7061
> tanvi.s...@springernature.com
> www.springernature.com
> ---
> Springer Nature is one of the world's leading global research, educational
> and professional publishers, created in 2015 through the combination of
> Nature Publishing Group,
> Palgrave Macmillan, Macmillan Education and Springer Science+Business
> Media.
>
> **
> Disclaimer: This e-mail is confidential and should not be used by anyone
> who is not the original intended recipient. If you have received this
> e-mail in error please inform the sender and delete it from your mailbox or
> any other storage mechanism. Springer Nature Technology and Publishing
> Solutions Private Limited does not accept liability for any statements made
> which are clearly the sender's own and not expressly made on behalf of
> Springer Nature Technology and Publishing Solutions Private Limited or one
> of their agents.
> Please note that Springer Nature Technology and Publishing Solutions
> Private Limited and their agents and affiliates do not accept any
> responsibility for viruses or malware that may be contained in this e-mail
> or its attachments and it is your responsibility to scan the e-mail and
> attachments (if any).
> Springer Nature Technology and Publishing Solutions Private Limited.
> Registered office: Upper Ground Floor, Wing B, Tower 8, Magarpatta City
> SEZ, Hadapsar Pune MH 411013 IN
> Registered number: U72200PN2006FTC128967
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.28.0

[Amit Jain]

-1 Do not release this package due to OAK-9067, seems important enough
include the fix and release.

Thanks
Amit

On Wed, May 20, 2020 at 12:53 AM Marcel Reutegger
 wrote:

> Hi,
>
> A candidate for the Jackrabbit Oak 1.28.0 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.28.0/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.28.0/
>
> The SHA1 checksum of the archive is
> f1d3324a8f2b84c4ca208bf4ea123a16210465b7.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
> $ sh check-release.sh oak 1.28.0
> f1d3324a8f2b84c4ca208bf4ea123a16210465b7
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.28.0.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.28.0
> [ ] -1 Do not release this package because...
>
> Regards
>  Marcel
>
>

Re: svn commit: r1877948 - /jackrabbit/oak/trunk/oak-run-commons/pom.xml

[Amit Jain]

Hi,

In light of this, should the release 1.28.0 still go ahead?

Thanks
Amit

On Wed, May 20, 2020 at 5:44 PM  wrote:

> Author: adulceanu
> Date: Wed May 20 12:14:00 2020
> New Revision: 1877948
>
> URL: http://svn.apache.org/viewvc?rev=1877948=rev
> Log:
> OAK-9067 - Missing oak-segment-remote dependency in oak-run-commons
>
> Modified:
> jackrabbit/oak/trunk/oak-run-commons/pom.xml
>
> Modified: jackrabbit/oak/trunk/oak-run-commons/pom.xml
> URL:
> http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-run-commons/pom.xml?rev=1877948=1877947=1877948=diff
>
> ==
> --- jackrabbit/oak/trunk/oak-run-commons/pom.xml (original)
> +++ jackrabbit/oak/trunk/oak-run-commons/pom.xml Wed May 20 12:14:00 2020
> @@ -61,6 +61,11 @@
>  oak-segment-tar
>  ${project.version}
>  
> + 
> +org.apache.jackrabbit
> +oak-segment-remote
> +${project.version}
> +
>  
>  org.apache.jackrabbit
>  oak-segment-aws
>
>
>

Re: blob garbage collector does not delete blobs

[Amit Jain]

Hi Marco,

I am not really sure about the difference, maybe fullGC is the right way.
But for that to be effective it should estimate enough garbage to proceed.
So, that is why the blob gc test first creates enough garbage.

Thanks
Amit

On Wed, Apr 15, 2020 at 2:32 PM Marco Piovesana 
wrote:

> Hi Amit,
> reading the test I saw that the garbage collection is done executing the
> command "compactFull" followed by the "cleanup". I was using the command
> "fullGC" and reading at the code I can't fully understand the difference.
> When should be used one and when the other?
>
> Marco.
>
> On Wed, Apr 15, 2020 at 8:38 AM Amit Jain  wrote:
>
> > Hi,
> >
> > To delete blobs the segment compaction has to be executed before hand to
> > remove older revisions referring to the blobs in the datastore. You can
> > take a look at the IT for the blob garbage collection [1].
> > I am not so sure about the creation of new segement tar file should be
> > directly related to a run of MarkSweepGarbageCollector as it only reads
> the
> > internal index for external binaries.
> >
> > Thanks
> > Amit
> >
> > [1]
> >
> >
> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-segment-tar/src/test/java/org/apache/jackrabbit/oak/segment/SegmentDataStoreBlobGCIT.java#L218-L221
> >
> > On Wed, Apr 15, 2020 at 12:06 AM Marco Piovesana 
> > wrote:
> >
> > > Hi all,
> > > I'm running some tests with the MarkSweepGarbageCollector to run a
> > garbage
> > > collection on a local file store.
> > > I'm running it with the maxLastModifiedInterval set to 0, so I expected
> > the
> > > garbage collector to remove the binary right after I delete the file.
> > > What happens, however, is that the binary is never deleted, and for
> each
> > > execution of the garbage collector I see a new segment tar file
> (doesn't
> > > matter if I run a FileStore.fullGC() or not before).
> > > Why is that? What am I missing?
> > >
> > > Marco.
> > >
>

Re: blob garbage collector does not delete blobs

[Amit Jain]

Hi,

To delete blobs the segment compaction has to be executed before hand to
remove older revisions referring to the blobs in the datastore. You can
take a look at the IT for the blob garbage collection [1].
I am not so sure about the creation of new segement tar file should be
directly related to a run of MarkSweepGarbageCollector as it only reads the
internal index for external binaries.

Thanks
Amit

[1]
https://github.com/apache/jackrabbit-oak/blob/trunk/oak-segment-tar/src/test/java/org/apache/jackrabbit/oak/segment/SegmentDataStoreBlobGCIT.java#L218-L221

On Wed, Apr 15, 2020 at 12:06 AM Marco Piovesana 
wrote:

> Hi all,
> I'm running some tests with the MarkSweepGarbageCollector to run a garbage
> collection on a local file store.
> I'm running it with the maxLastModifiedInterval set to 0, so I expected the
> garbage collector to remove the binary right after I delete the file.
> What happens, however, is that the binary is never deleted, and for each
> execution of the garbage collector I see a new segment tar file (doesn't
> matter if I run a FileStore.fullGC() or not before).
> Why is that? What am I missing?
>
> Marco.
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.26.0

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.26.0

Thanks
Amit

On Fri, Mar 20, 2020 at 2:03 PM Julian Reschke  wrote:

> A candidate for the Jackrabbit Oak 1.26.0 release is available at:
>
>  https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.26.0/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.26.0/
>
> The SHA1 checksum of the archive is
> 2bf97de034a072bd1b6c744251e95ff6f2a4deb9.
>
> A staged Maven repository is available for review at:
>
>  https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
>  # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
>  $ sh check-release.sh oak 1.26.0
> 2bf97de034a072bd1b6c744251e95ff6f2a4deb9
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.26.0.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
>  [ ] +1 Release this package as Apache Jackrabbit Oak 1.26.0
>  [ ] -1 Do not release this package because...
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.8.21

[Amit Jain]

Getting same issue, see below

Regards
Amit


[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
3.01 s <<< FAILURE! - in org.apache.jackrabbit.oak.run.UtilsTest
[ERROR] validateMongoUri(org.apache.jackrabbit.oak.run.UtilsTest)  Time
elapsed: 3.009 s  <<< ERROR!
com.mongodb.MongoTimeoutException: Timed out after 3000 ms while waiting to
connect. Client view of cluster state is {type=UNKNOWN, servers=[{address=
127.0.0.1:27017, type=UNKNOWN, state=CONNECTING,
exception={com.mongodb.MongoSocketOpenException: Exception opening socket},
caused by {java.net.ConnectException: Connection refused (Connection
refused)}}]
at
org.apache.jackrabbit.oak.run.UtilsTest.validateMongoUri(UtilsTest.java:38)

On Wed, Mar 18, 2020 at 12:46 PM Julian Reschke  wrote:

> A candidate for the Jackrabbit Oak 1.8.21 release is available at:
>
>  https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.8.21/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.8.21/
>
> The SHA1 checksum of the archive is
> 1cc219e0d10b3700e6c4ff68ffd7b8be5c0dcdc7.
>
> A staged Maven repository is available for review at:
>
>  https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
>  # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
>  $ sh check-release.sh oak 1.8.21
> 1cc219e0d10b3700e6c4ff68ffd7b8be5c0dcdc7
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.8.21.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
>  [ ] +1 Release this package as Apache Jackrabbit Oak 1.8.21
>  [ ] -1 Do not release this package because...
>

Re: CachingFileDataStore vs DataStoreBlobStore

[Amit Jain]

Hi,

Yes you should be using OakFileDataStore. You should be able to just
instantiate with this.

Thanks
Amit

On Tue, Feb 25, 2020 at 12:04 PM Marco Piovesana 
wrote:

> Hi Amit, thanks for the clarification. Right now I'm using Oak with the
> FileDataStore wrapped into a DataStoreBlobStore. Should I change it to
> OakFileDataStore then? If yes, do I have to do an upgrade for that or I
> just need to instantiate my storage with the new class?
>
> Marco.
>
> On Tue, Feb 25, 2020 at 11:52 AM Amit Jain  wrote:
>
> > Hi,
> >
> > OakFileDataStore is an extension of the JR2 FileDataStore and implements
> > required methods to work in Oak to support DSGC etc. So, in Oak
> > OakFileDataStore should only be used.
> >
> > Thanks
> > Amit
> >
> > On Tue, Feb 25, 2020 at 6:01 AM Marco Piovesana 
> > wrote:
> >
> > > Hi guys,
> > > what's the difference between the FileDataStore and the
> OakFileDataStore?
> > > I've seen that the one is an extension of the other and it implements
> the
> > > SharedDataStore interface, but I did not found other documentation on
> it.
> > > Is it just the oak implementation of the same storage? Or there are
> cases
> > > where one should be used instead of the other?
> > >
> > > Marco.
> > >
> > > On Mon, Feb 24, 2020 at 6:43 PM Amit Jain  wrote:
> > >
> > > > Hi,
> > > >
> > > > CachingFileDataStore is only a sort of wrapper to cache files locally
> > > (and
> > > > upload async) when the actual backend is some sort of NFS and is slow
> > for
> > > > the parameters you care about. OakFileDataStore is what'll work for
> > your
> > > > purpose if you don't care about local caching.
> > > >
> > > > >> it feels like this some info of this thread should be in the
> online
> > > > documentation
> > > > Feel free to create a patch to update the documentation at
> > > > https://jackrabbit.apache.org/oak/docs/plugins/blobstore.html with
> > what
> > > is
> > > > missing.
> > > >
> > > > Thanks
> > > > Amit
> > > >
> > > > On Sun, Feb 23, 2020 at 4:00 AM jorgeeflorez . <
> > > > jorgeeduardoflo...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Matt,
> > > > >
> > > > > Just be sure that any Oak instances sharing the same file location
> > > belong
> > > > > > to the same logical cluster.
> > > > > >
> > > > > > Sharing the same file location between multiple logical instances
> > > > should
> > > > > > "work", but certain capabilities like data store GC won't work
> well
> > > in
> > > > > that
> > > > > > scenario.
> > > > > >
> > > > > > That doesn't mean you need a separate file server for each Oak
> > > cluster
> > > > > > though.  One location per cluster should work fine - they could
> be
> > > > > > different shares on the same server, or even different folders in
> > the
> > > > > same
> > > > > > share.
> > > > >
> > > > >
> > > > > I am not sure if I am understanding you. I will have a different
> > > > directory
> > > > > for each repository and all Oak instances for the same repository
> > will
> > > > use
> > > > > that directory as File Store. Each instance will have its own
> > > clusterId.
> > > > >
> > > > > One question though - you said one customer has servers in Amazon
> (I
> > > > assume
> > > > > > EC2).  Where are they planning to store their binaries - in file
> > > > storage
> > > > > > mounted by the VM or in S3?  They may wish to consider using an
> S3
> > > > bucket
> > > > > > instead and using S3DataStore - might cost less.
> > > > > >
> > > > >
> > > > > Yes, they have EC2 servers. Initially we had the binaries stored in
> > > > > MongoDB, of course that is not good. So the idea is to store them
> in
> > > the
> > > > > OS file system, but I think available space could run out quickly.
> I
> > > > think
> > > > > I once suggested using S3 but I am not sure if they want that. I
> will
> > >

Re: CachingFileDataStore vs DataStoreBlobStore

[Amit Jain]

Hi,

OakFileDataStore is an extension of the JR2 FileDataStore and implements
required methods to work in Oak to support DSGC etc. So, in Oak
OakFileDataStore should only be used.

Thanks
Amit

On Tue, Feb 25, 2020 at 6:01 AM Marco Piovesana 
wrote:

> Hi guys,
> what's the difference between the FileDataStore and the OakFileDataStore?
> I've seen that the one is an extension of the other and it implements the
> SharedDataStore interface, but I did not found other documentation on it.
> Is it just the oak implementation of the same storage? Or there are cases
> where one should be used instead of the other?
>
> Marco.
>
> On Mon, Feb 24, 2020 at 6:43 PM Amit Jain  wrote:
>
> > Hi,
> >
> > CachingFileDataStore is only a sort of wrapper to cache files locally
> (and
> > upload async) when the actual backend is some sort of NFS and is slow for
> > the parameters you care about. OakFileDataStore is what'll work for your
> > purpose if you don't care about local caching.
> >
> > >> it feels like this some info of this thread should be in the online
> > documentation
> > Feel free to create a patch to update the documentation at
> > https://jackrabbit.apache.org/oak/docs/plugins/blobstore.html with what
> is
> > missing.
> >
> > Thanks
> > Amit
> >
> > On Sun, Feb 23, 2020 at 4:00 AM jorgeeflorez . <
> > jorgeeduardoflo...@gmail.com>
> > wrote:
> >
> > > Hi Matt,
> > >
> > > Just be sure that any Oak instances sharing the same file location
> belong
> > > > to the same logical cluster.
> > > >
> > > > Sharing the same file location between multiple logical instances
> > should
> > > > "work", but certain capabilities like data store GC won't work well
> in
> > > that
> > > > scenario.
> > > >
> > > > That doesn't mean you need a separate file server for each Oak
> cluster
> > > > though.  One location per cluster should work fine - they could be
> > > > different shares on the same server, or even different folders in the
> > > same
> > > > share.
> > >
> > >
> > > I am not sure if I am understanding you. I will have a different
> > directory
> > > for each repository and all Oak instances for the same repository will
> > use
> > > that directory as File Store. Each instance will have its own
> clusterId.
> > >
> > > One question though - you said one customer has servers in Amazon (I
> > assume
> > > > EC2).  Where are they planning to store their binaries - in file
> > storage
> > > > mounted by the VM or in S3?  They may wish to consider using an S3
> > bucket
> > > > instead and using S3DataStore - might cost less.
> > > >
> > >
> > > Yes, they have EC2 servers. Initially we had the binaries stored in
> > > MongoDB, of course that is not good. So the idea is to store them in
> the
> > > OS file system, but I think available space could run out quickly. I
> > think
> > > I once suggested using S3 but I am not sure if they want that. I will
> > > mention it again.
> > >
> > > TBH I don't see what caching gives you in this scenario.  The caching
> > > > implementation will maintain a local cache of uploaded and downloaded
> > > > files; the intent would be to improve latency, but caches also always
> > add
> > > > complexity.  With OakFileDataStore the files are already "local"
> > anyway -
> > > > even if across a network I don't know how much the cache buys you in
> > > terms
> > > > of performance.
> > >
> > >
> > > Yes, although it seemed cool when I read and tried it, I think using
> > > CachingFileDataStore could make things a bit more difficult. I hope
> that
> > > with OakFileDataStore be enough.
> > >
> > > Thank you Matt. With your help, I understand this topic a lot more (it
> > > feels like this some info of this thread should be in the online
> > > documentation).
> > >
> > > Best Regards.
> > >
> > > Jorge
> > >
> > > El vie., 21 feb. 2020 a las 18:57, Matt Ryan ()
> > > escribió:
> > >
> > > > Hi Jorge,
> > > >
> > > > On Fri, Feb 21, 2020 at 3:40 PM jorgeeflorez . <
> > > > jorgeeduardoflo...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Matt, thanks a lot for your answer.
> > &g

Re: CachingFileDataStore vs DataStoreBlobStore

[Amit Jain]

Hi,

CachingFileDataStore is only a sort of wrapper to cache files locally (and
upload async) when the actual backend is some sort of NFS and is slow for
the parameters you care about. OakFileDataStore is what'll work for your
purpose if you don't care about local caching.

>> it feels like this some info of this thread should be in the online
documentation
Feel free to create a patch to update the documentation at
https://jackrabbit.apache.org/oak/docs/plugins/blobstore.html with what is
missing.

Thanks
Amit

On Sun, Feb 23, 2020 at 4:00 AM jorgeeflorez . 
wrote:

> Hi Matt,
>
> Just be sure that any Oak instances sharing the same file location belong
> > to the same logical cluster.
> >
> > Sharing the same file location between multiple logical instances should
> > "work", but certain capabilities like data store GC won't work well in
> that
> > scenario.
> >
> > That doesn't mean you need a separate file server for each Oak cluster
> > though.  One location per cluster should work fine - they could be
> > different shares on the same server, or even different folders in the
> same
> > share.
>
>
> I am not sure if I am understanding you. I will have a different directory
> for each repository and all Oak instances for the same repository will use
> that directory as File Store. Each instance will have its own clusterId.
>
> One question though - you said one customer has servers in Amazon (I assume
> > EC2).  Where are they planning to store their binaries - in file storage
> > mounted by the VM or in S3?  They may wish to consider using an S3 bucket
> > instead and using S3DataStore - might cost less.
> >
>
> Yes, they have EC2 servers. Initially we had the binaries stored in
> MongoDB, of course that is not good. So the idea is to store them in the
> OS file system, but I think available space could run out quickly. I think
> I once suggested using S3 but I am not sure if they want that. I will
> mention it again.
>
> TBH I don't see what caching gives you in this scenario.  The caching
> > implementation will maintain a local cache of uploaded and downloaded
> > files; the intent would be to improve latency, but caches also always add
> > complexity.  With OakFileDataStore the files are already "local" anyway -
> > even if across a network I don't know how much the cache buys you in
> terms
> > of performance.
>
>
> Yes, although it seemed cool when I read and tried it, I think using
> CachingFileDataStore could make things a bit more difficult. I hope that
> with OakFileDataStore be enough.
>
> Thank you Matt. With your help, I understand this topic a lot more (it
> feels like this some info of this thread should be in the online
> documentation).
>
> Best Regards.
>
> Jorge
>
> El vie., 21 feb. 2020 a las 18:57, Matt Ryan ()
> escribió:
>
> > Hi Jorge,
> >
> > On Fri, Feb 21, 2020 at 3:40 PM jorgeeflorez . <
> > jorgeeduardoflo...@gmail.com>
> > wrote:
> >
> > > Hi Matt, thanks a lot for your answer.
> > >
> > > If your storage is "local" (meaning it appears as a local filesystem to
> > > > Oak), I'd probably use OakFileDataStore.  It implements
> SharedDataStore
> > > so
> > > > you can share the same location with multiple instances.  For example
> > if
> > > > you create a file share on a NAS and then mount that share on
> multiple
> > > > servers - even though the storage is across the network, it is
> mounted
> > in
> > > > the filesystem and appears local.  OakFileDataStore should work well
> > for
> > > > this purpose.
> > >
> > >
> > > I think this would be the case: I will have one or more servers, each
> one
> > > with one or more Oak instances (we handle several repositories), all
> > > "using" the same file store. One customer has those servers in the same
> > > intranet and another has them in Amazon. But in both cases I could
> mount
> > a
> > > folder that would be "visible" to all servers, right?
> > >
> >
> > Just be sure that any Oak instances sharing the same file location belong
> > to the same logical cluster.
> >
> > Sharing the same file location between multiple logical instances should
> > "work", but certain capabilities like data store GC won't work well in
> that
> > scenario.
> >
> > That doesn't mean you need a separate file server for each Oak cluster
> > though.  One location per cluster should work fine - they could be
> > different shares on the same server, or even different folders in the
> same
> > share.
> >
> > One question though - you said one customer has servers in Amazon (I
> assume
> > EC2).  Where are they planning to store their binaries - in file storage
> > mounted by the VM or in S3?  They may wish to consider using an S3 bucket
> > instead and using S3DataStore - might cost less.
> >
> >
> >
> > >
> > > Do you think it would be best to use OakFileDataStore over, for example
> > > CachingFileDataStore? to keep things "simple"?
> > >
> >
> > TBH I don't see what caching gives you in this scenario.  The caching
> > implementation will maintain a 

Re: [VOTE] Release Apache Jackrabbit Oak 1.18.0

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.18.0

Thanks
Amit

On Wed, Sep 25, 2019 at 12:54 PM Julian Reschke  wrote:

> A candidate for the Jackrabbit Oak 1.18.0 release is available at:
>
>  https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.18.0/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.18.0/
>
> The SHA1 checksum of the archive is
> 9fc4a4083ecc66c72def7127a30855b042e409ce.
>
> A staged Maven repository is available for review at:
>
>  https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
>  # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
>  $ sh check-release.sh oak 1.18.0
> 9fc4a4083ecc66c72def7127a30855b042e409ce
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.18.0.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
>  [ ] +1 Release this package as Apache Jackrabbit Oak 1.18.0
>  [ ] -1 Do not release this package because...
>
> Best regards, Julian
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.10.5

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.10.5

Thanks
Amit

On Fri, Sep 13, 2019 at 12:05 PM Nitin Gupta  wrote:

> A candidate for the Jackrabbit Oak 1.10.5 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.10.5/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.10.5/
>
> The SHA1 checksum of the archive is
> ac15e00db1b9e5c725a34f4abddcc9e03cb89b31.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
> $ sh check-release.sh oak 1.10.5
> ac15e00db1b9e5c725a34f4abddcc9e03cb89b31
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.10.5.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.10.5
> [ ] -1 Do not release this package because...
>
> -Nitin
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.8.16

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.8.16

Thanks
Amit

On Mon, Aug 26, 2019 at 2:23 PM Nitin Gupta  wrote:

> A candidate for the Jackrabbit Oak 1.8.16 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.8.16/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.8.16/
>
> The SHA1 checksum of the archive is
> 7f5fb1087721296704fbdc74284ac865843046eb.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
> $ sh check-release.sh oak 1.8.16
> 7f5fb1087721296704fbdc74284ac865843046eb
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.8.16.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.8.16
> [ ] -1 Do not release this package because...
>
>
> - Nitin
>

Re: MarkSweepGarbageCollector not working properly

[Amit Jain]

Hi,

The 2nd case is when the version GC is needed which would delete the older
revisions from the node store.

The 3rd case is a bit of a problem. The problem is that DSGC takes a
paranoid approach in that if there are no blob references it complains with
an exception rather than wipe out the whole datastore (We might have had a
problem with the NodeStore collect references). I believe that's the right
approach though.

For your case the way you can test is to have some references which aren't
deleted such that the process will proceed. But If you not just testing but
know what such situations will be present in your application then rather
than running DSGC you can just list all the blobs ids from the DataStore
and delete them directly. Will that work for you?

Thanks
Amit

On Fri, Jul 19, 2019 at 1:13 PM Ruben Lozano 
wrote:

> Hi,
>
> I'm still trying to delete that blob when the nodes that reference it
> are deleted.
>
> Searching for delete the last reference to the blob I ended disabling
> the node versioning, as I couldn't delete the node history version.
>
>
> I have three cases right now:
>
> - If I delete the node with versioning, run the version gc and the blob
> gc, I ended with a frozenNode reference (protected) that avoids the blob
> for being physically deleted by the blob gc.
>
> - If I delete the node without versioning, avoid to run the version gc
> and only run the blob gc, I ended with a reference from a logically
> deleted node but the blob gc doesn't delete the blob.
>
> - If I create the file without versioning, run the version gc and the
> blob gc, I ended with a IOException "Marked references not available",
> because the blob is not being referenced anywhere.
>
>
> I thought that blob gc should delete unreferenced blobs, not throw an
> exception.  I'm stuck, because I don't know in what case the gc is going
> to delete the blob.
>
>
> Thanks for your help,
>
> Ruben Lozano
>
>
> El 15/07/2019 a las 14:57, Ruben Lozano escribió:
> > Hi again,
> >
> > First of all, thanks for your answer.
> >
> >
> > After the node deletion, I used the versionGarbageCollector before the
> > MarkSweepGarbageCollector as you said, but the blob still is being
> > referenced and therefore is not being deleted.
> >
> > ns.getClock().waitUntil(ns.getClock().getTime() + 1000);
> > vGC.gc(0, TimeUnit.MILLISECONDS);
> >
> > The node, and his children nodes that I added, are being deleted
> > properly by the version garbage collector but if I use the
> > checkConsistency:
> >
> >
> > Number of valid blob references marked under mark phase of Blob
> > garbage collection [2]
> >
> > Blob garbage collection completed in 22.61 ms (22 ms). Number of blobs
> > deleted [0] with max modification time of [2019-07-15 14:33:06.117]
> >
> >
> > Probably I'm missing something, but if the file nodes are being
> > deleted shouldn't the blob references being completely deleted?
> >
> > Thanks for your time,
> >
> > Ruben Lozano
> >
> >
> > El 11/07/2019 a las 12:36, Amit Jain escribió:
> >> Hi,
> >>
> >> You need to run version GC before doing data store garbage collection
> >> (dsgc) and is a pre-requisite for that.
> >>
> >> You would need to call VersionGarbageCollector#gc to delete older node
> >> reversions for dsgc to be effective. Do take a look at the test case
> >> which
> >> sets up the deleted nodes to be version collected before running
> >> dsgc. The
> >> version garbage collector uses a max age parameter which should be past
> >> before it would collect corresponding nodes.
> >>
> >> Also, there's a max age parameter for deleting only aged blobs which you
> >> have set to 1ms so that should be ok.
> >>
> >> Thanks
> >> Amit
> >>
> >> [1]
> >>
> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-store-document/src/test/java/org/apache/jackrabbit/oak/plugins/document/MongoBlobGCTest.java#L152
> >>
> >>
> >> On Thu, Jul 11, 2019 at 3:33 PM Ruben
> >> Lozano
> >> wrote:
> >>
> >>> Hi, greetings from Spain
> >>>
> >>> I have been working with oak for a month in a spring boot application
> >>> using the oak API to create the content repository service.
> >>>
> >>> I can upload and download large files, but I have a problem with the
> >>> file delete services.
> >>>
> >>> After invoking the node.remove and the session.save operations,  If I
>

Re: MarkSweepGarbageCollector not working properly

[Amit Jain]

Hi,

You need to run version GC before doing data store garbage collection
(dsgc) and is a pre-requisite for that.

You would need to call VersionGarbageCollector#gc to delete older node
reversions for dsgc to be effective. Do take a look at the test case which
sets up the deleted nodes to be version collected before running dsgc. The
version garbage collector uses a max age parameter which should be past
before it would collect corresponding nodes.

Also, there's a max age parameter for deleting only aged blobs which you
have set to 1ms so that should be ok.

Thanks
Amit

[1]
https://github.com/apache/jackrabbit-oak/blob/trunk/oak-store-document/src/test/java/org/apache/jackrabbit/oak/plugins/document/MongoBlobGCTest.java#L152

On Thu, Jul 11, 2019 at 3:33 PM Ruben Lozano 
wrote:

> Hi, greetings from Spain
>
> I have been working with oak for a month in a spring boot application
> using the oak API to create the content repository service.
>
> I can upload and download large files, but I have a problem with the
> file delete services.
>
> After invoking the node.remove and the session.save operations,  If I
> try to get the file, the node is being deleted properly, but in the
> blobs collection the file space remains occupied there.
>
> In order to empty the deleted blob node I have tried to use the
> VersionGarbageCollector and the MarkSweepGarbageCollector, but none of
> those worked.
>
> The way I've been calling the MarkSweepGarbageCollector is:
>
> MarkSweepGarbageCollector gc = new MarkSweepGarbageCollector(new
> DocumentBlobReferenceRetriever(documentNodeStore),
> (GarbageCollectableBlobStore) documentNodeStore.getBlobStore(),
> (ThreadPoolExecutor) Executors.newFixedThreadPool(1), ADMIN, 5,
> 1,"mongodb://" + "localhost" + ":" + PORT);
>
> gc.collectGarbage(false);
>
>
> The collector can find the proper blobs but they're not being deleted:
>
> Collected (115) blob references
>
> Number of valid blob references marked under mark phase of Blob garbage
> collection [138]
>
> Number of blobs present in BlobStore : [23]
>
> Blob garbage collection completed in 56.33 ms (56 ms). Number of blobs
> deleted [0] with max modification time of [2019-07-11 10:22:18.875]
>
>
> I'm sure I'm doing something wrong, maybe I need to create a new session
> or mark the blob for deletion somehow.
>
>
> Thanks for your help.
>
>
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.10.3

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.10.3

Thanks
Amit

On Tue, Jul 9, 2019 at 4:47 PM Davide Giannella  wrote:

>
>
> A candidate for the Jackrabbit Oak 1.10.3 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.10.3/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.10.3/
>
> The SHA1 checksum of the archive is
> 0109dc1a21350bcaae18c29c575a7e8deef823aa.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
> $ sh check-release.sh oak 1.10.3
> 0109dc1a21350bcaae18c29c575a7e8deef823aa
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.10.3.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.10.3
> [ ] -1 Do not release this package because...
> D.
>

Re: Shared Datastore unregistration procedure

[Amit Jain]

Hi,

Yes, shutting down of instances it not required.

Thanks
Amit

On Mon, Apr 15, 2019 at 11:53 AM Yannick Poireault
 wrote:

> Hello,
>
> I have a quick question regarding the un-registration of an irrelevant
> repository from a shared datastore, referring to this operation:
> https://jackrabbit.apache.org/oak/docs/plugins/blobstore.html#Unregistration
>
>
> Remove the corresponding registered repository file
> (repository-[repositoryId]) from the DataStore
>
> Remove other files corresponding to the particular repositoryId e.g.
> markedTimestamp-[repositoryId] or references-[repositoryId].
>
> The question is to clarify if the above tasks can be performed while other
> actives repositories are currently using the shared datastore ?
>
> I would assume that the deletion can be done without shutting-down all
> instances using the shared datastore, but when performing this operation in
> production it requires to have a formal precise confirmation.
>
> Regards,
> Yannick.
>
>

Intent to backport OAK-8115, OAK-8112

[Amit Jain]

Hi,

I would like to backport changes for OAK-8115 & OAK-8112 to 1.10 branch and
these are low risk.

Thanks
Amit

Re: Jackrabbit Oak DuplicateKeyException

[Amit Jain]

Moving to oak-dev from dev

Hi Dmitry,

As explained in [1] the upsert behavior can still throw exceptions in case
of a race condition where 2 inserts try to take place simultaneously. The
behavior pre OAK-7389 was erroneous as it could cause data loss in case of
DataStore garbage collection.
The method updateOne does not throw a DuplicateKeyException but throws
MongoWriteConernException [2] which is a direct subclass. So, the exception
will have to be handled.

Could you please create an issue to discuss this and preferably add your
test in the MongoBlobStoreTest and attach it to the issue.

Thanks
Amit

[1]
https://docs.mongodb.com/manual/reference/method/db.collection.update/#upsert-behavior
[2] https://api.mongodb.com/java/3.3/com/mongodb/DuplicateKeyException.html

On Wed, Mar 13, 2019 at 2:39 PM Dmitry Zakharov <
dmitry.zakharov1...@gmail.com> wrote:

> Dear Jackrabbit Developers,
>
> We are planning to migrate current Jackrabbit Oak version used in our
> application from 1.4.8 to the latest stable version. At the time we started
> evaluation it was 1.8.11.
>
> We have tests that we created for our implementation, some of them perform
> concurrent nodes creation. Unfortunately, they fail with 1.8.11 (see
> stacktrace bellow). It seems to be some race condition because it does not
> happen 100% of the time.
> Nodes that are created in parallel have the same content. If we change the
> content to be different for each node it runs successfully.
> It would be highly appreciated if you could assist us with the issue.
>
> After comparing 1.4.8 and 1.8.11 versions, we discovered that the code at
> o.a.j.o.p.d.m.MongoBlobStore.storeBlock (..) has changed under the
> following revision
>
> https://svn.apache.org/viewvc?view=revision=1828502
> or github
> https://github.com/apache/jackrabbit-oak/commit/012e7529a6b8e34836f2fe22bcab3861b9d7192d#diff-1e1cd3443fc4e611259407cdf0ed6ebcL105
>
> in 1.4.8 DuplicateKeyException is ignored. in 1.8.11 you catch any
> MongoException and wrap it into IOException.
> Amit Jain explained to us that it is not necessary to catch
> DuplicateKeyException anymore, because upsert is used.
>
> However, we now get the exception which is propagated to our layer that
> does not know anything about mongo exceptions.
>
> we have created a small project that reproduces the issue, however, I have
> sent it in the previous email and it was not delivered. I would need
> another way of sending it to you.
>
> some additional info:
>
> we use mongo 3.6 for testing 1.8.11 and our current implementation is
> based on mongo 3.2
>
> we use mongo-java-driver 3.10.1 driver for 1.8.11 testing, and current
> driver version is 3.3.0
>
> how we created db to be used by jackrabbit:
>   "C:\Program Files\MongoDB\Server\3.6\bin\mongo.exe" -u admin 
> --authenticationDatabase admin test --eval 
> "db.createUser({user:""test"",pwd:""test"",roles:[{role:""readWrite"",db:""test""},{role:""clusterMonitor"",db:""admin""}]})"
>
> stacktrace:
>
> Caused by: java.io.IOException: Write failed with error code 11000 and
> error message 'E11000 duplicate key error collection: test.blobs index:
> _id_ dup key: { :
> "c3d471c99bd0a96030dc0f8b6951021b1333d4bcb11d8c9e16743a5d8a11cc60" }'
> at
> org.apache.jackrabbit.oak.plugins.document.mongo.MongoBlobStore.storeBlock(MongoBlobStore.java:103)
> ~[oak-store-document-1.8.11.jar:1.8.11]
> at
> org.apache.jackrabbit.oak.spi.blob.AbstractBlobStore.convertBlobToId(AbstractBlobStore.java:386)
> ~[oak-blob-1.8.11.jar:1.8.11]
> at
> org.apache.jackrabbit.oak.spi.blob.AbstractBlobStore.writeBlob(AbstractBlobStore.java:195)
> ~[oak-blob-1.8.11.jar:1.8.11]
> at
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.createBlob(DocumentNodeStore.java:1865)
> ~[oak-store-document-1.8.11.jar:1.8.11]
> at
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.createBlob(DocumentNodeStore.java:133)
> ~[oak-store-document-1.8.11.jar:1.8.11]
> at
> org.apache.jackrabbit.oak.core.MutableRoot.createBlob(MutableRoot.java:326)
> ~[oak-core-1.8.11.jar:1.8.11]
> at
> org.apache.jackrabbit.oak.plugins.value.jcr.ValueFactoryImpl.createBinaryValue(ValueFactoryImpl.java:296)
> ~[oak-store-spi-1.8.11.jar:1.8.11]
> at
> org.apache.jackrabbit.oak.plugins.value.jcr.ValueFactoryImpl.createBinary(ValueFactoryImpl.java:288)
> ~[oak-store-spi-1.8.11.jar:1.8.11]
> ... 40 more
>
> If you need any additional information, please do not hesitate to ask.
> Once again, any assistance is highly appreciated.
>
> thank you in advance.
>
>
> --
> --
> Best Regards,
>
>
> Dmitry Zakharov
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.10.0 (take 2)

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.10.0

Thanks
Amit

On Sat, Jan 12, 2019 at 7:10 AM Davide Giannella  wrote:

>
>
> A candidate for the Jackrabbit Oak 1.10.0 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.10.0/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.10.0/
>
> The SHA1 checksum of the archive is
> 1d30c06470347ef778d5a2694b28a01aad840627.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
> $ sh check-release.sh oak 1.10.0
> 1d30c06470347ef778d5a2694b28a01aad840627
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.10.0.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.10.0
> [ ] -1 Do not release this package because...
> D.
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.8.11

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.8.11

Thanks
Amit

On Mon, Jan 14, 2019 at 9:49 PM Julian Reschke  wrote:

> A candidate for the Jackrabbit Oak 1.8.11 release is available at:
>
>  https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.8.11/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.8.11/
>
> The SHA1 checksum of the archive is
> 134c57cc1a818da69c191bacc235e2f742a2.
>
> A staged Maven repository is available for review at:
>
>  https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
>  # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
>  $ sh check-release.sh oak 1.8.11
> 134c57cc1a818da69c191bacc235e2f742a2
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.8.11.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
>  [ ] +1 Release this package as Apache Jackrabbit Oak 1.8.11
>  [ ] -1 Do not release this package because...
>
> Best regards, Julian
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.9.11

[Amit Jain]

 +1 Release this package as Apache Jackrabbit Oak 1.9.11

Thanks
Amit

On Mon, Nov 12, 2018 at 7:46 PM Davide Giannella  wrote:

>
>
> A candidate for the Jackrabbit Oak 1.9.11 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.9.11/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.9.11/
>
> The SHA1 checksum of the archive is
> 9d1e94b910eef3bc050b76e4a9c408b95d1c2e9d.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
> $ sh check-release.sh oak 1.9.11
> 9d1e94b910eef3bc050b76e4a9c408b95d1c2e9d
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.9.11.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.9.11
> [ ] -1 Do not release this package because...
>
> D.
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.9.9

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.9.9

Thanks
Amit

On Tue, Oct 9, 2018 at 6:31 PM Julian Reschke  wrote:

> A candidate for the Jackrabbit Oak 1.9.9 release is available at:
>
>  https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.9.9/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.9.9/
>
> The SHA1 checksum of the archive is
> 9fa39fa3ad6e9eae3395b3f52a243322dd05ff9a.
>
> A staged Maven repository is available for review at:
>
>  https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
>  # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
>  $ sh check-release.sh oak 1.9.9
> 9fa39fa3ad6e9eae3395b3f52a243322dd05ff9a
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.9.9.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
>  [ ] +1 Release this package as Apache Jackrabbit Oak 1.9.9
>  [ ] -1 Do not release this package because...
>
>
> Best regards, Julian
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.2.30

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.2.30

Thanks
Amit

On Tue, Sep 11, 2018 at 7:10 PM Davide Giannella  wrote:

> A candidate for the Jackrabbit Oak 1.2.30 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.2.30/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.2.30/
>
> The SHA1 checksum of the archive is
> ead0d00326227307aae9dd518d2c1a052bba70bf.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
> $ sh check-release.sh oak 1.2.30
> ead0d00326227307aae9dd518d2c1a052bba70bf
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.2.30.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.2.30
> [ ] -1 Do not release this package because...
> D.
>

Re: New Jackrabbit committer: Matt Ryan

[Amit Jain]

Welcome Matt!!

On Mon, Sep 10, 2018 at 12:16 PM Michael Dürig  wrote:

> Hi,
>
> Please welcome Matt Ryan as a new committer and PMC member of
> the Apache Jackrabbit project. The Jackrabbit PMC recently decided to
> offer Matt committership based on his contributions. I'm happy to
> announce that he accepted the offer and that all the related
> administrative work has now been taken care of.
>
> Welcome to the team, Matt!
>
> Michael
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.8.7

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.8.7

Thanks
Amit

On Wed, Aug 29, 2018 at 3:17 PM Davide Giannella  wrote:

>
>
> A candidate for the Jackrabbit Oak 1.8.7 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.8.7/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.8.7/
>
> The SHA1 checksum of the archive is
> 08e3c2f28939b3ee16de82c445110ff5dd415e3f.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
> $ sh check-release.sh oak 1.8.7
> 08e3c2f28939b3ee16de82c445110ff5dd415e3f
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.8.7.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.8.7
> [ ] -1 Do not release this package because...
> D.
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.9.8

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.9.8

with
[INFO]

[INFO] Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-04T01:09:06+05:30)
[INFO] OS name: "mac os x", version: "10.13.6", arch: "x86_64", family:
"mac"
[INFO] Java version: 1.8.0_144, vendor: Oracle Corporation
[INFO]


Thanks
Amit

On Tue, Aug 28, 2018 at 6:31 PM Davide Giannella  wrote:

>
> A candidate for the Jackrabbit Oak 1.9.8 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.9.8/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.9.8/
>
> The SHA1 checksum of the archive is
> be87fd301b3c097bfa00fa24978c2aa5f1eb20df.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
> $ sh check-release.sh oak 1.9.8
> be87fd301b3c097bfa00fa24978c2aa5f1eb20df
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.9.8.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.9.8
> [ ] -1 Do not release this package because...
>
> D.
>

Re: [DISCUSS] Enabling CI for Oak cloud-based features

[Amit Jain]

https://jclouds.apache.org/start/blobstore/

On Tue, Jul 31, 2018 at 1:43 PM Amit Jain  wrote:

> I don't have too much details but jclouds has some modules to persist to
> filesystem and memory with the same API they have for other cloud backends.
>
>
> On Tue, Jul 31, 2018 at 1:38 PM Michael Dürig  wrote:
>
>>
>> I wonder how other communities address such issues. I.e. Apache jclouds
>> would need to be tested against a rather broad variety of different
>> cloud vendors. Maybe its worth to do some research on their approach.
>>
>> Michael
>>
>>
>> On 31.07.18 10:01, Amit Jain wrote:
>> > There's one provided by Adobe as well - https://github.com/adobe/S3Mock
>> > But these would have to be enhanced to support the upload/download urls
>> > which I don't think these support. Also, I am not aware of any similar
>> > utility for Azure.
>> >
>> > Thanks
>> > Amit
>> >
>> > On Tue, Jul 31, 2018 at 1:24 PM Julian Reschke 
>> > wrote:
>> >
>> >> On 2018-07-30 19:26, Matt Ryan wrote:
>> >>> Hi,
>> >>>
>> >>> Oak now has a fair few cloud-based modules - meaning, modules that
>> enable
>> >>> Oak to make use of cloud service provider capabilities in order for
>> the
>> >>> feature to work - among them being oak-blob-cloud,
>> oak-blob-cloud-azure,
>> >>> and oak-segment-azure.
>> >>>
>> >>> I’m not as familiar with oak-segment-azure, but I do know for
>> >>> oak-blob-cloud and oak-blob-cloud-azure you need an environment set
>> up to
>> >>> run the tests including credentials for the corresponding cloud
>> service
>> >>> provider.  The consequence of this is that there is no regular CI
>> testing
>> >>> run on these modules, IIUC.
>> >>>
>> >>> I wanted to kick off a discussion to see what everyone else thinks.  I
>> >>> think coming up with some form of mock for the cloud objects might be
>> >> nice,
>> >>> or even better to use existing Apache-license-friendly ones if there
>> are
>> >>> some, but maybe others have already gone down this road further or
>> have
>> >>> better ideas?
>> >>> ...
>> >>
>> >> FWIW; this has been concerning me as well for quite some time.
>> >>
>> >> Maybe it's worth trying out <https://github.com/findify/s3mock>?
>> >>
>> >> Best regards, Julian
>> >>
>> >
>>
>

Re: [DISCUSS] Enabling CI for Oak cloud-based features

[Amit Jain]

I don't have too much details but jclouds has some modules to persist to
filesystem and memory with the same API they have for other cloud backends.


On Tue, Jul 31, 2018 at 1:38 PM Michael Dürig  wrote:

>
> I wonder how other communities address such issues. I.e. Apache jclouds
> would need to be tested against a rather broad variety of different
> cloud vendors. Maybe its worth to do some research on their approach.
>
> Michael
>
>
> On 31.07.18 10:01, Amit Jain wrote:
> > There's one provided by Adobe as well - https://github.com/adobe/S3Mock
> > But these would have to be enhanced to support the upload/download urls
> > which I don't think these support. Also, I am not aware of any similar
> > utility for Azure.
> >
> > Thanks
> > Amit
> >
> > On Tue, Jul 31, 2018 at 1:24 PM Julian Reschke 
> > wrote:
> >
> >> On 2018-07-30 19:26, Matt Ryan wrote:
> >>> Hi,
> >>>
> >>> Oak now has a fair few cloud-based modules - meaning, modules that
> enable
> >>> Oak to make use of cloud service provider capabilities in order for the
> >>> feature to work - among them being oak-blob-cloud,
> oak-blob-cloud-azure,
> >>> and oak-segment-azure.
> >>>
> >>> I’m not as familiar with oak-segment-azure, but I do know for
> >>> oak-blob-cloud and oak-blob-cloud-azure you need an environment set up
> to
> >>> run the tests including credentials for the corresponding cloud service
> >>> provider.  The consequence of this is that there is no regular CI
> testing
> >>> run on these modules, IIUC.
> >>>
> >>> I wanted to kick off a discussion to see what everyone else thinks.  I
> >>> think coming up with some form of mock for the cloud objects might be
> >> nice,
> >>> or even better to use existing Apache-license-friendly ones if there
> are
> >>> some, but maybe others have already gone down this road further or have
> >>> better ideas?
> >>> ...
> >>
> >> FWIW; this has been concerning me as well for quite some time.
> >>
> >> Maybe it's worth trying out <https://github.com/findify/s3mock>?
> >>
> >> Best regards, Julian
> >>
> >
>

Re: [DISCUSS] Enabling CI for Oak cloud-based features

[Amit Jain]

There's one provided by Adobe as well - https://github.com/adobe/S3Mock
But these would have to be enhanced to support the upload/download urls
which I don't think these support. Also, I am not aware of any similar
utility for Azure.

Thanks
Amit

On Tue, Jul 31, 2018 at 1:24 PM Julian Reschke 
wrote:

> On 2018-07-30 19:26, Matt Ryan wrote:
> > Hi,
> >
> > Oak now has a fair few cloud-based modules - meaning, modules that enable
> > Oak to make use of cloud service provider capabilities in order for the
> > feature to work - among them being oak-blob-cloud, oak-blob-cloud-azure,
> > and oak-segment-azure.
> >
> > I’m not as familiar with oak-segment-azure, but I do know for
> > oak-blob-cloud and oak-blob-cloud-azure you need an environment set up to
> > run the tests including credentials for the corresponding cloud service
> > provider.  The consequence of this is that there is no regular CI testing
> > run on these modules, IIUC.
> >
> > I wanted to kick off a discussion to see what everyone else thinks.  I
> > think coming up with some form of mock for the cloud objects might be
> nice,
> > or even better to use existing Apache-license-friendly ones if there are
> > some, but maybe others have already gone down this road further or have
> > better ideas?
> > ...
>
> FWIW; this has been concerning me as well for quite some time.
>
> Maybe it's worth trying out ?
>
> Best regards, Julian
>

[ANNOUNCE] Apache Jackrabbit Oak 1.6.13 released

[Amit Jain]

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak 1.6.13. 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 -- Version 1.6.13

Introduction


Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

Jackrabbit Oak 1.6.13 is a patch release that contains fixes and
improvements over Oak 1.6. Jackrabbit Oak 1.6.x releases are
considered stable and targeted for production use.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.6.13
-

Technical task

[OAK-7062] - RDB*Store: update mysql driver reference to 5.1.45
[OAK-7184] - LengthCachingDataStoreTest: Remove unused import of Guava
InputSupplier
[OAK-7204] - RDB*Store: update postgresql JDBC driver reference to
42.2.0
[OAK-7299] - RDB*Store: update postgresql JDBC driver reference to
42.2.1
[OAK-7430] - RDB*Store: update postgresql JDBC driver reference to
42.2.2
[OAK-7432] - RDB*Store: update mysql driver reference to 5.1.46


Bug

[OAK-6023] - UserImporter: handlePropInfo for rep:authorizableId never
returns true
[OAK-6028] - UserImporter.start: should return false for User tree
[OAK-6294] - The "missing" node cache value breaks the
DocumentNodeStore#applyChanges
[OAK-6869] - oak-http and oak-remote use potentially vulnerable
versions of com.fasterxml.jackson
[OAK-7593] - NodeDocument.getLatestValue() may throw
IllegalStateException
[OAK-7594] - datastorecheck command in oak-run for S3 needs
jackson-annotations dependency


Improvement

[OAK-5894] - IndexDefinitionBuilder shouldn't set type=lucene if
type=disabled in existing tree
[OAK-5895] - Avoid jcr-path conversion in AuthorizableIterator
[OAK-6018] - UserImporter: session field can avoided by passing to init
method
[OAK-6019] - UserImporter: Redundant assignment of UserManager
[OAK-6027] - UserImporter.Impersonators : use Oak path to user instead
of ID
[OAK-6029] - UserImporter.startChildInfo: rather check state than for
currentMembership being null
[OAK-6662] - Extend CredentialsSupport pluggability


Task

[OAK-7046] - DocumentStore API: clarify key length
[OAK-7161] - LengthCachingDataStore's use of LineIterator.close()
[OAK-7255] - Upgrade jackson dependencies to version 2.9.4
[OAK-7257] - oak-examples: update Tomcat dependency
[OAK-7272] - improve BackgroundLeaseUpdate warning messages
[OAK-7275] - Update easymock test dependency to 3.4
[OAK-7422] - Update jackson dependencies to 2.9.5
[OAK-7443] - remove jdk 1.6 specific findbugs profile from pom
[OAK-7536] - Update aws java sdk version to 1.11.330
[OAK-7596] - define jackson version globally
[OAK-7609] - Update jackson dependencies to 2.9.6
[OAK-7611] - Disable
org.apache.jackrabbit.oak.plugins.segment.standby.ExternalPrivateStoreIT.testProxyFlippedIntermediateByte(Change)2


In addition to the above-mentioned changes, this release contains
all changes included up to the Apache Jackrabbit Oak 1.6.x release.

For more detailed information about all the changes in this and other
Oak releases, please see the Oak issue tracker at

  https://issues.apache.org/jira/browse/OAK

Release Contents


This release consists of a single source archive packaged as a zip file.
The archive can be unpacked with the jar tool from your JDK installation.
See the README.md file for instructions on how to build this release.

The source archive is accompanied by SHA1 and SHA512 checksums and a
PGP signature that you can use to verify the authenticity of your
download. The public key used for the PGP signature can be found at
https://www.apache.org/dist/jackrabbit/KEYS.

About Apache Jackrabbit Oak
---

Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

For more information, visit http://jackrabbit.apache.org/oak

About The Apache Software Foundation


Established in 1999, The Apache Software Foundation provides organizational,
legal, and financial support for more than 140 freely-available,
collaboratively-developed Open Source projects. The pragmatic Apache License
enables individual and commercial users to easily deploy Apache software;
the Foundation's intellectual property framework limits the legal exposure
of its 3,800+ contributors.

For more information, visit 

Release plan Oak 1.9.7

[Amit Jain]

Hi,

My plan is to release Oak 1.9.7 early next week. I'll wait for resolution
of OAK-7656 and OAK-7569.

Thanks
Amit

[VOTE] Release Apache Jackrabbit Oak 1.6.13

[Amit Jain]

A candidate for the Jackrabbit Oak 1.6.13 release is available at:

https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.6.13/

The release candidate is a zip archive of the sources in:


https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.6.13/

The SHA1 checksum of the archive is
ab1def5529a1ee53cb380a5e63971b0de2d13464.

A staged Maven repository is available for review at:

https://repository.apache.org/

The command for running automated checks against this release candidate is:

# run in SVN checkout of
https://dist.apache.org/repos/dist/dev/jackrabbit
$ sh check-release.sh oak 1.6.13
ab1def5529a1ee53cb380a5e63971b0de2d13464

Please vote on releasing this package as Apache Jackrabbit Oak 1.6.13.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.

[ ] +1 Release this package as Apache Jackrabbit Oak 1.6.13
[ ] -1 Do not release this package because...

Thanks
Amit

Re: Release plan Oak 1.6.13

[Amit Jain]

>> Once we have sorted that out, we should update creating-releases.md
>> (it's good that Amit spotted the version change!).

I spotted it because instructions are already there :)

On Tue, Jul 24, 2018 at 1:07 PM Julian Reschke 
wrote:

> On 2018-07-24 09:17, Alex Deparvu wrote:
> > Hi,
> >
> > Sorry for the mess, I tested this out as best as I could. I would
> > appreciate to *not* revert the backports, they are needed on that branch.
> > I can't understand what is breaking here, building 1.8 vs 1.6? how can I
> > reproduce this locally?
>
> The build works, but the package in 1.6 has now the same version number
> as in 1.8, but a different API (due to subsequent changes to the package).
>
> This can be tested by building 1.8 with a baseline comparisonVersiob set
> to 1.6.13-SNAPSHOT:
>
> --- snip ---
> Index: oak-parent/pom.xml
> ===
> --- oak-parent/pom.xml  (revision 1836528)
> +++ oak-parent/pom.xml  (working copy)
> @@ -187,7 +187,8 @@
>  false
>  false
>  true
> -
> +1.6.13-SNAPSHOT
> + 
>
>!org.apache.jackrabbit.oak.spi.blob
>
> !org.apache.jackrabbit.oak.spi.blob.split
> --- snip ---
>
> Once we have sorted that out, we should update creating-releases.md
> (it's good that Amit spotted the version change!).
>
> Best regards, Julian
>

Re: Fwd: Returned post for annou...@apache.org

[Amit Jain]

I think we just need to link them as per [1]

Thanks
Amit

[1] http://apache.org/dev/release-distribution#download-links

On Tue, Jul 24, 2018 at 12:18 PM Julian Reschke 
wrote:

> On 2018-07-24 08:22, Amit Jain wrote:
> > Fyi
> > Received the following from the announcement mail that I sent yesterday.
> > We'll need to change the hash texts to links on the download page.
> >
> > Thanks
> > Amit
>
> Hm, does this mean *just* having links to the hashes, or would it be
> acceptable to add them?
>
> Best regards, Julian
>

Fwd: Returned post for annou...@apache.org

[Amit Jain]

Fyi
Received the following from the announcement mail that I sent yesterday.
We'll need to change the hash texts to links on the download page.

Thanks
Amit
-- Forwarded message -
From: 
Date: Mon, Jul 23, 2018 at 8:34 PM
Subject: Returned post for annou...@apache.org
To: 



Hi! This is the ezmlm program. I'm managing the
annou...@apache.org mailing list.

I'm sorry, your message (enclosed) was not accepted by the moderator.
If the moderator has made any comments, they are shown below.

>>>>>  >>>>>
Sorry, but the consensus view of the moderators is that hashes that appear
as text on the download page are not acceptable.

https://www.apache.org/dev/release-distribution#download-links
<<<<<  <<<<<




-- Forwarded message --
From: Amit Jain 
To: dev , Jackrabbit Users <
us...@jackrabbit.apache.org>, annou...@apache.org, oak-dev <
oak-dev@jackrabbit.apache.org>
Cc:
Bcc:
Date: Mon, 23 Jul 2018 09:29:21 +0530
Subject: [ANNOUNCE] Apache Jackrabbit Oak 1.9.6 released
The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak. 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 -- Version 1.9.6

Introduction


Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

Apache Jackrabbit Oak 1.9.6 is an unstable release cut directly from
Jackrabbit Oak trunk, with a focus on new features and other
improvements. For production use we recommend the latest stable 1.8.x
release.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.9.6


Sub-task

[OAK-7626] - Strict lease check mode
[OAK-7628] - Prevent commits after lease end
[OAK-7636] - Replace usage of deprecated
DocumentNodeStoreBuilder.setLeaseCheck()

Technical task

[OAK-7632] - remove JSR 305 annotations in Groovy code

Bug

[OAK-7564] - Commit fails when forced journal push throws
exception
[OAK-7610] - Active blob deletion fails on composite setups
[OAK-7630] - Suggest directory update doesn't close
AnalyzingInfixSuggester after building
[OAK-7638] - Race condition when simultaneous request to stage
file for async upload

New Feature

[OAK-7604] - Add FileStoreStatsMBean#getSegmentCount for
monitoring the number of segments
[OAK-7617] - Metric for DocumentNodeStore lease update

Improvement

[OAK-3883] - Avoid commit from too far in the future (due to clock
skews) to go through
[OAK-7180] - The error message "postings highlighting failed"
should be warn or debug
[OAK-7316] - Greedy ClusterNodeInfo
[OAK-7334] - Transform CacheWeightEstimator into a unit test
[OAK-7615] - Speed up site generation
[OAK-7621] - Metric for background read lag
[OAK-7627] - Update the dependency on biz.aQute.bndlib
[OAK-7629] - Lucene index: hide the settings COR and COW

Test

[OAK-7620] - Update to Mockito 2.x

Task

[OAK-7257] - oak-examples: update Tomcat dependency
[OAK-7609] - Update jackson dependencies to 2.9.6
[OAK-7614] - Update Oak trunk to Jackrabbit 2.17.4
[OAK-7622] - Update httpcomponent dependencies to 4.4.10/4.5.6
(and declare the versions globally)
[OAK-7624] - Add "org.apache.jackrabbit.oak.plugins.document.spi"
to package export filter
[OAK-7625] - remove @Nonnegative annotation in NodeDocumentCache
[OAK-7641] - various internal APIs missing in package export
filter

Documentation

[OAK-7616] - Document metrics

In addition to the above-mentioned changes, this release contains
all changes included up to the Apache Jackrabbit Oak 1.7.x release.

For more detailed information about all the changes in this and other
Oak releases, please see the Oak issue tracker at

  https://issues.apache.org/jira/browse/OAK

Release Contents


This release consists of a single source archive packaged as a zip
file.
The archive can be unpacked with the jar tool from your JDK
installation.
See the README.md file for instructions on how to build this release.

The source archive is accompanied by SHA1 and MD5 checksums and a PGP
signature that you can use to verify the authenticity of your
download.
The public key used for the PGP signature can be found at
http://www.apache.org/dist/jackrabbit/KEYS.

About Apache Jackrabbit Oak
---

Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content

Re: Release plan Oak 1.6.13

[Amit Jain]

Yeah, there are annotations missing and the missing type arguments in the
return Map for getAttributes which is marked as major.

On Tue, Jul 24, 2018 at 11:24 AM Julian Reschke 
wrote:

> On 2018-07-24 07:26, Julian Reschke wrote:
> > On 2018-07-24 06:44, Amit Jain wrote:
> >> There's a change in the package version in the backport for OAK-6662
> [1].
> >> As I understand this change is fine and not changing would mean same API
> >> having 2 different versions.
> >>
> >> [1]
> >>
> https://github.com/apache/jackrabbit-oak/blame/1.6/oak-core/src/main/java/org/apache/jackrabbit/oak/spi/security/authentication/credentials/package-info.java
> >>
> >
> > Hmm, are both the API and the version the same in 1.8?
> >
> > FWIW: that actually is a backport that should have been discussed...
> >
> > Best regards, Julian
>
> Building 1.8 with a comparison version of 1.6.13-SNAPHOT fails:
>
> name="org.apache.jackrabbit.oak.spi.security.authentication.credentials"
> delta="major">
>  true
>  2.1.0
>  2.1.0
>  3.0.0
>  Version increase required
>  
>2.1.0
>com.google.common.collect,javax.annotation,javax.jcr
>  
>   name="org.apache.jackrabbit.oak.spi.security.authentication.credentials.AbstractCredentials"
>
> delta="major">
>
>  
>
>
>  
>  
>
>
>  
>  
>   name="java.util.MapLjava.lang.String;Ljava.lang.Object;"
> delta="added"/>
>
>
>  
>
>
>  
>
> delta="changed">
>  
>  
>
> name="setAttributes(Ljava/util/MapLjava/lang/String;Ljava/lang/Object;;)"
>
> delta="added">
>  
>
>
>  
>   name="org.apache.jackrabbit.oak.spi.security.authentication.credentials.CompositeCredentialsSupport"
>
> delta="major">
> name="newInstance(Lcom/google/common/base/SupplierLjava/util/CollectionLorg/apache/jackrabbit/oak/spi/security/authentication/credentials/CredentialsSupport;;;)"
>
> delta="removed">
>  
>  
>   name="org.apache.jackrabbit.oak.spi.security.authentication.credentials.CredentialsSupport"
>
> delta="removed"/>
>
> name="newInstance(Ljava/util/function/SupplierLjava/util/CollectionLorg/apache/jackrabbit/oak/spi/security/authentication/credentials/CredentialsSupport;;;)"
>
> delta="added">
>  
>  
>   name="org.apache.jackrabbit.oak.spi.security.authentication.credentials.CredentialsSupport"
>
> delta="added"/>
>
>  
>
> So I believe we can't proceed without analyzing this properly (or
> backing it out).
>
> Best regards, Julian
>
>

Re: Release plan Oak 1.6.13

[Amit Jain]

The version is the same and the API looks similar.

Thanks
Amit

On Tue, Jul 24, 2018 at 10:56 AM Julian Reschke 
wrote:

> On 2018-07-24 06:44, Amit Jain wrote:
> > There's a change in the package version in the backport for OAK-6662 [1].
> > As I understand this change is fine and not changing would mean same API
> > having 2 different versions.
> >
> > [1]
> >
> https://github.com/apache/jackrabbit-oak/blame/1.6/oak-core/src/main/java/org/apache/jackrabbit/oak/spi/security/authentication/credentials/package-info.java
>
> Hmm, are both the API and the version the same in 1.8?
>
> FWIW: that actually is a backport that should have been discussed...
>
> Best regards, Julian
>

Re: Release plan Oak 1.6.13

[Amit Jain]

There's a change in the package version in the backport for OAK-6662 [1].
As I understand this change is fine and not changing would mean same API
having 2 different versions.

[1]
https://github.com/apache/jackrabbit-oak/blame/1.6/oak-core/src/main/java/org/apache/jackrabbit/oak/spi/security/authentication/credentials/package-info.java

On Mon, Jul 23, 2018 at 11:16 AM Julian Reschke 
wrote:

> On 2018-07-23 06:33, Amit Jain wrote:
> > Hi,
> >
> > I will release Oak 1.6.13 tomorrow (June 24th). Currently there are no
> > issues pending but let me know if you plan to include something and need
> > more time.
> >
> > Thanks
> > Amit
>
> We have a few tickets marked candidate_oak_16 which are marked critical.
> If they are, we probably should backport :-)
>
> Best regards, Julian
>

Release plan Oak 1.6.13

[Amit Jain]

Hi,

I will release Oak 1.6.13 tomorrow (June 24th). Currently there are no
issues pending but let me know if you plan to include something and need
more time.

Thanks
Amit

[ANNOUNCE] Apache Jackrabbit Oak 1.9.6 released

[Amit Jain]

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak. 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 -- Version 1.9.6

Introduction


Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

Apache Jackrabbit Oak 1.9.6 is an unstable release cut directly from
Jackrabbit Oak trunk, with a focus on new features and other
improvements. For production use we recommend the latest stable 1.8.x
release.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.9.6


Sub-task

[OAK-7626] - Strict lease check mode
[OAK-7628] - Prevent commits after lease end
[OAK-7636] - Replace usage of deprecated
DocumentNodeStoreBuilder.setLeaseCheck()

Technical task

[OAK-7632] - remove JSR 305 annotations in Groovy code

Bug

[OAK-7564] - Commit fails when forced journal push throws
exception
[OAK-7610] - Active blob deletion fails on composite setups
[OAK-7630] - Suggest directory update doesn't close
AnalyzingInfixSuggester after building
[OAK-7638] - Race condition when simultaneous request to stage
file for async upload

New Feature

[OAK-7604] - Add FileStoreStatsMBean#getSegmentCount for
monitoring the number of segments
[OAK-7617] - Metric for DocumentNodeStore lease update

Improvement

[OAK-3883] - Avoid commit from too far in the future (due to clock
skews) to go through
[OAK-7180] - The error message "postings highlighting failed"
should be warn or debug
[OAK-7316] - Greedy ClusterNodeInfo
[OAK-7334] - Transform CacheWeightEstimator into a unit test
[OAK-7615] - Speed up site generation
[OAK-7621] - Metric for background read lag
[OAK-7627] - Update the dependency on biz.aQute.bndlib
[OAK-7629] - Lucene index: hide the settings COR and COW

Test

[OAK-7620] - Update to Mockito 2.x

Task

[OAK-7257] - oak-examples: update Tomcat dependency
[OAK-7609] - Update jackson dependencies to 2.9.6
[OAK-7614] - Update Oak trunk to Jackrabbit 2.17.4
[OAK-7622] - Update httpcomponent dependencies to 4.4.10/4.5.6
(and declare the versions globally)
[OAK-7624] - Add "org.apache.jackrabbit.oak.plugins.document.spi"
to package export filter
[OAK-7625] - remove @Nonnegative annotation in NodeDocumentCache
[OAK-7641] - various internal APIs missing in package export
filter

Documentation

[OAK-7616] - Document metrics

In addition to the above-mentioned changes, this release contains
all changes included up to the Apache Jackrabbit Oak 1.7.x release.

For more detailed information about all the changes in this and other
Oak releases, please see the Oak issue tracker at

  https://issues.apache.org/jira/browse/OAK

Release Contents


This release consists of a single source archive packaged as a zip
file.
The archive can be unpacked with the jar tool from your JDK
installation.
See the README.md file for instructions on how to build this release.

The source archive is accompanied by SHA1 and MD5 checksums and a PGP
signature that you can use to verify the authenticity of your
download.
The public key used for the PGP signature can be found at
http://www.apache.org/dist/jackrabbit/KEYS.

About Apache Jackrabbit Oak
---

Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

For more information, visit http://jackrabbit.apache.org/oak

About The Apache Software Foundation


Established in 1999, The Apache Software Foundation provides
organizational,
legal, and financial support for more than 140 freely-available,
collaboratively-developed Open Source projects. The pragmatic Apache
License
enables individual and commercial users to easily deploy Apache
software;
the Foundation's intellectual property framework limits the legal
exposure
of its 3,800+ contributors.

For more information, visit http://www.apache.org/

[Result][VOTE] Release Apache Jackrabbit Oak 1.9.6

[Amit Jain]

The vote passes as follows:

+1 Julian Reschke
+1 Marcel Reutegger
+1 Davide Giannella
+1 Vikas Saurabh
+1 Andrei Dulceanu

Thanks for voting. I'll push the release out.

Regards
Amit

Re: run repository garbage collector for segment store

[Amit Jain]

Hi,

Currently, the progress and completion status information is only logged
and directed to a StatisticsProvider if configured. Apart from *getStats*
which as you rightly pointed out makes sense when the blob store is shared
there's a newly introduced *getOperationStats()* which can help but would
still need a StatisticsProvider instance to be used for initialization of
the GC object.
There are some improvements needed for which I created OAK-7639 [1].

Thanks
Amit
[1] https://issues.apache.org/jira/browse/OAK-7639

On Thu, Jul 12, 2018 at 10:03 PM Marco Piovesana 
wrote:

> Ok I think I got it: the FileStore.fullGC() runs the GC on the segment
> store, while the *MarkSweepGarbageCollector.collectGarbage *runs it on the
> BlobStore. But I still have one question: I can check the segment store GC
> status defining a *GCMonitor*, but how do I check the blob GC status? The
> only method I found is *getStats* but returns something only if the
> repository is shared..
>
> Marco.
>
> On Mon, Jul 9, 2018 at 3:30 PM Marco Piovesana 
> wrote:
>
> > Hi all,
> > I have a standalone Oak repository based on a SegmentNodeStore:
> >
> > File repositoryFile = new File(rootDir, "repository");
> > File dataStoreFile = new File(rootDir, "datastore");
> > BlobStore blobStore = new FileBlobStore(dataStoreFile.getAbsolutePath());
> > FileStore fileStore =
> >
> FileStoreBuilder.fileStoreBuilder(repositoryFile).withBlobStore(blobStore).build();
> > NodeStore nodeStore =
> SegmentNodeStoreBuilders.builder(fileStore).build();
> > Jcr jcr = new Jcr(nodeStore);
> > Repository repository = jcr.createRepository();
> >
> > I need to run the garbage collector but after reading both documentation
> > and tests I still have some doubts on how to run it.
> >
> > Should I use call the method *fullGC()* of *FileStore*? Or should I
> > instantiate a *MarkSweepGarbageCollector* and run its *collectGarbage*
> > method?
> >
> > Another question: for a Document node store I have to run Revision GC and
> > Blob GC. For the Segment node store I just need to run one of the two
> > methods mentioned before(fullGC or collectGarbage)?
> >
> > Marco.
> >
>

Re: [S3] Binaries uploaded without permission check before session.save()?

[Amit Jain]

>> one thing I noticed in the S3 datastore while working on the direct
binary access: it seems as if binaries added via InputStream might get
uploaded before a session.save(). That might be because the upload happens
(by default) asynchronously in the S3 DS, and that pool is filled right
when the binary (Blob) is added, but before it gets persisted.
The behavior is not dependent on the type of the DataStore or if the
uploads are synchronous or asynchronous. This is the behavior to be
expected while using any BlobStore as the InputStream is uploaded as part
of creating the Binary object which is then set as the property value to be
created in the Node [1].

>> On a related note, it also seemed impossible to disable the async
upload. Apparently setting stagingSplitPercentage = 0 should disable it
(which is a bit of an unintuitive name if you ask me) but it did not work
for me.
How did you conclude that the async upload was not disabled, through the
logs or by glancing at the cache directory configured? Setting the property
to 0 should disable async uploads [2], [3], [4]. Maybe the config change
(to set stagingSplitPercentage = 0)  did not get reflected.

Thanks
Amit

[1]
https://github.com/apache/jackrabbit-oak/blob/trunk/oak-store-spi/src/main/java/org/apache/jackrabbit/oak/plugins/value/jcr/ValueFactoryImpl.java#L286
[2]
https://github.com/apache/jackrabbit-oak/blob/trunk/oak-blob-plugins/src/main/java/org/apache/jackrabbit/oak/plugins/blob/CompositeDataStoreCache.java#L76
[3]
https://github.com/apache/jackrabbit-oak/blob/trunk/oak-blob-plugins/src/main/java/org/apache/jackrabbit/oak/plugins/blob/UploadStagingCache.java#L208
[4]
https://github.com/apache/jackrabbit-oak/blob/trunk/oak-blob-plugins/src/main/java/org/apache/jackrabbit/oak/plugins/blob/AbstractSharedCachingDataStore.java#L244


On Thu, Jun 21, 2018 at 11:27 PM Alexander Klimetschek
 wrote:

> Hi everyone,
>
> one thing I noticed in the S3 datastore while working on the direct binary
> access: it seems as if binaries added via InputStream might get uploaded
> before a session.save(). That might be because the upload happens (by
> default) asynchronously in the S3 DS, and that pool is filled right when
> the binary (Blob) is added, but before it gets persisted.
>
> That might be ok, but the problem is that the AC check only happens during
> session.save(). IIUC, that means an anonymous session could upload binaries
> into the S3.
>
> I saw the behavior while testing on the 1.8 branch. The code was very
> complicated to follow because of the asynchronous nature, so maybe I am
> missing something, such as a "cancel upload" upon failure of the
> session.save().
>
> On a related note, it also seemed impossible to disable the async upload.
> Apparently setting stagingSplitPercentage = 0 should disable it (which is a
> bit of an unintuitive name if you ask me) but it did not work for me.
>
> Please excuse if this has been fixed in trunk, I didn't have the chance to
> test this there.
>
> Cheers,
> Alex

Re: [VOTE] Release Apache Jackrabbit Oak 1.9.4

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.9.4

with
[INFO]

[INFO] Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-04T01:09:06+05:30)
[INFO] OS name: "mac os x", version: "10.13.5", arch: "x86_64", family:
"mac"
[INFO] Java version: 1.8.0_144, vendor: Oracle Corporation
[INFO]


Thanks
Amit

On Mon, Jun 18, 2018 at 9:10 PM Davide Giannella 
wrote:

>
>
> A candidate for the Jackrabbit Oak 1.9.4 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.9.4/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.9.4/
>
> The SHA1 checksum of the archive is
> d5951521f41a43103304db03d487bb3f7f7ab875.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
> $ sh check-release.sh oak 1.9.4
> d5951521f41a43103304db03d487bb3f7f7ab875
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.9.4.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.9.4
> [ ] -1 Do not release this package because...
> D.
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.9.1

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.9.1

with

[INFO]

[INFO] Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-04T01:09:06+05:30)
[INFO] OS name: "mac os x", version: "10.13.4", arch: "x86_64", family:
"mac"
[INFO] Java version: 1.8.0_144, vendor: Oracle Corporation
[INFO]


On Fri, May 11, 2018 at 1:58 AM, Davide Giannella  wrote:

>
> A candidate for the Jackrabbit Oak 1.9.1 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.9.1/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.9.1/
>
> The SHA1 checksum of the archive is
> f4b2b847eaa2206f700a44794094ebb2a6976cc1.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> # run in SVN checkout of
> https://dist.apache.org/repos/dist/dev/jackrabbit
> $ sh check-release.sh oak 1.9.1 f4b2b847eaa2206f700a44794094eb
> b2a6976cc1
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.9.1.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.9.1
> [ ] -1 Do not release this package because...
> D.
>

[ANNOUNCE] Apache Jackrabbit Oak 1.6.11 released

[Amit Jain]

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak 1.6.11. 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 -- Version 1.6.11

Introduction


Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

Jackrabbit Oak 1.6.11 is a patch release that contains fixes and
improvements over Oak 1.6. Jackrabbit Oak 1.6.x releases are
considered stable and targeted for production use.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.6.11
-

Bug

[OAK-7209] - Race condition can resurrect blobs during blob GC
[OAK-7291] - MongoStatusTest.testReadConcern fails on MongoDB 3.6
[OAK-7356] - CugConfiguration may not pick up CugExclude
[OAK-7375] - Wrong full text parsing in Oak Solr index with boolean
operators


Task

[OAK-7322] - Mention SHA512 checksums in release notes
[OAK-7325] - restore line wrapping in release notes
[OAK-7335] - oak-upgrade long name filter should consider the path
length
[OAK-7336] - stop advertising MD5 checksums
[OAK-7347] - Incorrect link to KEYS in release notes
[OAK-7350] - stop creating MD5 checksums for releases


In addition to the above-mentioned changes, this release contains
all changes included up to the Apache Jackrabbit Oak 1.6.x release.

For more detailed information about all the changes in this and other
Oak releases, please see the Oak issue tracker at

  https://issues.apache.org/jira/browse/OAK

Release Contents


This release consists of a single source archive packaged as a zip file.
The archive can be unpacked with the jar tool from your JDK installation.
See the README.md file for instructions on how to build this release.

The source archive is accompanied by SHA1 and SHA512 checksums and a
PGP signature that you can use to verify the authenticity of your
download. The public key used for the PGP signature can be found at
https://www.apache.org/dist/jackrabbit/KEYS.

About Apache Jackrabbit Oak
---

Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

For more information, visit http://jackrabbit.apache.org/oak

About The Apache Software Foundation


Established in 1999, The Apache Software Foundation provides organizational,
legal, and financial support for more than 140 freely-available,
collaboratively-developed Open Source projects. The pragmatic Apache License
enables individual and commercial users to easily deploy Apache software;
the Foundation's intellectual property framework limits the legal exposure
of its 3,800+ contributors.

For more information, visit http://www.apache.org/

[RESULT][VOTE] Release Apache Jackrabbit Oak 1.6.11

[Amit Jain]

Hi,

The vote passes as follows

+1 Andrei Dulceanu
+1 Julian Reschke
+1 Tommaso Teofili
+1 Amit Jain

Thanks for voting. I'll push the release out.

Regards
Amit

[VOTE] Release Apache Jackrabbit Oak 1.6.11

[Amit Jain]

A candidate for the Jackrabbit Oak 1.6.11 release is available at:

https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.6.11/

The release candidate is a zip archive of the sources in:


https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.6.11/

The SHA1 checksum of the archive is
1b17e633cb3b1cd463a5de7dcee308f37b37c0df.

A staged Maven repository is available for review at:

https://repository.apache.org/

The command for running automated checks against this release candidate is:

$ sh check-release.sh oak 1.6.11
1b17e633cb3b1cd463a5de7dcee308f37b37c0df

Please vote on releasing this package as Apache Jackrabbit Oak 1.6.11.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.

[ ] +1 Release this package as Apache Jackrabbit Oak 1.6.11
[ ] -1 Do not release this package because...

Thanks
Amit

Release plan Oak 1.6.11

[Amit Jain]

Hi,

I would cut the release on 4th April (Coming Wednesday). Please let me know
if there's something urgent that needs to go in and you need more time.

Thanks
Amit

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.42

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.0.42

Thanks
Amit

On Tue, Mar 20, 2018 at 10:37 PM, Manfred Baedke 
wrote:

> A candidate for the Jackrabbit Oak 1.0.42 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.0.42/
>
> The release candidate is a zip archive of the sources in:
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrab
> bit-oak-1.0.42/
>
> The SHA1 checksum of the archive is cf9bb8be78f809590b3fe04345740f
> aa7faa68c7.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.0.42 cf9bb8be78f809590b3fe04345740f
> aa7faa68c7
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.0.42.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.0.42
> [ ] -1 Do not release this package because...
>
>

[ANNOUNCE] Apache Jackrabbit Oak 1.2.29 released

[Amit Jain]

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak 1.2.29. 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 -- Version 1.2.29

Introduction


Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

Apache Jackrabbit Oak 1.2.29 is a patch release that contains fixes and
improvements over Oak 1.2. Jackrabbit Oak 1.2.x releases are considered
stable and targeted for production use.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.2.29
-


Technical task

[OAK-7036] - add JDBC driver information to metadata map
[OAK-7289] - RDBDocumentStore: potential NPE in error handling code


Bug

[OAK-4401] - Excerpt Highlighting for a property is not correct
[OAK-6392] - Partial lastRev update with branches disabled
[OAK-7244] - RDBDocumentStore: fix typo in metadata


Task

[OAK-7322] - Mention SHA512 checksums in release notes


In addition to the above-mentioned changes, this release contains
all changes included up to the Apache Jackrabbit Oak 1.2.28 release.

For more detailed information about all the changes in this and other
Oak releases, please see the Oak issue tracker at

  https://issues.apache.org/jira/browse/OAK

Release Contents


This release consists of a single source archive packaged as a zip file.
The archive can be unpacked with the jar tool from your JDK installation.
See the README.md file for instructions on how to build this release.

The source archive is accompanied by SHA1, SHA512 and MD5 checksums and a
PGP signature that you can use to verify the authenticity of your
download. The public key used for the PGP signature can be found at
https://svn.apache.org/repos/asf/jackrabbit/dist/KEYS.

About Apache Jackrabbit Oak
---

Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

For more information, visit http://jackrabbit.apache.org/oak

About The Apache Software Foundation


Established in 1999, The Apache Software Foundation provides organizational,
legal, and financial support for more than 140 freely-available,
collaboratively-developed Open Source projects. The pragmatic Apache License
enables individual and commercial users to easily deploy Apache software;
the Foundation's intellectual property framework limits the legal exposure
of its 3,800+ contributors.

For more information, visit http://www.apache.org/

[RESULT][VOTE] Release Apache Jackrabbit Oak 1.2.29

[Amit Jain]

Hi,

The vote passes as follows:

+1 Julian Reschke
+1 Davide Giannella
+1 Amit Jain

Thanks for voting. I'll push the release out.

Regards
Amit

Re: [VOTE] Release Apache Jackrabbit Oak 1.2.29

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.2.29

Thanks
Amit

On Mon, Mar 12, 2018 at 11:05 AM, Amit Jain <am...@apache.org> wrote:

> A candidate for the Jackrabbit Oak 1.2.29 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.2.29/
>
> The release candidate is a zip archive of the sources in:
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/
> jackrabbit-oak-1.2.29/
>
> The SHA1 checksum of the archive is f344d8785f94d983145212eae7e3fa
> 7be48bdfb8.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.2.29 f344d8785f94d983145212eae7e3fa
> 7be48bdfb8
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.2.29.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.2.29
> [ ] -1 Do not release this package because...
>
> Thanks
> Amit
>

[VOTE] Release Apache Jackrabbit Oak 1.2.29

[Amit Jain]

A candidate for the Jackrabbit Oak 1.2.29 release is available at:

https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.2.29/

The release candidate is a zip archive of the sources in:


https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.2.29/

The SHA1 checksum of the archive is
f344d8785f94d983145212eae7e3fa7be48bdfb8.

A staged Maven repository is available for review at:

https://repository.apache.org/

The command for running automated checks against this release candidate is:

$ sh check-release.sh oak 1.2.29
f344d8785f94d983145212eae7e3fa7be48bdfb8

Please vote on releasing this package as Apache Jackrabbit Oak 1.2.29.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.

[ ] +1 Release this package as Apache Jackrabbit Oak 1.2.29
[ ] -1 Do not release this package because...

Thanks
Amit

Release plan Oak 1.2.29

[Amit Jain]

Hi,

Oak 1.2.29 is scheduled for release on 12th March (Monday). If you need
more time for urgent issues please let me know.

Thanks
Amit

Fwd: [CompositeDataStore] pull request to review GC changes

[Amit Jain]

Hi,

Could you please move this discussion to the relvant jira issue.

Thanks
Amit

On Thu, Feb 22, 2018 at 1:32 PM, Matt Ryan <o...@mvryan.org> wrote:

> Hi,
>
>
> On February 21, 2018 at 10:32:48 PM, Amit Jain (am...@ieee.org) wrote:
>
> Hi,
>
>
> > Now the problem comes when secondary tries to run the sweep phase. It
> will
> > first try to verify that a references file exists for each repository
> file
> > in DS_P - and fail. This fails because primary deleted its references
> file
> > already. Thus secondary will cancel GC and thus blob C never ends up
> > getting deleted. Note that secondary must delete C because it is the
> only
> > repository that knows about C.
> >
> > This same situation exists also if secondary sweeps first. If record D
> was
> > created by primary after secondary was cloned, then D is deleted by
> > primary, secondary never knows about blob D so it cannot delete it
> during
> > the sweep phase - it can only be deleted by primary.
> >
>
> The solution for Shared DataStore currently is to require all repositories
> to run a Mark phase then run the Sweep phase on one of them.
>
>
> Yes.  Sorry, I didn’t mention that.  I was trying to be brief and ended up
> being unclear.  In the situation I described above it is definitely running
> the mark phase first and then the sweep phase.  The problem is still as I
> described - no matter which one runs sweep first, it cannot delete all the
> binaries that may possibly have been deleted on both systems.
>
The problem is because that's how the systems are set up. For this
particular problem on the Secondary there is no reason to even account for
the Primary's datastore as it should not and cannot delete anything in
there.

>
> >
> > The change I made to the garbage collector is that when a repository
> > finishes the sweep phase, it doesn’t necessarily delete the references
> > file. Instead it marks the data store with a “sweepComplete” file
> > indicating that this repository finished the sweep phase. When there is a
>
> > “sweepComplete” file for every repository (in other words, the last
> > repository to sweep), then all the references files are deleted.
> >
> > Well currently the problem is that all repositories are not required to
> run the sweep phase. The solution above would have been ok when the GC is
> to be run manually at different times as in your case.
>
> Exactly - in the case I’ve described both have to successfully run a sweep
> or not all binaries will be deleted.
>
>
> But in the real world applications typically there's a cron (e.g. AEM
> maintenance task) which could be setup to execute weekly at a particular
> time on all repositories. In this case in almost all cases the repository
> which finished the Mark phase at the last would only be able to execute the
>
> Sweep phase as it would be the only repository to see all the reference
> files for other repos (others executing before it would fail). This is
> still Ok for the Shared DataStore use cases we have.
> But with the above solution since not all repositories would be able to run
>
> the sweep phase the reference files won't be cleaned up.
>
> A very valid point.  I’ll need to think that one through some more.
>
>
>
> Besides there's a problem of the Sweep phase on the primary encountering
> blobs it does not know about (from the secondary) and which it cannot
> delete creating an unpleasant experience. As I understand the Primary could
>
> be a production system and having these sort of errors crop up would be
> problematic.
>
> If they are regarded as errors, yes.  Currently this logs a WARN level
> message (not an ERROR) which suggests that sometimes not all the binaries
> targeted for deletion will actually be deleted.
>
> So this might be an issue of setting clear expectations.  But I do see the
> point.
>
Yes these are logged as WARN as these are not fatal and empirically these
are problematic and is questioned by customers. But apart from that there
is a performance impact also as each binary is attempted for deletion which
incurs a penalty.

>
>
> So, generically the solution would be to use the shared DataStore GC
> paradigm we currently have which requires Mark phase to be run on all
> repositories before running a Sweep.
>
> Yes - like I said this is being done, it still requires that both repos do
> a sweep.
>
>
>
> For this specific use case some observations and quick rough sketch of a
> possible solution:
> * The DataStores for the 2 repositories - Primary & Secondary can be
> thought of as Shared & Private
> ** Primary does not know about Secondary and could be an existi

Re: [VOTE] Release Apache Jackrabbit Oak 1.8.2

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.8.2

with

[INFO]

[INFO] Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-04T01:09:06+05:30)
[INFO] OS name: "mac os x", version: "10.13.3", arch: "x86_64", family:
"mac"
[INFO] Java version: 1.8.0_144, vendor: Oracle Corporation
[INFO]


Thanks
Amit

On Tue, Feb 6, 2018 at 6:19 PM, Davide Giannella  wrote:

>
> A candidate for the Jackrabbit Oak 1.8.2 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.8.2/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.8.2/
>
> The SHA1 checksum of the archive is
> 6fd2c8ac5bacffce016a41c4da783323ef763ab6.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.8.2 6fd2c8ac5bacffce016a41c4da7833
> 23ef763ab6
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.8.2.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.8.2
> [ ] -1 Do not release this package because...
>
> D.
>

Re: svn commit: r1822884 [1/3] - in /jackrabbit/oak/branches/1.6: ./ oak-parent/ oak-solr-core/ oak-solr-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/solr/configuration/ oak-solr-core/sr

[Amit Jain]

Hi Tommaso,

I am getting these errors on building 1.6 which means there missing
backports to 1.6.

Thanks
Amit


--

[INFO]


[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
(default-compile) on project oak-run: Compilation failure: Compilation
failure:

[ERROR]
/Users/amjain/source/svn/oak/branches/1.6/oak-run/src/main/java/org/apache/jackrabbit/oak/benchmark/FullTextSolrSearchTest.java:[101,74]
error: constructor RemoteSolrServerConfiguration in class
RemoteSolrServerConfiguration cannot be applied to given types;

[ERROR]   found: String,String,int,int,,String

[ERROR]   reason: actual argument String cannot be converted to int by
method invocation conversion

[ERROR]
/Users/amjain/source/svn/oak/branches/1.6/oak-run/src/main/java/org/apache/jackrabbit/oak/benchmark/FullTextSolrSearchTest.java:[116,72]
error: incompatible types

[ERROR]   required: SolrServer

[ERROR]   found:SolrClient

[ERROR]
/Users/amjain/source/svn/oak/branches/1.6/oak-run/src/main/java/org/apache/jackrabbit/oak/benchmark/FullTextSolrSearchTest.java:[133,60]
error: incompatible types

[ERROR] -> [Help 1] --

Re: Oak 1.8.2 release plan

[Amit Jain]

Backported the fix for OAK-7223 to 1.8 branch.
Release is good to go from my side.

Thanks
Amit

On Mon, Feb 5, 2018 at 3:55 PM, Davide Giannella  wrote:

> On 31/01/2018 10:09, Davide Giannella wrote:
> > We have a couple of blockers, which may require more testing. Postponing
> > to Monday to see if we're good to go or not.
>
> We still have to wait for confirmation on testing side that the two
> blockers are actually solved. Very likely this will be moved to future
> date.
>
> OAK-7223, OAK-7162
>
> D.
>
>
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.8.1

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.8.1

Thanks
Amit

On Mon, Jan 22, 2018 at 9:14 PM, Davide Giannella  wrote:

>
> A candidate for the Jackrabbit Oak 1.8.1 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.8.1/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.8.1/
>
> The SHA1 checksum of the archive is
> 3cbf1e206ac26cc764b8b6d658de0c97cf896acd.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.8.1 3cbf1e206ac26cc764b8b6d658de0c
> 97cf896acd
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.8.1.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.8.1
> [ ] -1 Do not release this package because...
>
> D.
>

[ANNOUNCE] Apache Jackrabbit Oak 1.2.28 released

[Amit Jain]

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak 1.2.28. The release is available for download at:

http://jackrabbit.apache.org/downloads.html

See the full release notes below for details about this released:

Release Notes -- Apache Jackrabbit Oak -- Version 1.2.28

Introduction


Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

Apache Jackrabbit Oak 1.2.28 is a patch release that contains fixes and
improvements over Oak 1.2. Jackrabbit Oak 1.2.x releases are considered
stable and targeted for production use.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.2.28
-

Sub-task

[OAK-5299] - Introduce BlobFactory in OakDirectory

Technical task

[OAK-6237] - Tomcat JDBC pool's StatementCache interceptor may cache
borked PreparedStatements with DB2
[OAK-6652] - RDB*Store: update postgresql JDBC driver reference to
42.1.4
[OAK-6660] - RDB*Store: update mysql JDBC driver reference to 5.1.44
(2017-08-30)
[OAK-6696] - RDB*Store: update Tomcat JDBC pool dependency to 7.0.81
[OAK-6782] - RDBDocumentStore: inconsistent handling of cache
invalidation on remove()
[OAK-6903] - RDB*Store: update Tomcat JDBC pool dependency to 7.0.82
[OAK-7068] - RDBBlobStore may wrap SQLExceptions into RuntimeExceptions
[OAK-7069] - RDBDataSourceWrapper: properly name
setTemporaryUpdateException

Bug

[OAK-4518] - ConcurrentAddReferenceTest fails occasionally
[OAK-5238] - IndexCopier causes concurrent update on NodeBuilder
[OAK-5933] - Checkpoints are not sorted correctly in RepositorySidegrade
[OAK-6011] - Test failure: JdbcToSegmentTest:validateMigration
[OAK-6057] - incorrect system property check in blob/upgrade tests
[OAK-6306] - upgrade uses lucene wrong version (transient dependency)
[OAK-6360] - Failed to retrieve previously indexed checkpoint in
composite node store
[OAK-6454] - Inaccurate data in the oak-upgrade progress logger
[OAK-6560] - Sidegrade uses too much memory
[OAK-6611] - [upgrade][oak-blob-cloud] Many S3DataStore errors during
migration with oak-upgrade
[OAK-6633] - Overwriting a versionable node with the
copy-versions=false doesn't remove versionable properties
[OAK-6685] - Background operation may fail when document is malformed
[OAK-6953] - CacheLIRS cannot be disabled
[OAK-6970] - IncludeIndexTest failure
[OAK-7101] - Stale documents in RDBDocumentStore cache
[OAK-7152] - CacheMap.clear() never returns


Improvement

[OAK-4863] - Reduce query batch size for deleted documents
[OAK-5317] - MongoBlobStore creates _id index unnecessarily
[OAK-6003] - Allow to migrate checkpoints for all type of sidegrades
[OAK-6131] - No need to rebuild the counter/uuid index anymore
[OAK-6188] - Allow to exclude nodes containing name fragment during the
migration
[OAK-6190] - Allow to migrate checkpoints even if the custom include
paths are specified
[OAK-6218] - Including id in DocumentStoreException which wrap
MongoException
[OAK-6333] - IndexPlanner should use actual entryCount instead of
limiting it to 1000
[OAK-6336] - Use the oak-blob-cloud for s3 support in oak-upgrade
[OAK-6650] - new release checksum requirements
[OAK-6878] - Populate S3DataStore fields with the passed properties in
oak-upgrade
[OAK-7121] - DocumentStore testing: allow config of DocumentMK.Builder
in AbstractDocumentStoreTest


Task

[OAK-6655] - Update travis build configuration
[OAK-6657] - Remove travis webhook configuration
[OAK-6751] - Update Oak 1.2 and 1.4 to Jackrabbit 2.12.8
[OAK-6952] - add SHA512 checksums to releases
[OAK-7120] - Use specific MongoDB version on travis-ci
[OAK-7126] - make RDBCacheConsistency2Test store-agnostic



In addition to the above-mentioned changes, this release contains
all changes included up to the Apache Jackrabbit Oak 1.2.27 release.

For more detailed information about all the changes in this and other
Oak releases, please see the Oak issue tracker at

  https://issues.apache.org/jira/browse/OAK

Release Contents


This release consists of a single source archive packaged as a zip file.
The archive can be unpacked with the jar tool from your JDK installation.
See the README.md file for instructions on how to build this release.

The source archive is accompanied by SHA1 and MD5 checksums and a PGP
signature that you can use to verify the authenticity of your download.
The public key used for the PGP signature can be found at
http://www.apache.org/dist/jackrabbit/KEYS.

About Apache Jackrabbit Oak
---

Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for 

[RESULT][VOTE] Release Apache Jackrabbit Oak 1.2.28

[Amit Jain]

Hi,

The vote passes as follows:
+1 Julian Reschke
+1 Alex Deparvu
+1 Andrei Dulceanu
+1 Davide Giannella
+1 Amit Jain

Thanks for voting. I'll push the release out.

Regards
Amit

[VOTE] Release Apache Jackrabbit Oak 1.2.28

[Amit Jain]

A candidate for the Jackrabbit Oak 1.2.28 release is available at:

https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.2.28/

The release candidate is a zip archive of the sources in:


https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.2.28/

The SHA1 checksum of the archive is
ab75dcba003fba0cace30d49307c92b9ecbb27cd.

A staged Maven repository is available for review at:

https://repository.apache.org/

The command for running automated checks against this release candidate is:

$ sh check-release.sh oak 1.2.28
ab75dcba003fba0cace30d49307c92b9ecbb27cd

Please vote on releasing this package as Apache Jackrabbit Oak 1.2.28.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.

[ ] +1 Release this package as Apache Jackrabbit Oak 1.2.28
[ ] -1 Do not release this package because...

Thanks
Amit

Re: [VOTE] Release Apache Jackrabbit Oak 1.6.8

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.6.8

Thanks
Amit

On Wed, Jan 10, 2018 at 2:48 AM, Davide Giannella  wrote:

>
> A candidate for the Jackrabbit Oak 1.6.8 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.6.8/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.6.8/
>
> The SHA1 checksum of the archive is
> 7afc203cab3881e3d54ce09707447acfcbf2734e.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.6.8 7afc203cab3881e3d54ce09707447a
> cfcbf2734e
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.6.8.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.6.8
> [ ] -1 Do not release this package because...
>
> D.
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.8.0

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.8.0

Thanks
Amit

On Tue, Jan 9, 2018 at 5:23 PM, Davide Giannella  wrote:

> A candidate for the Jackrabbit Oak 1.8.0 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.8.0/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.8.0/
>
> The SHA1 checksum of the archive is
> 8aafd753f98e02df0de6b32e4d7e065ebe450b88.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.8.0 8aafd753f98e02df0de6b32e4d7e06
> 5ebe450b88
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.8.0.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.8.0
> [ ] -1 Do not release this package because...
>
> D.
>

[ANNOUNCE] Apache Jackrabbit Oak 1.0.40 released

[Amit Jain]

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak 1.0.40. 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 -- Version 1.0.40

Introduction


Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

Apache Jackrabbit Oak 1.0.40 is a patch release that contains fixes and
improvements over Oak 1.0. Jackrabbit Oak 1.0.x releases are considered
stable and targeted for production use.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.


Changes in Oak 1.0.40
-


Sub-task

[OAK-5299] - Introduce BlobFactory in OakDirectory

Technical task

[OAK-6237] - Tomcat JDBC pool's StatementCache interceptor may cache
borked PreparedStatements with DB2
[OAK-6652] - RDB*Store: update postgresql JDBC driver reference to
42.1.4
[OAK-6660] - RDB*Store: update mysql JDBC driver reference to 5.1.44
(2017-08-30)
[OAK-6696] - RDB*Store: update Tomcat JDBC pool dependency to 7.0.81
[OAK-6782] - RDBDocumentStore: inconsistent handling of cache
invalidation on remove()
[OAK-6903] - RDB*Store: update Tomcat JDBC pool dependency to 7.0.82
[OAK-7068] - RDBBlobStore may wrap SQLExceptions into RuntimeExceptions
[OAK-7069] - RDBDataSourceWrapper: properly name
setTemporaryUpdateException


Bug

[OAK-4518] - ConcurrentAddReferenceTest fails occasionally
[OAK-5238] - IndexCopier causes concurrent update on NodeBuilder
[OAK-5933] - Checkpoints are not sorted correctly in RepositorySidegrade
[OAK-6011] - Test failure: JdbcToSegmentTest:validateMigration
[OAK-6057] - incorrect system property check in blob/upgrade tests
[OAK-6306] - upgrade uses lucene wrong version (transient dependency)
[OAK-6360] - Failed to retrieve previously indexed checkpoint in
composite node store
[OAK-6454] - Inaccurate data in the oak-upgrade progress logger
[OAK-6560] - Sidegrade uses too much memory
[OAK-6611] - [upgrade][oak-blob-cloud] Many S3DataStore errors during
migration with oak-upgrade
[OAK-6633] - Overwriting a versionable node with the
copy-versions=false doesn't remove versionable properties
[OAK-6685] - Background operation may fail when document is malformed
[OAK-6953] - CacheLIRS cannot be disabled
[OAK-6970] - IncludeIndexTest failure
[OAK-7101] - Stale documents in RDBDocumentStore cache


Improvement

[OAK-2638] - Use message from causing exception in
DocumentStoreException.convert()
[OAK-4863] - Reduce query batch size for deleted documents
[OAK-5317] - MongoBlobStore creates _id index unnecessarily
[OAK-6003] - Allow to migrate checkpoints for all type of sidegrades
[OAK-6131] - No need to rebuild the counter/uuid index anymore
[OAK-6188] - Allow to exclude nodes containing name fragment during the
migration
[OAK-6190] - Allow to migrate checkpoints even if the custom include
paths are specified
[OAK-6218] - Including id in DocumentStoreException which wrap
MongoException
[OAK-6650] - new release checksum requirements
[OAK-6878] - Populate S3DataStore fields with the passed properties in
oak-upgrade


Task

[OAK-6655] - Update travis build configuration
[OAK-6657] - Remove travis webhook configuration
[OAK-6701] - Update Oak 1.0 to Jackrabbit 2.8.6
[OAK-6952] - add SHA512 checksums to releases
[OAK-6971] - Remove composite node store-related features from the
oak-upgrade
[OAK-7076] - Update Oak 1.0 to Jackrabbit 2.8.7


In addition to the above-mentioned changes, this release contains
all changes included in previous Apache Jackrabbit Oak 1.0.x releases.

Please note, the backported RDB support for the DocumentNodeStore is
considered
experimental at this point and is not yet ready for production use. Feel
free
to try it out and report any issues you may see to the Oak developers.

For more detailed information about all the changes in this and other
Oak releases, please see the Oak issue tracker at

  https://issues.apache.org/jira/browse/OAK

Release Contents


This release consists of a single source archive packaged as a zip file.
The archive can be unpacked with the jar tool from your JDK installation.
See the README.md file for instructions on how to build this release.

The source archive is accompanied by SHA1 and MD5 checksums and a PGP
signature that you can use to verify the authenticity of your download.
The public key used for the PGP signature can be found at
http://www.apache.org/dist/jackrabbit/KEYS.

About Apache Jackrabbit Oak
---

Jackrabbit Oak is a scalable, high-performance hierarchical content
repository 

[RESULT][VOTE] Release Apache Jackrabbit Oak 1.0.40

[Amit Jain]

Hi,

The vote passes as follows:

+1 Julian Reschke
+1 Davide Giannella
+1 Andrei Dulceanu
+1 Amit Jain

Thanks for voting. I'll push the release out.

Regards
Amit

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.40

[Amit Jain]

Hi,

The vote passes as follows:

+1 Julian Reschke
+1 Davide Giannella
+1 Anfrei Dulceanu
+

On Fri, Jan 5, 2018 at 5:18 PM, Andrei Dulceanu 
wrote:

> [X] +1 Release this package as Apache Jackrabbit Oak 1.0.40
>
> where
>
> [INFO]
> 
> [INFO] Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
> 2017-10-18T10:58:13+03:00)
> [INFO] OS name: "mac os x", version: "10.13.2", arch: "x86_64", family:
> "mac"
> [INFO] Java version: 1.8.0_65, vendor: Oracle Corporation
> [INFO]
> 
>
> Andrei
>
> 2018-01-05 13:36 GMT+02:00 Davide Giannella :
>
> > [X] +1 Release this package as Apache Jackrabbit Oak 1.0.40
> >
> > D.
> >
> >
> >
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.40

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.0.40

Thanks
Amit

On Fri, Jan 5, 2018 at 11:31 AM, Amit Jain <am...@apache.org> wrote:

> A candidate for the Jackrabbit Oak 1.0.40 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.0.40/
>
> The release candidate is a zip archive of the sources in:
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/
> jackrabbit-oak-1.0.40/
>
> The SHA1 checksum of the archive is 9371a208ddf72b276611b2f90a1fc1
> b2d09768e6.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.0.40 9371a208ddf72b276611b2f90a1fc1
> b2d09768e6
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.0.40.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.0.40
> [ ] -1 Do not release this package because...
>
> Thanks
> Amit
>

[VOTE] Release Apache Jackrabbit Oak 1.0.40

[Amit Jain]

A candidate for the Jackrabbit Oak 1.0.40 release is available at:

https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.0.40/

The release candidate is a zip archive of the sources in:


https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.0.40/

The SHA1 checksum of the archive is
9371a208ddf72b276611b2f90a1fc1b2d09768e6.

A staged Maven repository is available for review at:

https://repository.apache.org/

The command for running automated checks against this release candidate is:

$ sh check-release.sh oak 1.0.40
9371a208ddf72b276611b2f90a1fc1b2d09768e6

Please vote on releasing this package as Apache Jackrabbit Oak 1.0.40.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.

[ ] +1 Release this package as Apache Jackrabbit Oak 1.0.40
[ ] -1 Do not release this package because...

Thanks
Amit

Re: [VOTE] Release Apache Jackrabbit Oak 1.7.14

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.7.14

with
[INFO] 
[INFO] Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-04T01:09:06+05:30)
[INFO] OS name: "mac os x", version: "10.13.2", arch: "x86_64", family: "mac"
[INFO] Java version: 1.8.0_144, vendor: Oracle Corporation
[INFO] 

Thanks
Amit

On Wed, Dec 20, 2017 at 11:16 PM, Davide Giannella  wrote:
>
> A candidate for the Jackrabbit Oak 1.7.14 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.7.14/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.7.14/
>
> The SHA1 checksum of the archive is
> 40c24fc5c36b511536e355a9864e3679177924b8.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.7.14
> 40c24fc5c36b511536e355a9864e3679177924b8
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.7.14.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.7.14
> [ ] -1 Do not release this package because...
> D

Re: [VOTE] Release Apache Jackrabbit Oak 1.7.12

[Amit Jain]

The issue of failing tests is fixed with OAK-7026 now. The impact of
the issue would be that the each execution of the datastorecheck
command with verbose option on windows would leave a temporary file.
Given limited impact my vote stays +1 for the release.

Thanks
Amit

On Tue, Dec 5, 2017 at 1:06 PM, Julian Reschke <julian.resc...@gmx.de> wrote:
> On 2017-12-05 08:27, Amit Jain wrote:
>>
>> Looking into the test failures...Seems to be an intermittent issue on
>> windows only
>> Had tested on windows as well before the commits
>> ...
>
>
> For me the tests seem to fail reliably. (Yes, on Windows)
>
> Best regards, Julian

Re: [VOTE] Release Apache Jackrabbit Oak 1.7.12

[Amit Jain]

Looking into the test failures...Seems to be an intermittent issue on
windows only
Had tested on windows as well before the commits

On Tue, Dec 5, 2017 at 12:53 PM, Julian Reschke  wrote:
> On 2017-12-05 07:10, Julian Reschke wrote:
>>
>> On 2017-12-04 21:25, Davide Giannella wrote:
>>>
>>> ...
>>
>>
>> Fails for me with:
>>
>>> [INFO] Running org.apache.jackrabbit.oak.run.DataStoreCheckTest
>>> [ERROR] Tests run: 12, Failures: 0, Errors: 2, Skipped: 0, Time elapsed:
>>> 2.02 s <<< FAILURE! - in org.apache.jackrabbit.oak.run.DataStoreCheckTest
>>> [ERROR]
>>> testConsistencyVerbose(org.apache.jackrabbit.oak.run.DataStoreCheckTest)
>>> Time elapsed: 0.26 s  <<< ERROR!
>>> java.io.IOException: Unable to delete file:
>>> C:\tmp\ids5117643859629864856.tmp
>>> at
>>> org.apache.jackrabbit.oak.run.DataStoreCheckTest.testAllParamsVerbose(DataStoreCheckTest.java:332)
>>> at
>>> org.apache.jackrabbit.oak.run.DataStoreCheckTest.testConsistencyVerbose(DataStoreCheckTest.java:233)
>>>
>>> [ERROR]
>>> testConsistencyVerboseWithDeleteTracker(org.apache.jackrabbit.oak.run.DataStoreCheckTest)
>>> Time elapsed: 0.172 s  <<< ERROR!
>>> java.io.IOException: Unable to delete file:
>>> C:\tmp\ids7859857301677881810.tmp
>>> at
>>> org.apache.jackrabbit.oak.run.DataStoreCheckTest.testAllParamsVerbose(DataStoreCheckTest.java:332)
>>> at
>>> org.apache.jackrabbit.oak.run.DataStoreCheckTest.testConsistencyVerboseWithDeleteTracker(DataStoreCheckTest.java:297)
>>
>>
>> Best regards, Julian
>
>
> Apparently cleanup was disabled in the changes for
> , and then re-enabled for
> .
>
> Best regards, Julian
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.7.12

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.7.12

Thanks
Amit

On Tue, Dec 5, 2017 at 1:55 AM, Davide Giannella  wrote:
>
> A candidate for the Jackrabbit Oak 1.7.12 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.7.12/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.7.12/
>
> The SHA1 checksum of the archive is
> eca45d4c8d357654253eb488526c4ef2b421ed06.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.7.12
> eca45d4c8d357654253eb488526c4ef2b421ed06
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.7.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.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.7.12
> [ ] -1 Do not release this package because...
>
> D.

Re: [VOTE] Release Apache Jackrabbit Oak 1.7.11

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.7.11

Thanks
Amit

On Tue, Nov 7, 2017 at 6:45 PM, Davide Giannella  wrote:
> A candidate for the Jackrabbit Oak 1.7.11 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.7.11/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.7.11/
>
> The SHA1 checksum of the archive is
> 445beb053b7f11b65d31e85da777b8d45b44f747.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.7.11
> 445beb053b7f11b65d31e85da777b8d45b44f747
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.7.11.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.7.11
> [ ] -1 Do not release this package because...
>
> D.

Re: [VOTE] Release Apache Jackrabbit Oak 1.6.6

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.6.6

Thanks
Amit

On Mon, Oct 30, 2017 at 2:57 PM, Davide Giannella  wrote:
>
>
> A candidate for the Jackrabbit Oak 1.6.6 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.6.6/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.6.6/
>
> The SHA1 checksum of the archive is
> d11179243a206cbb727a18d47025fca18803b4d6.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.6.6 d11179243a206cbb727a18d47025fca18803b4d6
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.6.6.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.6.6
> [ ] -1 Do not release this package because...
>
> D.

Re: [VOTE] Release Apache Jackrabbit Oak 1.7.10

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.7.10

Thanks
Amit

On Mon, Oct 23, 2017 at 10:02 PM, Davide Giannella  wrote:
>
> A candidate for the Jackrabbit Oak 1.7.10 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.7.10/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.7.10/
>
> The SHA1 checksum of the archive is
> e0c6282659cee0a8e9bd6ed4be35e0d5abad57b1.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.7.10
> e0c6282659cee0a8e9bd6ed4be35e0d5abad57b1
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.7.10.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.7.10
> [ ] -1 Do not release this package because...
>
> D.

Re: Intent to backport OAK-6604 and OAK-6611 to 1.6

[Amit Jain]

+1

Thanks
Amit

On Tue, Oct 10, 2017 at 5:18 PM, Tomek Rekawek 
wrote:

> Hi,
>
> I plan to backport these two issues. They improve the S3 resilience in
> oak-upgrade by using the newer version of S3DataStore and waiting until all
> the uploads are finished.
>
> Regards,
> Tomek
>
> --
> Tomek Rękawek | Adobe Research | www.adobe.com
> reka...@adobe.com
>
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.7.7

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.7.7

Thanks
Amit

On Mon, Sep 11, 2017 at 6:42 PM, Davide Giannella  wrote:

> A candidate for the Jackrabbit Oak 1.7.7 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.7.7/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.7.7/
>
> The SHA1 checksum of the archive is
> 3d57847b3dbf390daf7c552472fb3a53f63b2558.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.7.7 3d57847b3dbf390daf7c552472fb3a
> 53f63b2558
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.7.7.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.7.7
> [ ] -1 Do not release this package because...
>
> D.
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.6.5

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.6.5

Thanks
Amit

On Mon, Sep 4, 2017 at 8:10 PM, Davide Giannella  wrote:

> A candidate for the Jackrabbit Oak 1.6.5 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.6.5/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.6.5/
>
> The SHA1 checksum of the archive is
> 1b7407bb7b51209d8056ea4aad3757378d10e1ba.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.6.5 1b7407bb7b51209d8056ea4aad3757
> 378d10e1ba
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.6.5.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.6.5
> [ ] -1 Do not release this package because...
> D.
>

Re: svn commit: r1807198 - /jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/apache/jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java

[Amit Jain]

Hi Tomek,

You missed the actual store.close().

Thanks
Amit

On Mon, Sep 4, 2017 at 2:26 PM,  wrote:

> Author: tomekr
> Date: Mon Sep  4 08:56:45 2017
> New Revision: 1807198
>
> URL: http://svn.apache.org/viewvc?rev=1807198=rev
> Log:
> OAK-6611: Many S3DataStore errors during migration with oak-upgrade
>
> -wait until all the pending s3 uploads are done after the migration
>
> Modified:
> jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/
> apache/jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java
>
> Modified: jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/
> apache/jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java
> URL: http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-
> upgrade/src/main/java/org/apache/jackrabbit/oak/upgrade/
> cli/blob/S3DataStoreFactory.java?rev=1807198=1807197&
> r2=1807198=diff
> 
> ==
> --- jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/
> apache/jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java (original)
> +++ jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/
> apache/jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java Mon Sep  4
> 08:56:45 2017
> @@ -28,20 +28,15 @@ import java.util.regex.Pattern;
>  import javax.jcr.RepositoryException;
>
>  import org.apache.commons.io.IOUtils;
> -import org.apache.jackrabbit.core.data.DataStoreException;
>  import org.apache.jackrabbit.oak.blob.cloud.s3.S3DataStore;
>  import org.apache.jackrabbit.oak.plugins.blob.datastore.
> DataStoreBlobStore;
>  import org.apache.jackrabbit.oak.spi.blob.BlobStore;
> -import org.slf4j.Logger;
> -import org.slf4j.LoggerFactory;
>
>  import com.google.common.io.Closer;
>  import com.google.common.io.Files;
>
>  public class S3DataStoreFactory implements BlobStoreFactory {
>
> -private static final Logger log = LoggerFactory.getLogger(
> S3DataStoreFactory.class);
> -
>  private static final Pattern STRIP_VALUE_PATTERN =
> Pattern.compile("^[TILFDXSCB]?\"(.*)\"\\W*$");
>
>  private final Properties props;
> @@ -94,8 +89,10 @@ public class S3DataStoreFactory implemen
>  @Override
>  public void close() throws IOException {
>  try {
> -store.close();
> -} catch (DataStoreException e) {
> +while (store.getStats().get(1).getElementCount() >
> 0) {
> +Thread.sleep(100);
> +}
> +} catch (InterruptedException e) {
>  throw new IOException(e);
>  }
>  }
>
>
>

Re: svn commit: r1806894 - /jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/apache/jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java

[Amit Jain]

Yes +1 for backporting.

Thanks
Amit

On Fri, Sep 1, 2017 at 2:15 PM, Tomek Rekawek <reka...@adobe.com.invalid>
wrote:

> Hi Amit,
>
> thanks for noticing this. I’ve used the native S3DataStore#close() method.
> Also, I think it’s a good backport candidate (there were customers
> complaining on the Jackrabbit S3DataStore used in oak-upgrade). WDYT?
>
> Regards,
> Tomek
>
> --
> Tomek Rękawek | Adobe Research | www.adobe.com
> reka...@adobe.com
>
> > On 1 Sep 2017, at 10:17, Amit Jain <am...@ieee.org> wrote:
> >
> > Just saw that you already did that.
> >
> > Thanks
> > Amit
> >
> > On Fri, Sep 1, 2017 at 1:46 PM, Amit Jain <am...@ieee.org> wrote:
> >
> >> Hi Tomek,
> >>
> >> The {{asCloseable}} should also be changed to not take in the
> >> CachingDataStore but either the AbstractSharedCachingDataStore or
> >> S3DataStore instead and subsequently the import for CachingDataStore
> also
> >> removed.
> >>
> >> Thanks
> >> Amit
> >>
> >> On Fri, Sep 1, 2017 at 1:00 PM, <tom...@apache.org> wrote:
> >>
> >>> Author: tomekr
> >>> Date: Fri Sep  1 07:30:49 2017
> >>> New Revision: 1806894
> >>>
> >>> URL: https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fsvn.apache.org%2Fviewvc%3Frev%3D1806894%
> 26view%3Drev=02%7C01%7C%7C867bccc313a6432c02d308d4f111ea3d%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636398506629039415=
> 1337smywMXYTFMUYsuyv1or7oTA5IZ9s6iaU8pTqe3c%3D=0
> >>> Log:
> >>> OAK-6604: Oak Blob Cloud is not used by oak-upgrade
> >>>
> >>> Modified:
> >>>jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/apache/
> >>> jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java
> >>>
> >>> Modified: jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/apache/
> >>> jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java
> >>> URL: https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fsvn.apache.org%2Fviewvc%2Fjackrabbit%2Foak%
> 2Ftrunk%2Foak-upgrad=02%7C01%7C%7C867bccc313a6432c02d308d4f111ea3d%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636398506629039415=
> M4l0HNGNjGyt7P3jH3KpxBRr0in3jpcqHFITrnkCLeQ%3D=0
> >>> e/src/main/java/org/apache/jackrabbit/oak/upgrade/cli/
> >>> blob/S3DataStoreFactory.java?rev=1806894=1806893=
> 1806894=diff
> >>> 
> >>> ==
> >>> --- jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/apache/
> >>> jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java (original)
> >>> +++ jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/apache/
> >>> jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java Fri Sep  1
> >>> 07:30:49 2017
> >>> @@ -31,7 +31,7 @@ import org.apache.commons.io.FileUtils;
> >>> import org.apache.commons.io.IOUtils;
> >>> import org.apache.jackrabbit.core.data.CachingDataStore;
> >>> import org.apache.jackrabbit.core.data.DataStoreException;
> >>> -import org.apache.jackrabbit.oak.blob.cloud.aws.s3.S3DataStore;
> >>> +import org.apache.jackrabbit.oak.blob.cloud.s3.S3DataStore;
> >>> import org.apache.jackrabbit.oak.plugins.blob.datastore.DataStoreBl
> >>> obStore;
> >>> import org.apache.jackrabbit.oak.spi.blob.BlobStore;
> >>> import org.slf4j.Logger;
> >>>
> >>>
> >>>
> >>
>
>

Re: svn commit: r1806894 - /jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/apache/jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java

[Amit Jain]

Just saw that you already did that.

Thanks
Amit

On Fri, Sep 1, 2017 at 1:46 PM, Amit Jain <am...@ieee.org> wrote:

> Hi Tomek,
>
> The {{asCloseable}} should also be changed to not take in the
> CachingDataStore but either the AbstractSharedCachingDataStore or
> S3DataStore instead and subsequently the import for CachingDataStore also
> removed.
>
> Thanks
> Amit
>
> On Fri, Sep 1, 2017 at 1:00 PM, <tom...@apache.org> wrote:
>
>> Author: tomekr
>> Date: Fri Sep  1 07:30:49 2017
>> New Revision: 1806894
>>
>> URL: http://svn.apache.org/viewvc?rev=1806894=rev
>> Log:
>> OAK-6604: Oak Blob Cloud is not used by oak-upgrade
>>
>> Modified:
>> jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/apache/
>> jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java
>>
>> Modified: jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/apache/
>> jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java
>> URL: http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-upgrad
>> e/src/main/java/org/apache/jackrabbit/oak/upgrade/cli/
>> blob/S3DataStoreFactory.java?rev=1806894=1806893=1806894=diff
>> 
>> ==
>> --- jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/apache/
>> jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java (original)
>> +++ jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/apache/
>> jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java Fri Sep  1
>> 07:30:49 2017
>> @@ -31,7 +31,7 @@ import org.apache.commons.io.FileUtils;
>>  import org.apache.commons.io.IOUtils;
>>  import org.apache.jackrabbit.core.data.CachingDataStore;
>>  import org.apache.jackrabbit.core.data.DataStoreException;
>> -import org.apache.jackrabbit.oak.blob.cloud.aws.s3.S3DataStore;
>> +import org.apache.jackrabbit.oak.blob.cloud.s3.S3DataStore;
>>  import org.apache.jackrabbit.oak.plugins.blob.datastore.DataStoreBl
>> obStore;
>>  import org.apache.jackrabbit.oak.spi.blob.BlobStore;
>>  import org.slf4j.Logger;
>>
>>
>>
>

Re: svn commit: r1806894 - /jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/apache/jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java

[Amit Jain]

Hi Tomek,

The {{asCloseable}} should also be changed to not take in the
CachingDataStore but either the AbstractSharedCachingDataStore or
S3DataStore instead and subsequently the import for CachingDataStore also
removed.

Thanks
Amit

On Fri, Sep 1, 2017 at 1:00 PM,  wrote:

> Author: tomekr
> Date: Fri Sep  1 07:30:49 2017
> New Revision: 1806894
>
> URL: http://svn.apache.org/viewvc?rev=1806894=rev
> Log:
> OAK-6604: Oak Blob Cloud is not used by oak-upgrade
>
> Modified:
> jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/
> apache/jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java
>
> Modified: jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/
> apache/jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java
> URL: http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-
> upgrade/src/main/java/org/apache/jackrabbit/oak/upgrade/
> cli/blob/S3DataStoreFactory.java?rev=1806894=1806893&
> r2=1806894=diff
> 
> ==
> --- jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/
> apache/jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java (original)
> +++ jackrabbit/oak/trunk/oak-upgrade/src/main/java/org/
> apache/jackrabbit/oak/upgrade/cli/blob/S3DataStoreFactory.java Fri Sep  1
> 07:30:49 2017
> @@ -31,7 +31,7 @@ import org.apache.commons.io.FileUtils;
>  import org.apache.commons.io.IOUtils;
>  import org.apache.jackrabbit.core.data.CachingDataStore;
>  import org.apache.jackrabbit.core.data.DataStoreException;
> -import org.apache.jackrabbit.oak.blob.cloud.aws.s3.S3DataStore;
> +import org.apache.jackrabbit.oak.blob.cloud.s3.S3DataStore;
>  import org.apache.jackrabbit.oak.plugins.blob.datastore.
> DataStoreBlobStore;
>  import org.apache.jackrabbit.oak.spi.blob.BlobStore;
>  import org.slf4j.Logger;
>
>
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.4.18

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.4.18

Thanks
Amit

On Wed, Aug 30, 2017 at 2:53 PM, Davide Giannella  wrote:

>
> A candidate for the Jackrabbit Oak 1.4.18 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.4.18/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/
> jackrabbit-oak-1.4.18/
>
> The SHA1 checksum of the archive is
> 9e7353a042c2629ad8ffe3caae396a0e679ae554.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.4.18
> 9e7353a042c2629ad8ffe3caae396a0e679ae554
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.4.18.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.4.18
> [ ] -1 Do not release this package because...
>
> D.
>

[ANNOUNCE] Apache Jackrabbit Oak 1.7.6 released

[Amit Jain]

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak 1.7.6. 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 -- Version 1.7.6

Introduction


Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

Apache Jackrabbit Oak 1.7.6 is an unstable release cut directly from
Jackrabbit Oak trunk, with a focus on new features and other
improvements. For production use we recommend the latest stable 1.6.x
release.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.7.6
-


Sub-task

[OAK-6445] - Ensure mounted node stores don't contain versionable nodes


Technical task

[OAK-6505] - Ensure mounted node stores don't contain referenceable
nodes
[OAK-6524] - Provide an extension point to customize the NodeStore
builders
[OAK-6546] - JsonSerializer should taken an instance of JsopWriter


Bug

[OAK-6372] - ListRecord cannot handle more than 16581375 entries
[OAK-6416] - Test failure: MapRecordTest.testOak1104
[OAK-6452] - IllegalStateException: too much data for a segment during
oak-upgrade from segment to segment-tar
[OAK-6500] - NRTIndex leaks file handles due to unclosed IndexReader
[OAK-6503] - Active deletion of blobs tries to delete sub-16k inlined
blobs in case of seg-tar
[OAK-6504] - Active deletion of blobs needs to indicate information
about purged blobs to mark-sweep collector
[OAK-6507] - Cleanup incorrectly removes base state created by full
compaction
[OAK-6527] - CompositeNodeStore permission evaluation fails for open
setups
[OAK-6529] - IndexLoaderV1 and IndexLoaderV2 should not rely on
Buffer.array()
[OAK-6541] - While importing new index property indexes are getting
marked for reindex
[OAK-6548] - Composite node builder/state keeps references to all the
ancestor states
[OAK-6567] - Fix OSGi wiring after netty update to 4.1.x


Improvement

[OAK-937] - Query engine index selection tweaks: shortcut and hint
[OAK-5902] - Cold standby should allow syncing of blobs bigger than 2.2
GB
[OAK-6407] -  Refactor oak.spi.query into a separate module/bundle
[OAK-6450] - Stop relying on the service.pid property in
SecurityProviderRegistration
[OAK-6497] - Support old Segment NodeStore setups for oak-run index
tooling
[OAK-6510] - Fix string representation of the old generation reclaimer
[OAK-6518] - Implement transparent usage of different TAR index formats
[OAK-6520] - Improve tail compactions resilience when base state cannot
be determined
[OAK-6523] - Tune DocumentNodeStore setup for indexing flow for index
command
[OAK-6525] - Index consistency checker should check all indexes even
after failure
[OAK-6526] - Slow queries: ability to track them via JMX
[OAK-6528] - Implement transparent usage of different binary references
index formats
[OAK-6530] - Expose last RGC result via Supplier
[OAK-6534] - Compute indexPaths from index definitions json
[OAK-6536] - Periodic log message from continuous RGC
[OAK-6537] - Don't encode the checksums in the TAR index tests
[OAK-6539] - Decrease version export for
org.apache.jackrabbit.oak.spi.security.authentication
[OAK-6540] - Session.hasAccess(...) should reflect read-only status of
mounts
[OAK-6543] - NodeCounter: JMX description
[OAK-6549] - Move gcType to SegmentGCOptions
[OAK-6552] - Dump index command should fallback to dumping NodeState
incase of error
[OAK-6556] - gc.log should contain recordId of compacted root after
offline compaction
[OAK-6558] - Remove the 'parent' field from the CompositeNodeBuilder
[OAK-6559] - Don't allow to place mounts under mounts
[OAK-6564] - Update netty dependency to 4.1.x
[OAK-6565] - GetBlobResponseEncoder should not write all chunks at once


New Feature

[OAK-3710] - Continuous revision GC
[OAK-6457] - Increment the segment version number
[OAK-6531] - Implement rolling upgrade from Oak 1.6
[OAK-6545] - Support for dumping repository content as json along with
blobs via oak-run
[OAK-6553] - Progress indicator for compaction


Task

[OAK-6399] - Re-establish full offline compaction functionality
[OAK-6449] - Stop using the maven-scr-plugin
[OAK-6498] - Update Oak trunk to Jackrabbit 2.15.5
[OAK-6511] - Switch to official OSGi versioning annotations
[OAK-6519] - Properly handle tail compactions in deduplication caches
[OAK-6522] - Implement unit tests for OnlineCompactor
[OAK-6532] - Minimise usage of junit-addons
[OAK-6533] - Adjust test classpath order to reduce number of error

[RESULT][VOTE] Release Apache Jackrabbit Oak 1.7.6

[Amit Jain]

Hi,

The vote passes as follows:

+1 Andrei Dulceanu
+1 Robert Munteanu
+1 Michael Dürig
+1 Tommaso Teofili
+1 Amit Jain

Thanks for voting. I'll push the release out.

Regards
Amit

Re: OAK-6575 - Provide a secure external URL to a DataStore binary.

[Amit Jain]

Hi,

+1 from my side for the broad contours as proposed above.

Thanks
Amit

On Thu, Aug 24, 2017 at 10:58 AM, Chetan Mehrotra  wrote:

> Based on the feedback so far below is revised proposal
>
> 1. Define a new Adaptable interface in 'org.apache.jackrabbit.oak.api'
>
> public interface Adaptable {
>
> /**
>  * Adapts the binary to another type
>  *
>  * @param  The generic type to which this type is adapted
>  *to
>  * @param type The Class object of the target type
>  * @return The adapter target or null if the type cannot
>  * adapt to the requested type
>  */
>  AdapterType adaptTo(Class type);
> }
>
> 2. Have the binary implementation in Oak implement Adaptable
> 3. Have a minimal implementation in Oak on line of Sling Adaptor support
> [1]
>
> For current usecase we would provide an adaptation to SignedBinary
>
> public interface SignedBinary {
>
> URI getUri()
> }
>
> Chetan Mehrotra
>
> [1] https://github.com/apache/sling/tree/trunk/bundles/api/
> src/main/java/org/apache/sling/api/adapter
>
>
> On Wed, Aug 23, 2017 at 10:04 PM, Chetan Mehrotra
>  wrote:
> >> Hence, why not simply use  binaryProp instanceof SignedBinary ?
> >
> > As Julian mentioned it would make it tricky to support multiple
> > extensions with various permutations. Having adapter support for
> > simplify the implementation
> >
> >> No client should be issued a signed url that could be used in the
> distant
> >> (relatively) future bypassing fresh ACL constraints saved to Oak.
> >
> > Fair point. Then lets drop the ttl paramater
> >
> > Chetan Mehrotra
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.7.6

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.7.6

Thanks
Amit

On Tue, Aug 22, 2017 at 12:22 PM, Amit Jain <am...@apache.org> wrote:

> A candidate for the Jackrabbit Oak 1.7.6 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.7.6/
>
> The release candidate is a zip archive of the sources in:
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/
> jackrabbit-oak-1.7.6/
>
> The SHA1 checksum of the archive is 700852d123bbb320932d20d2a4f359
> 202bd82ae5.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.7.6 700852d123bbb320932d20d2a4f359
> 202bd82ae5
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.7.6.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.7.6
> [ ] -1 Do not release this package because...
>
> Thanks
> Amit
>

[VOTE] Release Apache Jackrabbit Oak 1.7.6

[Amit Jain]

A candidate for the Jackrabbit Oak 1.7.6 release is available at:

https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.7.6/

The release candidate is a zip archive of the sources in:


https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.7.6/

The SHA1 checksum of the archive is
700852d123bbb320932d20d2a4f359202bd82ae5.

A staged Maven repository is available for review at:

https://repository.apache.org/

The command for running automated checks against this release candidate is:

$ sh check-release.sh oak 1.7.6 700852d123bbb320932d20d2a4f359202bd82ae5

Please vote on releasing this package as Apache Jackrabbit Oak 1.7.6.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.

[ ] +1 Release this package as Apache Jackrabbit Oak 1.7.6
[ ] -1 Do not release this package because...

Thanks
Amit

[ANNOUNCE] Apache Jackrabbit Oak 1.6.4 released

[Amit Jain]

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak 1.6.4. 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 -- Version 1.6.4

Introduction


Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

Jackrabbit Oak 1.6.4 is a patch release that contains fixes and
improvements over Oak 1.6. Jackrabbit Oak 1.6.x releases are
considered stable and targeted for production use.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.6.4
-


Bug

[OAK-6442] - Update Oak 1.6 to Jackrabbit 2.14.2
[OAK-6462] - Incorrect memory calculation for bundled node states
[OAK-6493] - LuceneIndexProviderService.enableHybridIndexing=false
results in NullPointerException
[OAK-6500] - NRTIndex leaks file handles due to unclosed IndexReader

Improvement

[OAK-5827] - Don't use SHA-1 for new DataStore binaries
[OAK-6333] - IndexPlanner should use actual entryCount instead of
limiting it to 1000
[OAK-6359] - Change behavior for very complex queries
[OAK-6464] - Public constructor for RandomStream
[OAK-6495] - Fallback to classic diff when journal is broken

In addition to the above-mentioned changes, this release contains
all changes included up to the Apache Jackrabbit Oak 1.6.x release.

For more detailed information about all the changes in this and other
Oak releases, please see the Oak issue tracker at

  https://issues.apache.org/jira/browse/OAK

Release Contents


This release consists of a single source archive packaged as a zip
file.
The archive can be unpacked with the jar tool from your JDK
installation.
See the README.md file for instructions on how to build this release.

The source archive is accompanied by SHA1 and MD5 checksums and a PGP
signature that you can use to verify the authenticity of your
download.
The public key used for the PGP signature can be found at
http://www.apache.org/dist/jackrabbit/KEYS.

About Apache Jackrabbit Oak
---

Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

For more information, visit http://jackrabbit.apache.org/oak

About The Apache Software Foundation


Established in 1999, The Apache Software Foundation provides
organizational,
legal, and financial support for more than 140 freely-available,
collaboratively-developed Open Source projects. The pragmatic Apache
License
enables individual and commercial users to easily deploy Apache
software;
the Foundation's intellectual property framework limits the legal
exposure
of its 3,800+ contributors.

For more information, visit http://www.apache.org/

[RESULT][VOTE] Release Apache Jackrabbit Oak 1.6.4

[Amit Jain]

Hi,

The vote passes as follows:

+1 Andrei Dulceanu
+1 Julian Reschke
+1 Robert Munteanu
+1 Thomas Mueller
+1 Amit Jain

Thanks for voting. I'll push the release out.

Regards
Amit

Re: Release plan Oak 1.7.6

[Amit Jain]

There are about 5 issues which are marked as 'In progress'. Please resolve
these issues appropriately if done. I am postponing the release further to
Monday 21st August.

Thanks
Amit

On Wed, Aug 16, 2017 at 9:02 AM, Amit Jain <am...@ieee.org> wrote:

> Hi,
>
> I plan to release Oak 1.7.6 tomorrow.
> I will move any unresolved issues to the next releases. Let me know if
> there's something urgent that you want to get in and need more time.
>
> Thanks
> Amit
>

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.39

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.0.39

Thanks
Amit

On Tue, Aug 15, 2017 at 11:55 PM, Manfred Baedke 
wrote:

> A candidate for the Jackrabbit Oak 1.0.39 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.0.39/
>
> The release candidate is a zip archive of the sources in:
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrab
> bit-oak-1.0.39/
>
> The SHA1 checksum of the archive is 5cfb85374d99c96f5528697255a0f5
> c626657032.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.0.39 5cfb85374d99c96f5528697255a0f5
> c626657032
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.0.39.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.0.39
> [ ] -1 Do not release this package because...
>
>

[VOTE] Release Apache Jackrabbit Oak 1.6.4

[Amit Jain]

A candidate for the Jackrabbit Oak 1.6.4 release is available at:

https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.6.4/

The release candidate is a zip archive of the sources in:


https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.6.4/

The SHA1 checksum of the archive is
93c5f0e3b93472d2bd22a36b69c42b479c191552.

A staged Maven repository is available for review at:

https://repository.apache.org/

The command for running automated checks against this release candidate is:

$ sh check-release.sh oak 1.6.4 93c5f0e3b93472d2bd22a36b69c42b479c191552

Please vote on releasing this package as Apache Jackrabbit Oak 1.6.4.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.

[ ] +1 Release this package as Apache Jackrabbit Oak 1.6.4
[ ] -1 Do not release this package because...

Release plan Oak 1.7.6

[Amit Jain]

Hi,

I plan to release Oak 1.7.6 tomorrow.
I will move any unresolved issues to the next releases. Let me know if
there's something urgent that you want to get in and need more time.

Thanks
Amit

[ANNOUNCE] Apache Jackrabbit Oak 1.2.27 released

[Amit Jain]

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak 1.2.26. The release is available for download at:

http://jackrabbit.apache.org/downloads.html

See the full release notes below for details about this released:

Release Notes -- Apache Jackrabbit Oak -- Version 1.2.27

Introduction


Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

Apache Jackrabbit Oak 1.2.27 is a patch release that contains fixes and
improvements over Oak 1.2. Jackrabbit Oak 1.2.x releases are considered
stable and targeted for production use.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.2.27
-


Bug

[OAK-3930] - Sysview import of single valued mv property creates sv
property
[OAK-4067] - AssertionError thrown for Lucene index with empty suggest
disctionary
[OAK-5949] - XPath: string literals parsed as identifiers
[OAK-6317] - LMSEstimator update amount depending on cost amount
[OAK-6391] - With FastQuerySize, getSize() returns -1 if there are
exactly 21 rows


In addition to the above-mentioned changes, this release contains
all changes included up to the Apache Jackrabbit Oak 1.2.26 release.

For more detailed information about all the changes in this and other
Oak releases, please see the Oak issue tracker at

  https://issues.apache.org/jira/browse/OAK

Release Contents


This release consists of a single source archive packaged as a zip file.
The archive can be unpacked with the jar tool from your JDK installation.
See the README.md file for instructions on how to build this release.

The source archive is accompanied by SHA1 and MD5 checksums and a PGP
signature that you can use to verify the authenticity of your download.
The public key used for the PGP signature can be found at
http://www.apache.org/dist/jackrabbit/KEYS.

About Apache Jackrabbit Oak
---

Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

For more information, visit http://jackrabbit.apache.org/oak

About The Apache Software Foundation


Established in 1999, The Apache Software Foundation provides organizational,
legal, and financial support for more than 140 freely-available,
collaboratively-developed Open Source projects. The pragmatic Apache License
enables individual and commercial users to easily deploy Apache software;
the Foundation's intellectual property framework limits the legal exposure
of its 3,800+ contributors.

For more information, visit http://www.apache.org/

[RESULT][VOTE] Release Apache Jackrabbit Oak 1.2.27

[Amit Jain]

Hi,

The vote passes as follows:

+1 Julian Reschke
+1 Davide Giannella
+1 Andrei Dulceanu
+1 Amit Jain

Thanks for voting. I'll push the release out.

Regards
Amit

Re: [VOTE] Release Apache Jackrabbit Oak 1.7.5

[Amit Jain]

+1 Release this package as Apache Jackrabbit Oak 1.7.5

Thanks
Amit

On Mon, Jul 31, 2017 at 7:13 PM, Davide Giannella  wrote:

>
>
> A candidate for the Jackrabbit Oak 1.7.5 release is available at:
>
> https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.7.5/
>
> The release candidate is a zip archive of the sources in:
>
>
> https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.7.5/
>
> The SHA1 checksum of the archive is
> bb58dbad3679df71c539ba4f837de5336aa29abb.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/
>
> The command for running automated checks against this release candidate is:
>
> $ sh check-release.sh oak 1.7.5 bb58dbad3679df71c539ba4f837de5
> 336aa29abb
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.7.5.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.7.5
> [ ] -1 Do not release this package because...
>
> D.
>