Re: [VOTE] Release Apache Jackrabbit Oak 1.0.26

On 2016-01-19 11:49, Dominique Jaeggi wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.0.26 Best regards, Julian

Re: [VOTE] Release Apache Jackrabbit Oak 1.3.14

On 2016-01-18 17:15, Davide Giannella wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.3.14 Best regards, Julian

Re: [DISCUSS] avoid bad commits with mis-behaving clock

On 2016-01-14 17:36, Vikas Saurabh wrote: Opened OAK-3883 for this. Have added following: * We can start self-destrucut mode while updating lease * Revision creation should check that newly created revision isn't beyond leaseEnd time * Implementation done for OAK-2682 might be useful to

Re: svn commit: r1724598 - in /jackrabbit/oak/trunk/oak-core/src: main/java/org/apache/jackrabbit/oak/api/ main/java/org/apache/jackrabbit/oak/plugins/document/rdb/ main/java/org/apache/jackrabbit/oak

On 2016-01-14 14:13, Chetan Mehrotra wrote: On Thu, Jan 14, 2016 at 6:40 PM, wrote: jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/api/Blob.java

Re: svn commit: r1724598 - in /jackrabbit/oak/trunk/oak-core/src: main/java/org/apache/jackrabbit/oak/api/ main/java/org/apache/jackrabbit/oak/plugins/document/rdb/ main/java/org/apache/jackrabbit/oak

On 2016-01-14 14:13, Chetan Mehrotra wrote: On Thu, Jan 14, 2016 at 6:40 PM, wrote: jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/api/Blob.java

Re: [DISCUSS] avoid bad commits with mis-behaving clock

On 2016-01-14 01:26, Vikas Saurabh wrote: ... Note that in trunk, we also have mechanism to detect misbehaving system clocks; see . Best regards, Julian

Re: Slow tests

On 2016-01-11 11:56, Francesco Mari wrote: Hi all, I opened OAK-3858 to discuss about some slow running tests. I would like to raise awareness to the whole team, since I don't have enough background in every subsystem to evaluate if a test is slow because of a potential bug, if it should be

Re: [VOTE] Release Apache Jackrabbit Oak 1.3.13

On 2016-01-04 14:36, Davide Giannella wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.3.13 Best regards, Julian

Re: DocumentRDB builds time out on Jenkins

On 2015-12-11 16:07, Michael Dürig wrote: ... And build 611 () is going to timeout again (this time for the RDBMK JDK 1.7 integration tests). No it didn't:

Re: DocumentRDB builds time out on Jenkins

On 2015-12-10 15:58, Julian Reschke wrote: On 2015-12-10 15:22, Marcel Reutegger wrote: Hi, hmm, this could be similar to https://issues.apache.org/jira/browse/OAK-2704 I had a closer look at the DOCUMENT_RDB fixture and I think the problem is with the createNodeStore() method. The method

Re: DocumentRDB builds time out on Jenkins

On 2015-12-10 14:57, Tomek Rekawek wrote: Hi, I spent some time analysing the logs and I found out a strange thing. On a “slow” machine, in the surefire logs for the AtomicCounterTest (which takes 63 sec while it should 3 sec), following test case appears [1]: It’s a test case from a

Re: DocumentRDB builds time out on Jenkins

On 2015-12-10 15:22, Marcel Reutegger wrote: Hi, hmm, this could be similar to https://issues.apache.org/jira/browse/OAK-2704 I had a closer look at the DOCUMENT_RDB fixture and I think the problem is with the createNodeStore() method. The method is supposed to create independent node store

Re: fixVersions in jira

On 2015-12-09 10:33, Davide Giannella wrote: On 08/12/2015 16:06, Julian Reschke wrote: So what's the correct JIRA state for something that has been fixed in 1.3.x, which is intended to be backported to 1.2, but hasn't been backported yet? Can I still set that to "resolved"? If th

Re: DocumentRDB builds time out on Jenkins

On 2015-12-09 09:42, Michael Dürig wrote: Hi, In the last 5 build on our Jenkins instance [1] we always had one of the DocumentRDB jobs timing out [2]. This means the job didn't complete within 90 minutes. This is not because we are close to the limit as regular builds take roughly 30 minutes.

Re: DocumentRDB builds time out on Jenkins

