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

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #1216) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1216/ to view the results. Changes: No changes Test results: 18 tests failed. FAILED:

Re: [Fwd: New Windows Slaves Online - Old slaves will ge going Offline]

Thanks for forwarding. We've been to one of those slaved before but the build didn't get far. I switched to the generic Windows label as recommended for now. Let's see how this turns out. Michael On 18.10.16 9:22 , Robert Munteanu wrote: Hi, This might be of interest to you in the context

[Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 1215 - Failure

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #1215) Status: Failure Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1215/ to view the results. Changes: No changes Test results: 2 tests failed. FAILED:

Re: Oak query performance problem

Hi, > I really don¹t see the reason why this could be such a hard query Who said it's a hard query? :-) Is the problem performance, or is the problem that you get an exception? If the problem is performance, then you need an index on the node type rep:ACL. If the problem is the exception:

Re: Oak query performance problem

Hey Thomas, Ok perfect, laying an oak:QueryIndexDefinition on propertyNames jcr:primaryType and declaringNodeTypes rep:ACL solved the issue. I presumed there already was an index for all the existing jcr:primaryTypes :), not that you have to specifically have them in the declaringNodeTypes

Oak query performance problem

Hello all, I got a problem in oak concerning query performance for the following simple queries SELECT * FROM [rep:ACL] WHERE ISDESCENDANTNODE([/content]) SELECT * FROM [rep:ACL] WHERE ISDESCENDANTNODE([/var]) I get the following exception: java.lang.UnsupportedOperationException: The query

Re: Default setup configured to index all nodetype

Hi, This is an old problem, but never solved. See OAK-1150. Regards, Thomas On 17/10/16 16:08, "Chetan Mehrotra" wrote: >Hi Team, > >While doing some benchmarks I realized that default setup is >configured to index *all* nodetypes. In InitialContent the nodetype

[Fwd: New Windows Slaves Online - Old slaves will ge going Offline]

Hi, This might be of interest to you in the context of getting Oak CI builds setup on Windows. Robert Forwarded Message From: Gavin McDonald Reply-to: bui...@apache.org To: bui...@apache.org Subject: New Windows Slaves Online - Old slaves will ge going