Re: svn commit: r1781064 - /jackrabbit/oak/trunk/oak-doc/src/site/markdown/query/index-management.md
Hi Thomas,
On Tue, Jan 31, 2017 at 5:07 PM, wrote:
> +The following script created the index externalId:
> +
> +// create-externalId.txt
> +// create a unique index on externalId
> +{"print": "check if externalId already exists"}
> +{"xpath": "/jcr:root/oak:index/externalId"}
> +{"if": "$resultSize", "=": 1, "print": "index externalId already exists"}
> +{"$create": []}
> +{"if": "$resultSize", "=": 0, "$create": [1]}
> +{"for": "$create", "do": [
> +{"print": "does not exist; creating..."},
> +{"addNode": "/oak:index/externalId", "node": {
> +"jcr:primaryType": "oak:QueryIndexDefinition",
> +"{Name}propertyNames": ["rep:externalId"],
> +"type": "property",
> +"unique": true
> +}},
> +{"session": "save"},
> +{"print": "done; index is now:"},
> +{"xpath": "/jcr:root/oak:index/externalId", "depth": 2}
> +]}
> +exit
Scripting in JSON looks interesting!
However would like to understand the approach here and how it should
be used. Oak Console already uses Groovy and can execute those script
via ":load" construct. We already use this with customer setups to
execute scripts hosted on github [1], [2] So not sure why we need to
use this approach and how it meets the requirement for OAK-5324
Chetan Mehrotra
[1] https://gist.github.com/stillalex/e7067bcb86c89bef66c8
[2] https://gist.github.com/chetanmeh/d7588d96a839dd2d26760913e4055215
incomplete diffManyChildren during a persisted branch merge
Hi, I'm following up on failure case in oak 1.2.14 where as part of a persisted branch merge commit hooks do not propagate through all affected changes, resulting in an inconsistent state. It's unclear how realistic this scenario is and/or if it's relevant, but I was able to produce such a scenario in a test case. Interesting thing is that it's quite easily reproducible in 1.2.14 while as later in the 1.2 branch it takes longer for the test (which loops until it fails) to fail. Also, it doesn't fail in trunk even after eg 500 iterations. Does this ring a bell with anyone - diffManyChildren / wrong _modified calculation / branch - perhaps this was fixed in trunk a while ago and not backported? Cheers, Stefan -- https://issues.apache.org/jira/browse/OAK-5557
Re: [VOTE] Release Apache Jackrabbit Oak 1.6.0
On 2017-01-31 12:45, Davide Giannella wrote: On 31/01/2017 09:27, Marcel Reutegger wrote: Even though the introduction section in the RELEASE-NOTES.txt is a bit confusing. It is referring to Oak 1.4, while I think it should say 1.6. G and I even read it more than once. Used search/replace etc Maybe for the next year we can think of a review process for the release notes before the vote. I'll put that into the "creating releases" check list...
Re: [VOTE] Release Apache Jackrabbit Oak 1.6.0
> [X] +1 Release this package as Apache Jackrabbit Oak 1.6.0 Davide
Provide Common Ancestor To ConflictHandler
Hi team I wanted to inquire whether the persistence team would be interested to put [0] on the road map. Next to preventing regularly occurring merge issues in production, specifically in the user group membership area, I am sure oak would benefit as a whole from featuring three way merges. Greetings dom. [0] https://issues.apache.org/jira/browse/OAK-3381
Re: [VOTE] Release Apache Jackrabbit Oak 1.6.0
On 31/01/2017 09:27, Marcel Reutegger wrote: > Even though the introduction section in the RELEASE-NOTES.txt is a bit > confusing. It is referring to Oak 1.4, while I think it should say 1.6. G and I even read it more than once. Used search/replace etc Maybe for the next year we can think of a review process for the release notes before the vote. > I guess not a big deal and can be changed for 1.6.1. I already did it for not loosing this: http://svn.apache.org/r1781067 Davide
JIRA commit plugin
Hi, What can be done about the missing JIRA plugin that links to commits on a specific issue? I'm unable to access any data, the link asks me to "Authenticate to see related commits". I assume this is an Infra problem? thanks, alex
Re: [VOTE] Release Apache Jackrabbit Oak 1.6.0
On 2017-01-30 22:09, Davide Giannella wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.6.0 Best regards, Julian
Re: [VOTE] Release Apache Jackrabbit Oak 1.6.0
On 30/01/17 22:09, Davide Giannella wrote: > Please vote on releasing this package as Apache Jackrabbit Oak 1.6.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.6.0 Even though the introduction section in the RELEASE-NOTES.txt is a bit confusing. It is referring to Oak 1.4, while I think it should say 1.6. I guess not a big deal and can be changed for 1.6.1. Regards Marcel
Re: [VOTE] Release Apache Jackrabbit Oak 1.6.0
On 30.1.17 10:09 , Davide Giannella wrote: [x] +1 Release this package as Apache Jackrabbit Oak 1.6.0 Michael