On 2015-12-09 12:02, Michael Dürig wrote: On 9.12.15 11:58 , Julian Reschke wrote: On 2015-12-09 09:42, Michael Dürig wrote: Hi, In the last 5 build on our Jenkins instance [1] we always had one of the DocumentRDB jobs timing out [2]. This means the job didn't complete within 90 minutes

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.25

On 2015-12-08 06:13, Amit Jain wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.0.25 Best regards, Julian

Re: [VOTE] Release Apache Jackrabbit Oak 1.2.9

On 2015-12-08 15:04, Davide Giannella wrote: > ... [X] +1 Release this package as Apache Jackrabbit Oak 1.2.9 Best regards, Julian

Re: [VOTE] Shut down oakcomm...@jackrabbit.apache.org mailing list

On 2015-12-08 17:51, Michael Dürig wrote: ... [X] +1, shut down oakcomm...@jackrabbit.apache.org Best regards, Julian

Re: [VOTE] Release Apache Jackrabbit Oak 1.3.12

On 2015-12-07 17:17, Davide Giannella wrote: ... [+] +1 Release this package as Apache Jackrabbit Oak 1.3.12 Best regards, Julian

Re: [VOTE] Release Apache Jackrabbit Oak 1.3.11

On 2015-11-23 07:36, Amit Jain wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.3.11 Best regards, Julian

Re: [VOTE] Release Apache Jackrabbit Oak 1.2.8

On 2015-11-17 07:43, Chetan Mehrotra wrote: After rerunning the build with -PintegrationTesting,unittesting the build failed with 2 test failures on RDB [1] ... Are these reproducible with Derby? (-Dnsfixtures=DOCUMENT_RDB -Prdb-derby -Drdb.jdbc-url=jdbc:derby:foo\;create=true) Best regards,

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.24

On 2015-11-16 16:57, Davide Giannella wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.0.24 Best regards, Julian

Re: [VOTE] Release Apache Jackrabbit Oak 1.2.8

On 2015-11-16 17:43, Davide Giannella wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.2.8 Best regards, Julian

Re: [VOTE] Release Apache Jackrabbit Oak 1.3.10

On 2015-11-09 11:50, Davide Giannella wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.3.10 Best regards, Julian

Re: v1.3.9 - http state of play?

On 2015-11-09 01:55, Jason Harrop wrote: Hi guys, I have a standalone server running: java -jar oak-run-1.3.9.jar server What's the current state of play for talking to it via http? My objective is to add a binary file via http. Various things I tried: 1. oak-http: the examples in the

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.23

On 2015-10-28 10:59, Davide Giannella wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.0.23 Best regards, Julian

Re: [VOTE] Release Apache Jackrabbit Oak 1.3.9

On 2015-10-27 13:19, Davide Giannella wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.3.9 Best regards, Julian

Re: Why does oak-core import every package with an optional resolution?

On 2015-10-26 12:13, Chetan Mehrotra wrote: Looking at history of oak-core/pom.xml this change was done in [1] for OAK-1708 most like to support loading of various DB drivers from within Oak Core and probably a temp change which was not looked back again. That might not be required now as the

Re: Why does oak-core import every package with an optional resolution?

On 2015-10-26 16:37, Francesco Mari wrote: 2015-10-26 13:15 GMT+01:00 Julian Reschke <julian.resc...@gmx.de>: On 2015-10-26 12:13, Chetan Mehrotra wrote: Looking at history of oak-core/pom.xml this change was done in [1] for OAK-1708 most like to support loading of various DB driver

Re: [VOTE] Release Apache Jackrabbit Oak 1.2.7

On 2015-10-06 15:10, Davide Giannella wrote: On 06/10/2015 13:09, Julian Reschke wrote: On 2015-10-06 14:02, Julian Reschke wrote: On 2015-10-06 12:26, Davide Giannella wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.2.7 Best regards, Julian But wait... At least on my

Re: multiple releases at the same time

On 2015-10-06 13:15, Davide Giannella wrote: Good morning everyone, it happened I had to perform 2 oak releases in the same day which ended up in not being able as it's quite a long process to run all the UTs/ITs and all the release steps and uploads. I was therefore thinking about staring the

Re: [VOTE] Release Apache Jackrabbit Oak 1.2.7

On 2015-10-06 14:35, Marcel Reutegger wrote: On 06/10/15 14:09, "Julian Reschke" wrote: On 2015-10-06 14:02, Julian Reschke wrote: On 2015-10-06 12:26, Davide Giannella wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.2.7 Best regards, Julian But wait... At l

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.22

