[jira] [Commented] (OAK-7726) Build Jackrabbit Oak #1623 failed
[ https://issues.apache.org/jira/browse/OAK-7726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607292#comment-16607292 ] Hudson commented on OAK-7726: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #1634|https://builds.apache.org/job/Jackrabbit%20Oak/1634/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1634/console] > Build Jackrabbit Oak #1623 failed > - > > Key: OAK-7726 > URL: https://issues.apache.org/jira/browse/OAK-7726 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1623 has failed. > First failed run: [Jackrabbit Oak > #1623|https://builds.apache.org/job/Jackrabbit%20Oak/1623/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1623/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7510) Run repository initializers with hooks
[
https://issues.apache.org/jira/browse/OAK-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Deparvu resolved OAK-7510.
---
Resolution: Fixed
Fix Version/s: 1.9.9
fixed with http://svn.apache.org/viewvc?rev=1840303&view=rev
depending on the value of {{oak.strictInitialNSChecks}} system property you get
a warning in the logs (this is the default), or it can fail the transaction.
> Run repository initializers with hooks
> --
>
> Key: OAK-7510
> URL: https://issues.apache.org/jira/browse/OAK-7510
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
>Reporter: Alex Deparvu
>Assignee: Alex Deparvu
>Priority: Major
> Labels: modularization
> Fix For: 1.10, 1.9.9
>
>
> Currently the repository initializers (RepositoryInitializer and
> WorkspaceInitializer) run when the repo boots without any hooks [0] which
> means that current RepositoryInitializers need to setup custom Roots (roots
> with hardcoded editor providers like NamespaceEditorProvider and
> TypeEditorProvider) on top of the provided builders to be able to setup
> properly. I'm looking at the InitialContent [1] and the CugConfiguration [2]
> in the context of installing node types.
> I would like to look into removing the hardcoded providers and trying to run
> all existing editors over the content produced by the initializers.
> As an added benefit this will allow decoupling of hard dependencies between
> components (see for example OAK-7499)
> [0]
> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/Oak.java#L687
>
> [1]
> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/InitialContent.java#L134
> [2]
> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-authorization-cug/src/main/java/org/apache/jackrabbit/oak/spi/security/authorization/cug/impl/CugConfiguration.java#L162
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7726) Build Jackrabbit Oak #1623 failed
[ https://issues.apache.org/jira/browse/OAK-7726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607183#comment-16607183 ] Hudson commented on OAK-7726: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #1633|https://builds.apache.org/job/Jackrabbit%20Oak/1633/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1633/console] > Build Jackrabbit Oak #1623 failed > - > > Key: OAK-7726 > URL: https://issues.apache.org/jira/browse/OAK-7726 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1623 has failed. > First failed run: [Jackrabbit Oak > #1623|https://builds.apache.org/job/Jackrabbit%20Oak/1623/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1623/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-2655) Test failure: OrderableNodesTest.testAddNode
[
https://issues.apache.org/jira/browse/OAK-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607170#comment-16607170
]
Julian Reschke commented on OAK-2655:
-
Updated test: [^OAK-2655.diff] - this fails with RDBDS, but passed with Mongo
and Memory. Need to figure out whether RDB's behavior is ok or needs to be
fixed... (cc [~mreutegg])
> Test failure: OrderableNodesTest.testAddNode
>
>
> Key: OAK-2655
> URL: https://issues.apache.org/jira/browse/OAK-2655
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: rdbmk
>Affects Versions: 1.0.30, 1.2
> Environment: Jenkins, Ubuntu:
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/
>Reporter: Michael Dürig
>Assignee: Julian Reschke
>Priority: Major
> Labels: CI, Jenkins
> Fix For: 1.0.31, 1.3.12, 1.4
>
> Attachments: 2655.diff, OAK-2655.diff
>
>
> {{org.apache.jackrabbit.oak.jcr.OrderableNodesTest.testAddNode}} fails on
> Jenkins when running the {{DOCUMENT_RDB}} fixture.
> Failure seen at builds: 30, 44, 57, 58, 69, 78, 115, 121, 130, 132, 142, 152
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/30/jdk=jdk-1.6u45,label=Ubuntu,nsfixtures=DOCUMENT_RDB,profile=unittesting/testReport/junit/org.apache.jackrabbit.oak.jcr/OrderableNodesTest/testAddNode_0_/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-2655) Test failure: OrderableNodesTest.testAddNode
[
https://issues.apache.org/jira/browse/OAK-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-2655:
Attachment: OAK-2655.diff
> Test failure: OrderableNodesTest.testAddNode
>
>
> Key: OAK-2655
> URL: https://issues.apache.org/jira/browse/OAK-2655
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: rdbmk
>Affects Versions: 1.0.30, 1.2
> Environment: Jenkins, Ubuntu:
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/
>Reporter: Michael Dürig
>Assignee: Julian Reschke
>Priority: Major
> Labels: CI, Jenkins
> Fix For: 1.0.31, 1.3.12, 1.4
>
> Attachments: 2655.diff, OAK-2655.diff
>
>
> {{org.apache.jackrabbit.oak.jcr.OrderableNodesTest.testAddNode}} fails on
> Jenkins when running the {{DOCUMENT_RDB}} fixture.
> Failure seen at builds: 30, 44, 57, 58, 69, 78, 115, 121, 130, 132, 142, 152
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/30/jdk=jdk-1.6u45,label=Ubuntu,nsfixtures=DOCUMENT_RDB,profile=unittesting/testReport/junit/org.apache.jackrabbit.oak.jcr/OrderableNodesTest/testAddNode_0_/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7735) Split segment store persistence
[ https://issues.apache.org/jira/browse/OAK-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607090#comment-16607090 ] Tomek Rękawek commented on OAK-7735: Added tests in [r1840291|https://svn.apache.org/r1840291]. > Split segment store persistence > --- > > Key: OAK-7735 > URL: https://issues.apache.org/jira/browse/OAK-7735 > Project: Jackrabbit Oak > Issue Type: Story > Components: segment-tar >Reporter: Tomek Rękawek >Assignee: Tomek Rękawek >Priority: Major > Fix For: 1.10, 1.9.9 > > Attachments: OAK-7735.patch > > > Split segment store persistence is a proxy layer that can be used between the > SegmentMK and the actual segment store persistence. It's configured with two > backends: read-only and read-write. It delegates all the read requests to the > read-only backend, but any write request (eg. creating a new segment) is > delegated to the read-write backend. > The main advantage is that we can have a segment store in the cloud (using > the oak-segment-azure), shared amongst many Oak instances, starting > dynamically. All the changes specific for a given instance are stored > locally, with the TarPersistence. > The implementation remembers the state (tar file list, last journal entry) of > the read-only backend during it's initialisation, so the read-only backend > can be used by a different instance, as long as it only appends new segments > (eg. no compaction). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7735) Split segment store persistence
[ https://issues.apache.org/jira/browse/OAK-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomek Rękawek resolved OAK-7735. Resolution: Fixed > Split segment store persistence > --- > > Key: OAK-7735 > URL: https://issues.apache.org/jira/browse/OAK-7735 > Project: Jackrabbit Oak > Issue Type: Story > Components: segment-tar >Reporter: Tomek Rękawek >Assignee: Tomek Rękawek >Priority: Major > Fix For: 1.10, 1.9.9 > > Attachments: OAK-7735.patch > > > Split segment store persistence is a proxy layer that can be used between the > SegmentMK and the actual segment store persistence. It's configured with two > backends: read-only and read-write. It delegates all the read requests to the > read-only backend, but any write request (eg. creating a new segment) is > delegated to the read-write backend. > The main advantage is that we can have a segment store in the cloud (using > the oak-segment-azure), shared amongst many Oak instances, starting > dynamically. All the changes specific for a given instance are stored > locally, with the TarPersistence. > The implementation remembers the state (tar file list, last journal entry) of > the read-only backend during it's initialisation, so the read-only backend > can be used by a different instance, as long as it only appends new segments > (eg. no compaction). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7739) Use an index only if a certain node or property exists
[
https://issues.apache.org/jira/browse/OAK-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607028#comment-16607028
]
Thomas Mueller commented on OAK-7739:
-
Todo:
* Make the implementation more robust, e.g. against exceptions storing
multi-valued propertes / wrong types / nodes / wrong data in the "useIfExists"
property.
* How to reduce the risk of configuration mistakes.
* Documentation.
> Use an index only if a certain node or property exists
> --
>
> Key: OAK-7739
> URL: https://issues.apache.org/jira/browse/OAK-7739
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing, query
>Reporter: Thomas Mueller
>Priority: Major
> Fix For: 1.9.9
>
>
> Currently, adding a new index (or reindexing) means the index is used for
> queries as soon as indexing is finished. When using the composite node store
> (in a blue-green deployment), it would be better if there is some control on
> when the index is used for queries. Meaning, the index is used only if a
> certain node or property exists. It is not used if the node or property
> doesn't exist. That allows to control usage as follows:
> * Old (blue) version: node /library/version, property v1 does exist, but v2
> does not.
> * New (green) version: node /library/version, property v1 does not exist, but
> v2 does exist.
> Now a new index can be created which is not used with the old version, but
> used with the new version. The index configuration is as follows:
> {noformat}
> /oak:index/foo_v2/@useIfExists = /library/version/@v2
> {noformat}
> Similary, an index is used only with the old, but not with the new version,
> as follows:
> {noformat}
> /oak:index/foo_v1/@useIfExists = /library/version/@v1
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7472) tests should pass with locking disabled
[ https://issues.apache.org/jira/browse/OAK-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606955#comment-16606955 ] Julian Reschke commented on OAK-7472: - trunk: [r1831689|http://svn.apache.org/r1831689] [r1830923|http://svn.apache.org/r1830923] [r1830911|http://svn.apache.org/r1830911] 1.8: [r1840283|http://svn.apache.org/r1840283] > tests should pass with locking disabled > --- > > Key: OAK-7472 > URL: https://issues.apache.org/jira/browse/OAK-7472 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: jcr >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_6 > Fix For: 1.10, 1.9.2, 1.8.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (OAK-7472) tests should pass with locking disabled
[ https://issues.apache.org/jira/browse/OAK-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7472: Comment: was deleted (was: trunk: [r1831689|http://svn.apache.org/r1831689] [r1830923|http://svn.apache.org/r1830923] [r1830911|http://svn.apache.org/r1830911] ) > tests should pass with locking disabled > --- > > Key: OAK-7472 > URL: https://issues.apache.org/jira/browse/OAK-7472 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: jcr >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_6 > Fix For: 1.10, 1.9.2, 1.8.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7472) tests should pass with locking disabled
[ https://issues.apache.org/jira/browse/OAK-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7472: Fix Version/s: 1.8.8 > tests should pass with locking disabled > --- > > Key: OAK-7472 > URL: https://issues.apache.org/jira/browse/OAK-7472 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: jcr >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_6 > Fix For: 1.10, 1.9.2, 1.8.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7472) tests should pass with locking disabled
[ https://issues.apache.org/jira/browse/OAK-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7472: Labels: candidate_oak_1_6 (was: candidate_oak_1_8) > tests should pass with locking disabled > --- > > Key: OAK-7472 > URL: https://issues.apache.org/jira/browse/OAK-7472 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: jcr >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_6 > Fix For: 1.10, 1.9.2, 1.8.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
