Re: [VOTE] Release Apache Jackrabbit 2.14.1

2017-05-30 Thread Chetan Mehrotra
+1 Chetan Mehrotra On Tue, May 30, 2017 at 2:21 PM, KÖLL Claus wrote: > +1 > > greets > claus

AW: [VOTE] Release Apache Jackrabbit 2.14.1

2017-05-30 Thread KÖLL Claus
+1 greets claus

[ANNOUNCE] Apache Jackrabbit Oak 1.7.0 released

2017-05-30 Thread Davide Giannella
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 --

Re: [VOTE] Release Apache Jackrabbit 2.14.1

2017-05-30 Thread Tomek Rękawek
Hi Julian, > On 29 May 2017, at 11:37, Julian Reschke wrote: >[ ] +1 Release this package as Apache Jackrabbit 2.14.1 +1 Regards, Tomek -- Tomek Rękawek | Adobe Research | www.adobe.com reka...@adobe.com smime.p7s Description: S/MIME cryptographic signature

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers

2017-05-30 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Fix Version/s: 2.16 > TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers >

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers

2017-05-30 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Summary: TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers (was:

Re: codahale metrics Jmx reporter

2017-05-30 Thread Andrei Kalfas
Hi, Exposing the metrics registry is about exposing the data, while exposing the reporter would be exposing behavior. Doing so, the encouraged pattern here is that you get to tap into the metrics and pick whatever you like. I thought that oak-core is the best position to say what metrics are

Re: svn commit: r1796624 - /jackrabbit/oak/trunk/oak-store-spi/src/main/java/org/apache/jackrabbit/oak/spi/state/AbstractNodeState.java

2017-05-30 Thread Michael Dürig
On 30.05.17 07:00, Chetan Mehrotra wrote: On Mon, May 29, 2017 at 6:50 PM, wrote: +private static final int CHILDREN_CAP = getInteger("children.cap", 100); Better to have system property prefix with 'oak' i.e. 'oak.children.cap' Agreed. Done at

[RESULT][VOTE] Release Apache Jackrabbit Oak 1.7.0

2017-05-30 Thread Davide Giannella
Hello Team, the vote passes as follows: +1 Davide Giannella +1 Alex Parvulescu +1 Michael Dürig Thanks for voting. I'll push the release out. -- Davide

Re: copy on write node store

2017-05-30 Thread Michael Dürig
Hi Tomek, AFAIU from your mail and from looking at the patch this is about a node store implementation that can be rolled back to a previous state. If this is the case, a simpler way to achieve this might be to use the TarMK and and add functionality for rolling it back. The cleanest way

Re: copy on write node store

2017-05-30 Thread Tomek Rekawek
Hello Michael, thanks for the reply! > On 30 May 2017, at 09:18, Michael Dürig wrote: > AFAIU from your mail and from looking at the patch this is about a node store > implementation that can be rolled back to a previous state. > > If this is the case, a simpler way to

Re: codahale metrics Jmx reporter

2017-05-30 Thread Chetan Mehrotra
On Tue, May 30, 2017 at 11:30 AM, Andrei Kalfas wrote: > I thought that oak-core is the best position to say what metrics are needed, > and the way that we want to extend the behavior is by picking whatever > reporter we say fits the environment - this is why I

Re: codahale metrics Jmx reporter

2017-05-30 Thread Chetan Mehrotra
On Tue, May 30, 2017 at 11:53 AM, Andrei Kalfas wrote: > Looks to me that there is a dependency on oak functionality. Ian can confirm but I believe thats not required now (the component does not get activated) and was only a temporary workaround. Oak publishes the

BUILD FAILURE: Jackrabbit Oak - Build # 355 - Failure

2017-05-30 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit Oak (build #355) Status: Failure Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/355/ to view the results. Changes: [mduerig] OAK-6272: AbstractNodeState.toString does not scale to many child nodes Prefix system

[ANNOUNCE] Apache Jackrabbit Oak 1.7.0 released

2017-05-30 Thread Davide Giannella
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 --

Re: codahale metrics Jmx reporter

2017-05-30 Thread Andrei Kalfas
https://github.com/ieb/statsd-reporter-osgi/blob/master/src/main/java/org/apache/sling/statsd/OakStatisticsProviderShim.java#L24 Looks to me that there is a

Re: copy on write node store

2017-05-30 Thread Julian Sedding
Slightly off topic: the thought that the copy on read/write indexing features may need to be explicitly managed in such a setup just occurred to me. I.e. when an instance is switched to the copy on write node store, the local index directory will deviate from the "mainline" node store. Upon

Re: copy on write node store

2017-05-30 Thread Michael Dürig
On 30.05.17 09:34, Tomek Rekawek wrote: Hello Michael, thanks for the reply! On 30 May 2017, at 09:18, Michael Dürig wrote: AFAIU from your mail and from looking at the patch this is about a node store implementation that can be rolled back to a previous state. If

Re: failure building oak-upgrade

2017-05-30 Thread Angela Schreiber
hi tomek confirming that the issue is gone. thanks a lot angela On 29/05/17 20:45, "Tomek Rekawek" wrote: >Hi, > >regression fixed, sorry for that. > >Regards, >Tomek > >-- >Tomek Rękawek | Adobe Research | www.adobe.com >reka...@adobe.com > >> On 29 May 2017, at

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

2017-05-30 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit Oak (build #356) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/356/ to view the results. Changes: [rombert] OAK-6196 - Improve Javadoc of multiplexing SPI Expand the Javadoc for Mount.isMounted

Re: [discuss] expose way to detect "eventual consistency delay"

2017-05-30 Thread Stefan Egli
On 30/05/17 14:51, "Stefan Egli" wrote: >on how Oak could "expose a way to detect the eventual delay". ... "to detect the eventual consistency delay" ... of course ...

[discuss] expose way to detect "eventual consistency delay"

2017-05-30 Thread Stefan Egli
Hi all, I'd like to invite those interested to join a discussion in https://issues.apache.org/jira/browse/OAK-6276 on how Oak could "expose a way to detect the eventual delay". This is a requirement coming from the integration with an external messaging system in an Oak-based application. One

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

2017-05-30 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit Oak (build #357) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/357/ to view the results. Changes: [angela] OAK-6277 : UserQueryManager: redundant check for colliding bound and offset OAK-6278