On 2015-10-05 10:23, Davide Giannella wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.0.22

Re: Drop/keep support for Java6

On 2015-10-05 12:08, Michael Dürig wrote: Hi, I was wondering whether we should/could/want to drop support for Java 6 in Oak. If we keep supporting it, what would be a realistic time line? I assume this is about "trunk", not 1.2 or 1.0, right? As much as I'd love to drop it, given the

Re: jackrabbit-oak build #6541: Broken

On 2015-09-30 14:23, Marcel Reutegger wrote: The failure is: Running org.apache.jackrabbit.oak.plugins.document.mongo.ReadPreferenceIT Tests run: 8, Failures: 0, Errors: 8, Skipped: 0, Time elapsed: 0.982 sec <<< FAILURE!

Re: jackrabbit-oak build #6541: Broken

On 2015-09-30 14:36, Julian Reschke wrote: On 2015-09-30 14:23, Marcel Reutegger wrote: The failure is: Running org.apache.jackrabbit.oak.plugins.document.mongo.ReadPreferenceIT Tests run: 8, Failures: 0, Errors: 8, Skipped: 0, Time elapsed: 0.982 sec <<< FAILURE! testPreferenceC

Re: [VOTE] Release Apache Jackrabbit Oak 1.3.7

On 2015-09-28 03:20, Amit Jain wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.3.7 Best regards, Julian

Re: Builds timing out on Jenkins

On 2015-09-23 17:49, Michael Dürig wrote: Hi, I started seeing builds timing out (after 90mins) on Jenkins [1]. So far I think this affected the DOCUMENT_RDB fixture only. Julian, how long should such builds take? As I also have seen OOME in this area, might we run under memory pressure?

Re: issues ClusterNodeInfo (not) picking an existing entry on startup

On 2015-09-21 10:41, Marcel Reutegger wrote: Hi, On 17/09/15 18:48, "Julian Reschke" wrote: With the current assignment very weird things can happen, and I believe I see exactly this happening in a customer problem I'm investigating. The sequence is: 1) First system startup, cluster

Re: issues ClusterNodeInfo (not) picking an existing entry on startup

On 2015-09-21 10:41, Marcel Reutegger wrote: Hi, On 17/09/15 18:48, "Julian Reschke" wrote: With the current assignment very weird things can happen, and I believe I see exactly this happening in a customer problem I'm investigating. The sequence is: 1) First system startup, cluster

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.21

On 2015-09-17 11:09, Marcel Reutegger wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.0.21 Best regards, Julian

Re: [VOTE] Release Apache Jackrabbit Oak 1.2.6

On 2015-09-17 11:42, Marcel Reutegger wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.2.6 Best regards, Julian

issues ClusterNodeInfo (not) picking an existing entry on startup

Hi there, when the DocumentNodeStore starts up, it attempts to find an entry that matches the current instance (which is defined by something based on network interface address and the current working directory). However, an additional check is done when the cluster lease end time hasn't

Re: JCR node name and non space whitespace chars like line break etc

On 2015-09-15 10:03, Chetan Mehrotra wrote: If I change the code in Namespace#isValidLocalName to use Character#isWhitespace then NameValidator starts objecting to node names having non space whitespace chars. So looks like current impl has a issue and we should fix it. But fixing it would be

Re: Oak 1.3.6 release plan

On 2015-09-14 10:17, Julian Reschke wrote: On 2015-09-14 10:03, Stefan Egli wrote: On 14/09/15 09:51, "Marcel Reutegger" <mreut...@adobe.com> wrote: ...would it make sense to just disable the lease check for the diagnostics in oak-run? ... +1 as a short-term fix Cheers,

Re: Oak 1.3.6 release plan

On 2015-09-14 09:17, Marcel Reutegger wrote: Hi, are things really broken because of the LeaseCheckDocumentWrapper? AFAIU it means the DocumentNodeStore will currently fall back to a generic implementation for getReferencedBlobsIterator(), which works but may be less efficient than the Mongo

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.20

On 2015-09-14 06:49, Amit Jain wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.0.20 Best regards, Julian

Re: Oak 1.3.6 release plan

On 2015-09-14 10:03, Stefan Egli wrote: On 14/09/15 09:51, "Marcel Reutegger" wrote: ...would it make sense to just disable the lease check for the diagnostics in oak-run? ... +1 as a short-term fix Cheers, Stefan I agree that this would have been broken by the other

