BUILD FAILURE: Jackrabbit Oak - Build # 2756 - Still Failing
The Apache Jenkins build system has built Jackrabbit Oak (build #2756) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/2756/ to view the results. Changes: [mreutegg] [maven-release-plugin] prepare for next development iteration [mreutegg] [maven-release-plugin] prepare release jackrabbit-oak-1.28.0 Test results: All tests passed<>
Re: Query ordered by node name
Hi Julian, thanks for your reply. > You could try the Oak Index Definition Generator. > > http://oakutils.appspot.com/generate/index > I regularly use that page to generate the index definitions I need. It was odd, when I tried the suggested index it was not chosen. It was cheaper to traverse. I deleted the index, created it again and now it is chosen, but it takes more time than traversing. Traversing takes around 24 seconds. With name = ":name" takes around 39 seconds. With name = "fn:name()" takes around 39 seconds. When the index is created this is some of the log it prints: INFO org.apache.jackrabbit.oak.plugins.index.IndexUpdate - Reindexing Traversed #86 /repo1/pruebaJF2/Doc 463312580 [4673.91 nodes/s, 16826067.39 nodes/hr] (Elapsed 3.078 min, Expected 2.000 s, Completed 98.92%) INFO org.apache.jackrabbit.oak.plugins.index.IndexUpdate - Indexing report - /oak:index/bigIndex*(81213) INFO org.apache.jackrabbit.oak.plugins.index.IndexUpdate - Reindexing completed INFO org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate - [async] Reindexing completed for indexes: [/oak:index/bigIndex*(81213)] in 3.093 min (185608 ms) I do not know what is going on. Maybe the index takes into account more nodes that it should (like version nodes) or something like that to take longer than traversing... Regards. Jorge El mar., 19 may. 2020 a las 4:02, Julian Sedding () escribió: > Or alternatively try [function = "fn:name()"], i.e. with the brackets "()". > > Regards > Julian > > On Tue, May 19, 2020 at 10:57 AM Julian Sedding > wrote: > > > > Hi Jorge > > > > You could try the Oak Index Definition Generator. > > > > http://oakutils.appspot.com/generate/index > > > > FWIW, in the "name" property node it sets [name = ":name"] instead of > > [function = "fn:name"]. I don't know if that makes a difference and > > which is better, if any. > > > > Regards > > Julian > > > > On Mon, May 18, 2020 at 11:55 PM jorgeeflorez . > > wrote: > > > > > > Hello, > > > with the following query I am able to get file nodes ordered by name: > > > > > > SELECT * FROM [nt:file] AS s WHERE ISCHILDNODE(s, [/repo1/pruebaJF1]) > ORDER > > > BY NAME([s]) DESC > > > > > > unfortunately, because I do not have an index, on a big repository I > have > > > warnings like: > > > > > > WARN org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor > - > > > Traversed 81000 nodes with filter Filter(query=SELECT * FROM [nt:file] > AS s > > > WHERE ISCHILDNODE(s, [/repo1/pruebaJF1]) ORDER BY NAME([s]) DESC, > > > path=/repo1/pruebaJF1/*); consider creating an index or changing the > query > > > > > > and the query takes a lot of time. > > > > > > I do not know how to define a proper index for name(). if I use the > > > following: > > > - compatVersion = 2 > > > - async = "async" > > > - jcr:primaryType = oak:QueryIndexDefinition > > > - evaluatePathRestrictions = true > > > - type = "lucene" > > > + indexRules > > >+ nt:file > > > + properties > > > + primaryType > > > - name = "jcr:primaryType" > > > - propertyIndex = true > > > + name > > > - function = "fn:name" > > > - ordered = true > > > - type = "String" > > > > > > the index is used (index cost is 501 compared to 80946 for traverse), > but > > > it takes more time than traversing with warnings like: > > > > > > WARN > > > > org.apache.jackrabbit.oak.plugins.index.search.spi.query.FulltextIndex$FulltextPathCursor > > > - Index-Traversed 8 nodes with filter Filter(query=SELECT * FROM > > > [nt:file] AS s WHERE ISCHILDNODE(s, [/repo1/pruebaJF1]) ORDER BY > NAME([s]) > > > DESC, path=/repo1/pruebaJF1/*) > > > > > > Thanks in advance. > > > > > > Regards. > > > > > > Jorge >
BUILD FAILURE: Jackrabbit Oak - Build # 2755 - Still Failing
The Apache Jenkins build system has built Jackrabbit Oak (build #2755) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/2755/ to view the results. Changes: [mreutegg] Ignore target folder and IntelliJ project files [mreutegg] Ignore target folder and IntelliJ project files [mreutegg] Ignore target folder and IntelliJ project files Test results: All tests passed<>
Re: [VOTE] Release Apache Jackrabbit Oak 1.8.22
On 19.05.2020 14:14, Angela Schreiber wrote: hi nitin the checks were all ok when running checkout from https://dist.apache.org/repos/dist/dev/jackrabbit however, i noticed that the verification of previous releases were executed from https://dist.apache.org/repos/dist/release/jackrabbit. ... Um, how would that work when the release candidate is, well, not released yet (and thus not under /repos/dist)? Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit Oak 1.8.22
hi nitin the checks were all ok when running checkout from https://dist.apache.org/repos/dist/dev/jackrabbit however, i noticed that the verification of previous releases were executed from https://dist.apache.org/repos/dist/release/jackrabbit. is there a particular reason for cutting this one from the 'dev' and not from the 'release'? and if not: does it have an implication? kind regards angela From: Nitin Gupta Sent: Tuesday, May 19, 2020 11:46 AM To: oak-dev@jackrabbit.apache.org Subject: [VOTE] Release Apache Jackrabbit Oak 1.8.22 A candidate for the Jackrabbit Oak 1.8.22 release is available at: https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.8.22/ The release candidate is a zip archive of the sources in: https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.8.22/ The SHA1 checksum of the archive is 482328ad73876b5ee1db0af5b885b0b17463986b. 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.22 482328ad73876b5ee1db0af5b885b0b17463986b Please vote on releasing this package as Apache Jackrabbit Oak 1.8.22. 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.22 [ ] -1 Do not release this package because... Regards, Nitin
BUILD FAILURE: Jackrabbit Oak - Build # 2754 - Still Failing
The Apache Jenkins build system has built Jackrabbit Oak (build #2754) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/2754/ to view the results. Changes: [amitj] OAK-8827: AWS support for segment-tar - Add dependency to oak-segment-remote for oak-upgrade Test results: All tests passed<>
[VOTE] Release Apache Jackrabbit Oak 1.8.22
A candidate for the Jackrabbit Oak 1.8.22 release is available at: https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.8.22/ The release candidate is a zip archive of the sources in: https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.8.22/ The SHA1 checksum of the archive is 482328ad73876b5ee1db0af5b885b0b17463986b. 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.22 482328ad73876b5ee1db0af5b885b0b17463986b Please vote on releasing this package as Apache Jackrabbit Oak 1.8.22. 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.22 [ ] -1 Do not release this package because... Regards, Nitin
Re: Query ordered by node name
Or alternatively try [function = "fn:name()"], i.e. with the brackets "()". Regards Julian On Tue, May 19, 2020 at 10:57 AM Julian Sedding wrote: > > Hi Jorge > > You could try the Oak Index Definition Generator. > > http://oakutils.appspot.com/generate/index > > FWIW, in the "name" property node it sets [name = ":name"] instead of > [function = "fn:name"]. I don't know if that makes a difference and > which is better, if any. > > Regards > Julian > > On Mon, May 18, 2020 at 11:55 PM jorgeeflorez . > wrote: > > > > Hello, > > with the following query I am able to get file nodes ordered by name: > > > > SELECT * FROM [nt:file] AS s WHERE ISCHILDNODE(s, [/repo1/pruebaJF1]) ORDER > > BY NAME([s]) DESC > > > > unfortunately, because I do not have an index, on a big repository I have > > warnings like: > > > > WARN org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor - > > Traversed 81000 nodes with filter Filter(query=SELECT * FROM [nt:file] AS s > > WHERE ISCHILDNODE(s, [/repo1/pruebaJF1]) ORDER BY NAME([s]) DESC, > > path=/repo1/pruebaJF1/*); consider creating an index or changing the query > > > > and the query takes a lot of time. > > > > I do not know how to define a proper index for name(). if I use the > > following: > > - compatVersion = 2 > > - async = "async" > > - jcr:primaryType = oak:QueryIndexDefinition > > - evaluatePathRestrictions = true > > - type = "lucene" > > + indexRules > >+ nt:file > > + properties > > + primaryType > > - name = "jcr:primaryType" > > - propertyIndex = true > > + name > > - function = "fn:name" > > - ordered = true > > - type = "String" > > > > the index is used (index cost is 501 compared to 80946 for traverse), but > > it takes more time than traversing with warnings like: > > > > WARN > > org.apache.jackrabbit.oak.plugins.index.search.spi.query.FulltextIndex$FulltextPathCursor > > - Index-Traversed 8 nodes with filter Filter(query=SELECT * FROM > > [nt:file] AS s WHERE ISCHILDNODE(s, [/repo1/pruebaJF1]) ORDER BY NAME([s]) > > DESC, path=/repo1/pruebaJF1/*) > > > > Thanks in advance. > > > > Regards. > > > > Jorge
Re: Query ordered by node name
Hi Jorge You could try the Oak Index Definition Generator. http://oakutils.appspot.com/generate/index FWIW, in the "name" property node it sets [name = ":name"] instead of [function = "fn:name"]. I don't know if that makes a difference and which is better, if any. Regards Julian On Mon, May 18, 2020 at 11:55 PM jorgeeflorez . wrote: > > Hello, > with the following query I am able to get file nodes ordered by name: > > SELECT * FROM [nt:file] AS s WHERE ISCHILDNODE(s, [/repo1/pruebaJF1]) ORDER > BY NAME([s]) DESC > > unfortunately, because I do not have an index, on a big repository I have > warnings like: > > WARN org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor - > Traversed 81000 nodes with filter Filter(query=SELECT * FROM [nt:file] AS s > WHERE ISCHILDNODE(s, [/repo1/pruebaJF1]) ORDER BY NAME([s]) DESC, > path=/repo1/pruebaJF1/*); consider creating an index or changing the query > > and the query takes a lot of time. > > I do not know how to define a proper index for name(). if I use the > following: > - compatVersion = 2 > - async = "async" > - jcr:primaryType = oak:QueryIndexDefinition > - evaluatePathRestrictions = true > - type = "lucene" > + indexRules >+ nt:file > + properties > + primaryType > - name = "jcr:primaryType" > - propertyIndex = true > + name > - function = "fn:name" > - ordered = true > - type = "String" > > the index is used (index cost is 501 compared to 80946 for traverse), but > it takes more time than traversing with warnings like: > > WARN > org.apache.jackrabbit.oak.plugins.index.search.spi.query.FulltextIndex$FulltextPathCursor > - Index-Traversed 8 nodes with filter Filter(query=SELECT * FROM > [nt:file] AS s WHERE ISCHILDNODE(s, [/repo1/pruebaJF1]) ORDER BY NAME([s]) > DESC, path=/repo1/pruebaJF1/*) > > Thanks in advance. > > Regards. > > Jorge