Re: Oak 1.3.6 release plan

On 2015-09-10 09:19, Marcel Reutegger wrote: Hi, I plan to release 1.3.6 on Monday. And this time I really hope I will have the time to actually perform the release. Thanks Amit for taking care of the previous 1.3.5 release! ... Given the amount of breakage we currently have because of

Re: JCR TCK tests on DOCUMENT_RDB

On 2015-09-09 17:59, Julian Reschke wrote: On 2015-09-09 17:49, Michael Dürig wrote: On 9.9.15 3:55 , Julian Reschke wrote: On 2015-09-09 15:27, Michael Dürig wrote: On 8.9.15 2:49 , Julian Reschke wrote: We'd need -Dnsfixtures=DOCUMENT_RDB -Prdb-derby -Drdb.jdbc-url=jdbc:derby:foo

Re: JCR TCK tests on DOCUMENT_RDB

On 2015-09-09 15:27, Michael Dürig wrote: On 8.9.15 2:49 , Julian Reschke wrote: We'd need -Dnsfixtures=DOCUMENT_RDB -Prdb-derby -Drdb.jdbc-url=jdbc:derby:foo\;create=true You should be able to login to that Jenkins instance and edit its configuration using your ASF U/P. Michael OK

Re: JCR TCK tests on DOCUMENT_RDB

On 2015-09-09 17:49, Michael Dürig wrote: On 9.9.15 3:55 , Julian Reschke wrote: On 2015-09-09 15:27, Michael Dürig wrote: On 8.9.15 2:49 , Julian Reschke wrote: We'd need -Dnsfixtures=DOCUMENT_RDB -Prdb-derby -Drdb.jdbc-url=jdbc:derby:foo\;create=true You should be able to login

Re: JCR TCK tests on DOCUMENT_RDB

On 2015-09-08 09:35, Marcel Reutegger wrote: Hi, JCR TCK tests currently do not run on Jenkins with the DOCUMENT_RDB fixture. IIUC the tests do not run because no system property 'rdb.jdbc-url' is set. Why is the default empty and needs to be enabled explicitly? Wouldn't it be better for test

Re: JCR TCK tests on DOCUMENT_RDB

On 2015-09-08 12:14, Michael Dürig wrote: On 8.9.15 11:43 , Julian Reschke wrote: PS: we still should change the Jenkins tests to use Derby instead of H2; does anybody know how to? I would know how to change configurations on Jenkins but nothing about those tests. Is that what you

Re: oak-run upgrade improvements

On 2015-09-03 09:14, Robert Munteanu wrote: On Wed, 2015-09-02 at 18:35 +, Tomek Rekawek wrote: Hi, One more thing. The “upgrade" command requires a lot of Maven dependencies (Amazon API client for the S3 support, Jackrabbit 2 for the repository upgrades, etc.) Some of these dependencies

code cleanup vs backports

Hi there, I recently had to backport stuff, and it turned out to be harder than it should have been. This was caused by code cleanup changes that weren't backported and thus caused merge conflicts. Now code cleanup is a good thing, and it needs to be done, for performance, robustness,

Re: [VOTE] Release Apache Jackrabbit Oak 1.3.5

On 2015-09-01 15:30, Davide Giannella wrote: ... [ ] +1 Release this package as Apache Jackrabbit Oak 1.3.5 [ ] -1 Do not release this package because... ... [X] +1 Release this package as Apache Jackrabbit Oak 1.3.5

Re: Multiple DocumentNodeStores sharing a single DocumentStore

On 2015-08-28 14:01, Robert Munteanu wrote: Hi, I'm looking at LastRevRecoveryAgentTest [1] which uses a shared document store for two DocumentNodeStore instances. Disposing both node store instances makes the tests fail, as the document store will be closed by the first call to dispose() and

Re: Using of final for variables and parameters

On 2015-08-28 08:36, Thomas Mueller wrote: Hi, I wonder what does the team think about using final for variables and parameters. In Oak, so far we didn't use it a lot. This question has come up with OAK-3148. The patch uses final for variables, but not for parameters. Lately, I have seens

Re: [VOTE] Release Apache Jackrabbit Oak 1.2.4

On 2015-08-24 08:09, Amit Jain wrote: ... Please vote on releasing this package as Apache Jackrabbit Oak 1.2.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.2.4

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.19

On 2015-08-21 13:54, Davide Giannella wrote: ... Please vote on releasing this package as Apache Jackrabbit Oak 1.0.19. 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

Re: Is the hashing of long paths still needed?

On 2015-08-21 12:17, Bertrand Delacretaz wrote: On Fri, Aug 21, 2015 at 12:11 PM, Julian Reschke julian.resc...@greenbytes.de wrote: ...It is still needed, as both persistence implementations (Mongo, RDB) are restricted to IDs of 512 bytes length (yes, bytes, not characters) Ok, thanks

Re: Is the hashing of long paths still needed?

On 2015-08-21 11:57, Bertrand Delacretaz wrote: Hi, Continuing to play with Robert's MultiplexingDocumentStore [1] I got a failure in the oak-jcr module's LongPathTest. That's due to the conversion of long paths to their hashed variants - those cannot be used to locate the appropriate

System.exit()???? , was: svn commit: r1696202 - in /jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/document: ClusterNodeInfo.java DocumentMK.java DocumentNodeStore.java

On 2015-08-17 09:47, stefane...@apache.org wrote: Author: stefanegli Date: Mon Aug 17 07:47:15 2015 New Revision: 1696202 URL: http://svn.apache.org/r1696202 Log: OAK-2739 : lease check introduced : by default there's now a check active which assures the local lease is valid upon every action

Re: System.exit()???? , was: svn commit: r1696202 - in /jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/document: ClusterNodeInfo.java DocumentMK.java DocumentNodeStore.j

On 2015-08-18 11:14, Stefan Egli wrote: On 18/08/15 10:57, Julian Reschke wrote: ... Hi Julian, The idea is indeed that if an instance fails to update the lease then it will be considered by other instances in the cluster as dead/crashed - even though it still continues to function

Re: slow and failing builds

On 2015-08-17 15:53, Davide Giannella wrote: On 17/08/2015 15:38, Julian Reschke wrote: Speaking of which: for DOCUMENT_RDB, I'd like to switch from H2DB to Derby, which will require setting a new system properties for the tests. Who's able to modify the settings for Jenkins? Now I should

Re: slow and failing builds

On 2015-08-17 15:17, Michael Dürig wrote: On 17.8.15 1:45 , Davide Giannella wrote: https://issues.apache.org/jira/browse/OAK-2714 but I honestly lost track on what are we actually doing to address the failing tests. I try to keep track of the failing tests and update the table in that

Re: DocumentStorePerformanceTest executed during unit tests

On 2015-08-11 09:02, Davide Giannella wrote: On 10/08/2015 18:47, Julian Reschke wrote: On 2015-08-10 17:17, Francesco Mari wrote: Hi all, I noticed that DocumentStorePerformanceTest is executed during the test phase of Oak Core. It runs for a relatively long time compared to the unit tests

Re: svn commit: r1695297 [1/3] - in /jackrabbit/oak/branches/1.0: ./ oak-commons/src/main/java/org/apache/jackrabbit/oak/commons/sort/ oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/document

On 2015-08-11 14:55, mreut...@apache.org wrote: Author: mreutegg Date: Tue Aug 11 12:55:41 2015 New Revision: 1695297 URL: http://svn.apache.org/r1695297 Log: OAK-2829: Comparing node states for external changes is too slow OAK-3002: Optimize docCache and docChildrenCache invalidation by

Re: DocumentStorePerformanceTest executed during unit tests

On 2015-08-10 17:17, Francesco Mari wrote: Hi all, I noticed that DocumentStorePerformanceTest is executed during the test phase of Oak Core. It runs for a relatively long time compared to the unit tests (50 seconds on my machine), and I think that it should be executed with the integration

Re: jackrabbit-oak build #6116: Broken

On 2015-08-04 16:49, Angela Schreiber wrote: changes made with OAK-3170 require the API extensions in jackrabbit-api made with revision 1694048. i therefore expect that build to pass as soon as it picks that rev. br angela I have the same problem locally, despite having updated and built

Re: jackrabbit-oak build #6116: Broken

On 2015-08-04 17:27, Angela Schreiber wrote: hm... according to the jackrabbit log r1694048 (JCR-3880) was before r1694063 (JCR-3896 - Release Jackrabbit 2.10.2) but oak trunk is still on 2.10.2-SNAPSHOT (and not yet on 2.10.2) not sure if setting to 2.10.3-SNAPSHOT was really needed. kind

Re: jackrabbit-oak build #6116: Broken

On 2015-08-04 17:04, Julian Reschke wrote: On 2015-08-04 16:49, Angela Schreiber wrote: changes made with OAK-3170 require the API extensions in jackrabbit-api made with revision 1694048. i therefore expect that build to pass as soon as it picks that rev. br angela I have the same problem

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.18

On 2015-07-31 14:42, Chetan Mehrotra wrote: On Fri, Jul 31, 2015 at 5:39 PM, Julian Reschke julian.resc...@greenbytes.de wrote: Tests run: 9, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.595 sec FAILURE! copyOnWriteAndLocks

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.18

On 2015-07-31 11:01, Amit Jain wrote: A candidate for the Jackrabbit Oak 1.0.18 release is available at: https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.0.18/ The release candidate is a zip archive of the sources in: ... Apart from the well-known test failures in ClockTest, I

Re: svn commit: r1690941 - in /jackrabbit/oak/trunk/oak-core/src: main/java/org/apache/jackrabbit/oak/plugins/document/rdb/ test/java/org/apache/jackrabbit/oak/plugins/document/

On 2015-07-15 05:10, Chetan Mehrotra wrote: Hi Julian, On Tue, Jul 14, 2015 at 7:57 PM, resc...@apache.org wrote: + +ListString ids = new ArrayListString(); +for (T doc : documents) { +ids.add(doc.getId()); +} +LOG.debug(insert

Re: RDBDocumentStore using same table schema for all collections

On 2015-07-09 09:54, Chetan Mehrotra wrote: Hi, Looking at RDBDocumentStore it appears that it is using same table schema for all collections. For e.g. columns like deletedOnce, hasBinary are only required for NodeDocument. However they are present in the tables Yes. Any specific reason for

Re: RDBDocumentStore using same table schema for all collections

On 2015-07-13 12:54, Chetan Mehrotra wrote: On Mon, Jul 13, 2015 at 3:53 PM, Julian Reschke julian.resc...@gmx.de wrote: Simplicity and the complete lack of contract. How would the DS implementation *know* what needs to be indexed? Then we should define the contract. What needs to be indexed

Re: /oak:index (DocumentNodeStore)

On 2015-07-09 09:15, Marcel Reutegger wrote: Hi Ian, there are mainly two reasons why we cannot use DocumentStore based indexes for this purpose: - MongoDB only supports a limited number of indexes (64 per collection) and applications usually have a need for more indexes. - Data in Oak

Re: [VOTE] Release Apache Jackrabbit Oak 1.3.1

On 2015-06-22 15:20, Davide Giannella wrote: ... Please vote on releasing this package as Apache Jackrabbit Oak 1.3.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

Re: 1.3.1 cut

On 2015-06-18 11:27, Davide Giannella wrote: Good morning Team, next monday around 10AM I will be cutting 1.3.1 as by plan. We still have 137 unresolved issues. Please take a look at them and act accordingly. In case I will bulk move them to 1.3.2 if not resolved. In case you need more time

trunk build is failing due baseline plugin complaining

(see subject -- what's going on here???)

Re: trunk build is failing due baseline plugin complaining

On 2015-06-16 15:52, Julian Reschke wrote: (see subject -- what's going on here???) ...: [ERROR] org.apache.jackrabbit.oak.plugins.segment: Version increase required; detected 2.0.0, suggested 3.0.0 [ERROR] org.apache.jackrabbit.oak.spi.security.user.action: Version increase required

Re: Semantics of the document key at the DocumentStore level

On 2015-06-15 17:11, Robert Munteanu wrote: On Wed, 2015-06-10 at 10:13 +, Marcel Reutegger wrote: maybe CachingDocumentStore is misleading and we would rather name it HierarchicalDocumentStore, which also implements caching and leverage hierarchical information for invalidation as needed.

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.15

On 2015-06-12 10:26, Amit Jain wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.0.15

Re: [VOTE] Release Apache Jackrabbit Oak 1.3.0

On 2015-06-08 12:36, Davide Giannella wrote: ... Please vote on releasing this package as Apache Jackrabbit Oak 1.3.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

Re: Updating 1.0 and 1.2 to JR 2.10.1

On 2015-06-04 12:08, Davide Giannella wrote: Hello team, anyone against updating our 1.0 and 1.2 branches to use Jacrabbit 2.10.1? Cheers Davide No, please go ahead!

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.14

On 2015-05-13 11:45, Julian Reschke wrote: ... I haven't been able to have a success run, due to intermittent failures due to our much loved ClckDriftTest problem (Windows), and also observation-related failures (timing). That being said: none of these problems are new, so I'm ok with proceeding

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.14

On 2015-05-12 18:24, Davide Giannella wrote: A candidate for the Jackrabbit Oak 1.0.14 release is available at: https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.0.14/ The release candidate is a zip archive of the sources in:

RDB test failures, was: Build failed in Jenkins: Apache Jackrabbit Oak matrix » latest1.7,Ubuntu,DOCUMENT_RDB,unittesting #120

Hi there, I've been trying to understand this issue for quite some time now, but do not understand it yet. It does happen on my test machine as well, however I really need lots of test runs. Adding more and more debug information has led me to the conclusion that it might indeed be the

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.13

[X] +1 Release this package as Apache Jackrabbit Oak 1.0.13

Re: [VOTE] Release Apache Jackrabbit Oak 1.2.1

[X] +1 Release this package as Apache Jackrabbit Oak 1.2.1

Re: Unnecessary itemExists overhead in JcrResourceProvider.createResource

On 2015-04-08 10:10, Felix Meschberger wrote: Hi Joel Thanks for pointing out. Yet, this has been discussed before. Turns out that checking for item existence before accessing the item is JCR API best practice. So Sling follows best practice. Why would it be best practice? You need to

Re: Jackrabbit Oak 1.2 release plan

On 2015-04-07 14:30, Marcel Reutegger wrote: Hi all, ... - OAK-2704: ConcurrentAddIT occasionally fail with OakMerge0001 Julian R., did you have a chance to look into this? Could this be related to running multiple tests in parallel? ConcurrentAddIT extends from AbstractRepositoryTest, which

Re: Yourkit profiler open source license

On 2015-03-23 13:41, Michael Dürig wrote: Hi, The YourKit profiler license is free of charge for non-commercial open source projects: The license is granted to developers of non-commercial Open Source projects, with an established and active community. The license is free. However, we ask you

Re: ClockDrift test failures on Windows (OAK-1904)

On 2015-03-20 01:48, Alexander Klimetschek wrote: AFAIK, this is expected, on Windows (or some Windows versions), System.currentTimeMillis() only has a resolution of 15ms http://stackoverflow.com/questions/7859019/system-currenttimemillis-is-not-accurate-on-windows-xp Cheers, Alex That's

Re: ClockDrift test failures on Windows (OAK-1904)

On 2015-03-20 10:20, Davide Giannella wrote: On 20/03/2015 07:36, Julian Reschke wrote: On 2015-03-20 01:48, Alexander Klimetschek wrote: AFAIK, this is expected, on Windows (or some Windows versions), System.currentTimeMillis() only has a resolution of 15ms http://stackoverflow.com/questions

Re: ClockDrift test failures on Windows (OAK-1904)

On 2015-03-20 11:04, Michael Dürig wrote: On 19.3.15 5:11 , Julian Reschke wrote: - As far as I can tell, the reason why we even have Clock.Fast is the assumption that Clock.SIMPLE (== System.currentTimeMillis()) may be slow. Does anybody know what exactly is the problem? (Because, after all

ClockDrift test failures on Windows (OAK-1904)

So, as they plague the new Jenkins build and they also occur sometimes over here, I spent some time with them... 1) There was a single test for all of the clocks (simple, accurate, fast); I have refactored these so that they execute separately. 2) Most of the failures seem to be related to

Re: svn commit: r1666220 - in /jackrabbit/oak/trunk: oak-commons/ oak-commons/src/main/java/org/apache/jackrabbit/oak/commons/sort/ oak-commons/src/test/java/org/apache/jackrabbit/oak/commons/sort/ oa

With this change, I get a reliable test failure on Windows: Tests in error: overflowToDisk(org.apache.jackrabbit.oak.commons.sort.StringSortTest): Unable to delete file: C:\tmp\oak-sorter-1426178913437-0\strings-sorted.txt Best regards, Julian On 2015-03-12 16:22, chet...@apache.org

<    5   6   7   8   9   10   11   12   13   14   >