[jira] [Commented] (OAK-6509) Build Jackrabbit Oak #598 failed
[ https://issues.apache.org/jira/browse/OAK-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161902#comment-16161902 ] Hudson commented on OAK-6509: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #730|https://builds.apache.org/job/Jackrabbit%20Oak/730/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/730/console] > Build Jackrabbit Oak #598 failed > > > Key: OAK-6509 > URL: https://issues.apache.org/jira/browse/OAK-6509 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: https://builds.apache.org/view/J/job/Jackrabbit%20Oak/ > The build Jackrabbit Oak #598 has failed. > First failed run: [Jackrabbit Oak > #598|https://builds.apache.org/job/Jackrabbit%20Oak/598/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/598/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6648) test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
[
https://issues.apache.org/jira/browse/OAK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161852#comment-16161852
]
Julian Reschke commented on OAK-6648:
-
I appreciate that this unblocks my own development. Now we just need to make
sure that we actually address these issues at some point of time.
> test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
>
>
> Key: OAK-6648
> URL: https://issues.apache.org/jira/browse/OAK-6648
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Michael Dürig
> Labels: test-failure, windows
> Fix For: 1.8
>
>
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@6bb75258
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8,
[jira] [Commented] (OAK-6648) test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
[
https://issues.apache.org/jira/browse/OAK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161814#comment-16161814
]
Michael Dürig commented on OAK-6648:
Unscheduling now until I have access to a Windows environment to reproduce.
> test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
>
>
> Key: OAK-6648
> URL: https://issues.apache.org/jira/browse/OAK-6648
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Michael Dürig
> Labels: test-failure, windows
> Fix For: 1.8
>
>
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@6bb75258
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ...
[jira] [Updated] (OAK-6648) test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
[
https://issues.apache.org/jira/browse/OAK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6648:
---
Fix Version/s: (was: 1.7.8)
1.8
> test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
>
>
> Key: OAK-6648
> URL: https://issues.apache.org/jira/browse/OAK-6648
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Michael Dürig
> Labels: test-failure, windows
> Fix For: 1.8
>
>
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@6bb75258
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> {
[jira] [Commented] (OAK-6648) test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
[
https://issues.apache.org/jira/browse/OAK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161811#comment-16161811
]
Michael Dürig commented on OAK-6648:
Thanks for the pointer [~catholicon]. I added a respective method to the
{{CIHelpers}} class replaced the ad-hoc ones.
Also at. http://svn.apache.org/viewvc?rev=1808053=rev I disabled the
failing test on Windows.
> test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
>
>
> Key: OAK-6648
> URL: https://issues.apache.org/jira/browse/OAK-6648
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Michael Dürig
> Labels: test-failure, windows
> Fix For: 1.8
>
>
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@6bb75258
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 =
[jira] [Commented] (OAK-6648) test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
[
https://issues.apache.org/jira/browse/OAK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161557#comment-16161557
]
Vikas Saurabh commented on OAK-6648:
[~mduerig], {{IndexCopierTest}} has:
{code}
private static void assumeNotWindows() {
assumeTrue(!StandardSystemProperty.OS_NAME.value().toLowerCase().contains("windows"));
}
{code}
Maybe, we can put this in {{CIHelper}} and use that one all over the place
which require such check.
> test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
>
>
> Key: OAK-6648
> URL: https://issues.apache.org/jira/browse/OAK-6648
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Michael Dürig
> Labels: test-failure, windows
> Fix For: 1.7.8
>
>
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@6bb75258
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 =
[jira] [Commented] (OAK-6509) Build Jackrabbit Oak #598 failed
[ https://issues.apache.org/jira/browse/OAK-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161517#comment-16161517 ] Hudson commented on OAK-6509: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #729|https://builds.apache.org/job/Jackrabbit%20Oak/729/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/729/console] > Build Jackrabbit Oak #598 failed > > > Key: OAK-6509 > URL: https://issues.apache.org/jira/browse/OAK-6509 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: https://builds.apache.org/view/J/job/Jackrabbit%20Oak/ > The build Jackrabbit Oak #598 has failed. > First failed run: [Jackrabbit Oak > #598|https://builds.apache.org/job/Jackrabbit%20Oak/598/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/598/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OAK-6648) test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
[
https://issues.apache.org/jira/browse/OAK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161472#comment-16161472
]
Michael Dürig edited comment on OAK-6648 at 9/11/17 4:02 PM:
-
Checked again, cannot reproduce at my end. I assume this has to do with the
point in time when files can/cannot be deleted on Windows vs. other platforms.
Will investigate once I have access to a Windows environment.
Until then we should probably add a method to {{CIHelper}} to detect a Windows
environment and disable the test in that case. [~reschke], could you help out
with finding a good way to detect whether the tests are running on Windows?
was (Author: mduerig):
Checked again, cannot reproduce at my end. I assume this has to do with the
point in time when files can/cannot be deleted on Windows vs. other platforms.
Will investigate once I have access to a Windows environment.
> test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
>
>
> Key: OAK-6648
> URL: https://issues.apache.org/jira/browse/OAK-6648
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Michael Dürig
> Labels: test-failure, windows
> Fix For: 1.7.8
>
>
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@6bb75258
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
>
[jira] [Updated] (OAK-6648) test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
[
https://issues.apache.org/jira/browse/OAK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6648:
---
Labels: test-failure windows (was: )
> test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
>
>
> Key: OAK-6648
> URL: https://issues.apache.org/jira/browse/OAK-6648
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Michael Dürig
> Labels: test-failure, windows
> Fix For: 1.7.8
>
>
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@6bb75258
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7
[jira] [Commented] (OAK-6648) test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
[
https://issues.apache.org/jira/browse/OAK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161472#comment-16161472
]
Michael Dürig commented on OAK-6648:
Checked again, cannot reproduce at my end. I assume this has to do with the
point in time when files can/cannot be deleted on Windows vs. other platforms.
Will investigate once I have access to a Windows environment.
> test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
>
>
> Key: OAK-6648
> URL: https://issues.apache.org/jira/browse/OAK-6648
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Michael Dürig
> Fix For: 1.7.8
>
>
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@6bb75258
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> =
[jira] [Commented] (OAK-6648) test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
[
https://issues.apache.org/jira/browse/OAK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161443#comment-16161443
]
Julian Reschke commented on OAK-6648:
-
Yes, it's likely Windows-only.
> test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
>
>
> Key: OAK-6648
> URL: https://issues.apache.org/jira/browse/OAK-6648
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Michael Dürig
> Fix For: 1.7.8
>
>
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@6bb75258
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... },
[jira] [Comment Edited] (OAK-6648) test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
[
https://issues.apache.org/jira/browse/OAK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161443#comment-16161443
]
Julian Reschke edited comment on OAK-6648 at 9/11/17 3:30 PM:
--
Yes, it's likely Windows-only - and it is reproducible.
was (Author: reschke):
Yes, it's likely Windows-only.
> test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
>
>
> Key: OAK-6648
> URL: https://issues.apache.org/jira/browse/OAK-6648
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Michael Dürig
> Fix For: 1.7.8
>
>
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@6bb75258
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 =
[jira] [Commented] (OAK-6648) test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
[
https://issues.apache.org/jira/browse/OAK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161437#comment-16161437
]
Michael Dürig commented on OAK-6648:
[~reschke], is this reproducible at your end? Might this be a Windows issue, as
I cannot reproduce it on osx nor linux.
> test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
>
>
> Key: OAK-6648
> URL: https://issues.apache.org/jira/browse/OAK-6648
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Michael Dürig
> Fix For: 1.7.8
>
>
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@6bb75258
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ...
[jira] [Updated] (OAK-6648) test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
[
https://issues.apache.org/jira/browse/OAK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6648:
---
Fix Version/s: 1.7.8
> test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
>
>
> Key: OAK-6648
> URL: https://issues.apache.org/jira/browse/OAK-6648
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Andrei Dulceanu
> Fix For: 1.7.8
>
>
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@6bb75258
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
[jira] [Assigned] (OAK-6648) test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
[
https://issues.apache.org/jira/browse/OAK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig reassigned OAK-6648:
--
Assignee: Michael Dürig (was: Andrei Dulceanu)
> test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
>
>
> Key: OAK-6648
> URL: https://issues.apache.org/jira/browse/OAK-6648
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Michael Dürig
> Fix For: 1.7.8
>
>
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@6bb75258
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ...
[jira] [Updated] (OAK-6641) test failure in org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT
[
https://issues.apache.org/jira/browse/OAK-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-6641:
Affects Version/s: 1.7.7
> test failure in
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT
>
>
> Key: OAK-6641
> URL: https://issues.apache.org/jira/browse/OAK-6641
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar, tarmk-standby
>Affects Versions: 1.7.7
>Reporter: Julian Reschke
>Assignee: Andrei Dulceanu
> Labels: cold-standby
> Fix For: 1.8, 1.7.8
>
>
> {noformat}
> Tests run: 10, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 99.858 sec
> <<< FAILURE! - in
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT
> testSyncBigBlob(org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT)
> Time elapsed: 71.122 sec <<< ERROR!
> java.lang.RuntimeException: Error occurred while obtaining InputStream for
> blobId
> [8098b6ac1491be80b7e58a85767ede178c432866d90caf6726f556406ecc84a4#1073741824]
> Caused by: java.io.IOException:
> org.apache.jackrabbit.core.data.DataStoreException: Record
> 8098b6ac1491be80b7e58a85767ede178c432866d90caf6726f556406ecc84a4 does not
> exist
> Caused by: org.apache.jackrabbit.core.data.DataStoreException: Record
> 8098b6ac1491be80b7e58a85767ede178c432866d90caf6726f556406ecc84a4 does not
> exist
> {noformat}
> (might be specific to Windows)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6648) test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
Julian Reschke created OAK-6648:
---
Summary: test failure seen in
org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
Key: OAK-6648
URL: https://issues.apache.org/jira/browse/OAK-6648
Project: Jackrabbit Oak
Issue Type: Bug
Components: segment-tar
Reporter: Julian Reschke
{noformat}
Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
Apache Jackrabbit Oak 1.6.1
===> true
===> org.apache.jackrabbit.oak.plugins.document.*,
org.apache.jackrabbit.oak.plugins.segment.*,
org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
===> org.apache.jackrabbit.oak.plugins.document.*,
org.apache.jackrabbit.oak.plugins.segment.*,
org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
org.apache.jackrabbit.oak.spi.commit.EmptyHook
===> org.apache.jackrabbit.oak.plugins.document.*,
org.apache.jackrabbit.oak.plugins.segment.*,
org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
org.apache.jackrabbit.oak.spi.commit.EmptyHook,
org.apache.jackrabbit.oak.spi.commit.CommitInfo
===> true
===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@6bb75258
===> SegmentNodeBuilder{path=/}
===> null
===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3 =
property-value-5-3, property-name-5-4 = property-value-5-4, property-name-5-5 =
property-value-5-5, property-name-5-6 = property-value-5-6, property-name-5-7 =
property-value-5-7, property-name-5-8 = property-value-5-8, property-name-5-9 =
property-value-5-9, node-5-3 = { ... }, node-5-4 = { ... }, node-5-9 = { ... },
node-5-1 = { ... }, node-5-2 = { ... }, node-5-7 = { ... }, node-5-8 = { ... },
node-5-5 = { ... }, node-5-0 = { ... }, node-5-6 = { ... } }
Apache Jackrabbit Oak 1.6.1
===> true
===> org.apache.jackrabbit.oak.plugins.document.*,
org.apache.jackrabbit.oak.plugins.segment.*,
org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
===> org.apache.jackrabbit.oak.plugins.document.*,
org.apache.jackrabbit.oak.plugins.segment.*,
org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
org.apache.jackrabbit.oak.spi.commit.EmptyHook
===> org.apache.jackrabbit.oak.plugins.document.*,
org.apache.jackrabbit.oak.plugins.segment.*,
org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
org.apache.jackrabbit.oak.spi.commit.EmptyHook,
org.apache.jackrabbit.oak.spi.commit.CommitInfo
===> true
===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
===> SegmentNodeBuilder{path=/}
===> null
===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3 =
property-value-5-3, property-name-5-4 = property-value-5-4, property-name-5-5 =
property-value-5-5, property-name-5-6 = property-value-5-6, property-name-5-7 =
property-value-5-7, property-name-5-8 = property-value-5-8, property-name-5-9 =
property-value-5-9, node-5-3 = { ... }, node-5-4 = { ... }, node-5-9 = { ... },
node-5-1 = { ... }, node-5-2 = { ... }, node-5-7 = { ... }, node-5-8 = { ... },
node-5-5 = { ... }, node-5-0 = { ... }, node-5-6 = { ... } }
Apache Jackrabbit Oak 1.6.1
===> true
===> org.apache.jackrabbit.oak.plugins.document.*,
org.apache.jackrabbit.oak.plugins.segment.*,
org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
===> org.apache.jackrabbit.oak.plugins.document.*,
org.apache.jackrabbit.oak.plugins.segment.*,
org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
org.apache.jackrabbit.oak.spi.commit.EmptyHook
===> org.apache.jackrabbit.oak.plugins.document.*,
org.apache.jackrabbit.oak.plugins.segment.*,
org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
org.apache.jackrabbit.oak.spi.commit.EmptyHook,
org.apache.jackrabbit.oak.spi.commit.CommitInfo
===> true
===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
===> SegmentNodeBuilder{path=/}
===> null
===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3 =
property-value-5-3, property-name-5-4 = property-value-5-4, property-name-5-5 =
property-value-5-5, property-name-5-6 = property-value-5-6, property-name-5-7 =
property-value-5-7, property-name-5-8 = property-value-5-8, property-name-5-9 =
property-value-5-9, node-5-3 = { ... }, node-5-4 = { ... }, node-5-9 = { ... },
node-5-1 = { ... }, node-5-2 = { ... }, node-5-7 = { ... }, node-5-8 = { ... },
node-5-5 = { ... }, node-5-0 = { ... }, node-5-6 = { ... } }
Apache Jackrabbit Oak 1.6.1
===> true
===> org.apache.jackrabbit.oak.plugins.document.*,
org.apache.jackrabbit.oak.plugins.segment.*,
org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
===> org.apache.jackrabbit.oak.plugins.document.*,
org.apache.jackrabbit.oak.plugins.segment.*,
org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
org.apache.jackrabbit.oak.spi.commit.EmptyHook
===>
[jira] [Assigned] (OAK-6648) test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
[
https://issues.apache.org/jira/browse/OAK-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke reassigned OAK-6648:
---
Assignee: Andrei Dulceanu
> test failure seen in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
>
>
> Key: OAK-6648
> URL: https://issues.apache.org/jira/browse/OAK-6648
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Andrei Dulceanu
>
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@6bb75258
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@5b04476e
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... },
[jira] [Comment Edited] (OAK-6644) Use ReadOnlyNodeBuilder for the read-only mounts
[ https://issues.apache.org/jira/browse/OAK-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161263#comment-16161263 ] Tomek Rękawek edited comment on OAK-6644 at 9/11/17 2:55 PM: - Fixed for trunk in [r1808026|https://svn.apache.org/r1808026] & [r1808033|https://svn.apache.org/r1808033]. was (Author: tomek.rekawek): Fixed for trunk in [r1808026|https://svn.apache.org/r1808026]. > Use ReadOnlyNodeBuilder for the read-only mounts > > > Key: OAK-6644 > URL: https://issues.apache.org/jira/browse/OAK-6644 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: composite >Reporter: Tomek Rękawek > Fix For: 1.8, 1.7.8 > > > Using native node builder (Segment/DocumentNodeBuilder) may be a bit > expensive. Let's try to use ReadOnlyNodeBuilder for the non-default, > read-only mounts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6639) ObservationQueueFullWarnTest.testQueueFullThenFlushing fails sometimes
[
https://issues.apache.org/jira/browse/OAK-6639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli resolved OAK-6639.
--
Resolution: Fixed
Fix Version/s: 1.7.8
Thanks [~catholicon] for spotting!
I've fixed this in rev 1808032
The issue was that when registering an Observer the Observable (typically, ours
at least do) call contentChanged with an initial, empty commit info. That
initial call still ends up on the BackgroundObserver's queue - so it actually
occupies an additional entry - which was not correctly taken into account when
designing the test.
So the fix is to, after registering the listener (which is when the Observer is
registered), sleep 2sec to give the BackgroundObserver enough time to process
that initial contentChanged call.
> ObservationQueueFullWarnTest.testQueueFullThenFlushing fails sometimes
> --
>
> Key: OAK-6639
> URL: https://issues.apache.org/jira/browse/OAK-6639
> Project: Jackrabbit Oak
> Issue Type: Test
> Components: jcr
>Reporter: Vikas Saurabh
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: 1.8, 1.7.8
>
> Attachments: archive.zip, console.txt
>
>
> Very intermittently,
> {{ObservationQueueFullWarnTest.testQueueFullThenFlushing}} fails. It had
> failed once in one of our internal CI setups. And recently (thankfully??) on
> apache setup \[0] \[1] \[2].
> Description from Apache failure:
>
> h4. Error Message
> Just filled queue must not convert local->external expected:<6> but was:<4>
> h4. Stacktrace
> {noformat}
> java.lang.AssertionError: Just filled queue must not convert local->external
> expected:<6> but was:<4>
> at
> org.apache.jackrabbit.oak.jcr.observation.ObservationQueueFullWarnTest.testQueueFullThenFlushing(ObservationQueueFullWarnTest.java:312)
> {noformat}
> h4. Standard Output
> {noformat}
> storing: /testNode/local0
> storing: /testNode/local1
> storing: /testNode/local2
> storing: /testNode/local3
> storing: /testNode/local4
> storing: /testNode/local5
> GOT: 1 - COUNTER: 1
> - Event{type=4, path=/testNode/local0, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=0}, userID=admin,
> userData=null, date=1504862948917, external=false}
> GOT: 1 - COUNTER: 2
> - Event{type=4, path=/testNode/local1, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=1}, userID=admin,
> userData=null, date=1504862948918, external=false}
> GOT: 1 - COUNTER: 3
> - Event{type=4, path=/testNode/local2, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=2}, userID=admin,
> userData=null, date=1504862948919, external=false}
> GOT: 1 - COUNTER: 4
> - Event{type=4, path=/testNode/local3, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=3}, userID=admin,
> userData=null, date=1504862948919, external=false}
> GOT: 2 - COUNTER: 6
> - Event{type=4, path=/testNode/local4, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=4}, userID=oak:unknown,
> userData=null, date=1504862873156, external=true}
> - Event{type=4, path=/testNode/local5, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=5}, userID=oak:unknown,
> userData=null, date=1504862873156, external=true}
> {noformat}
>
> \[0]:
> https://lists.apache.org/thread.html/9c952201c132e2c6dce67b2d4fb13d9b0040d9874514885a9ed5bc9f@%3Coak-dev.jackrabbit.apache.org%3E
> \[1]: https://builds.apache.org/job/Jackrabbit%20Oak/722/
> \[2]:
> https://builds.apache.org/job/Jackrabbit%20Oak/722/org.apache.jackrabbit$oak-jcr/testReport/junit/org.apache.jackrabbit.oak.jcr.observation/ObservationQueueFullWarnTest/testQueueFullThenFlushing_SegmentTar_/
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (OAK-6639) ObservationQueueFullWarnTest.testQueueFullThenFlushing fails sometimes
[
https://issues.apache.org/jira/browse/OAK-6639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161365#comment-16161365
]
Stefan Egli edited comment on OAK-6639 at 9/11/17 2:39 PM:
---
Thanks [~catholicon] for spotting!
I've fixed this in rev
[1808032|http://svn.apache.org/viewvc?rev=1808032=rev]
The issue was that when registering an Observer the Observable (typically, ours
at least do) call contentChanged with an initial, empty commit info. That
initial call still ends up on the BackgroundObserver's queue - so it actually
occupies an additional entry - which was not correctly taken into account when
designing the test.
So the fix is to, after registering the listener (which is when the Observer is
registered), sleep 2sec to give the BackgroundObserver enough time to process
that initial contentChanged call.
was (Author: egli):
Thanks [~catholicon] for spotting!
I've fixed this in rev 1808032
The issue was that when registering an Observer the Observable (typically, ours
at least do) call contentChanged with an initial, empty commit info. That
initial call still ends up on the BackgroundObserver's queue - so it actually
occupies an additional entry - which was not correctly taken into account when
designing the test.
So the fix is to, after registering the listener (which is when the Observer is
registered), sleep 2sec to give the BackgroundObserver enough time to process
that initial contentChanged call.
> ObservationQueueFullWarnTest.testQueueFullThenFlushing fails sometimes
> --
>
> Key: OAK-6639
> URL: https://issues.apache.org/jira/browse/OAK-6639
> Project: Jackrabbit Oak
> Issue Type: Test
> Components: jcr
>Reporter: Vikas Saurabh
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: 1.8, 1.7.8
>
> Attachments: archive.zip, console.txt
>
>
> Very intermittently,
> {{ObservationQueueFullWarnTest.testQueueFullThenFlushing}} fails. It had
> failed once in one of our internal CI setups. And recently (thankfully??) on
> apache setup \[0] \[1] \[2].
> Description from Apache failure:
>
> h4. Error Message
> Just filled queue must not convert local->external expected:<6> but was:<4>
> h4. Stacktrace
> {noformat}
> java.lang.AssertionError: Just filled queue must not convert local->external
> expected:<6> but was:<4>
> at
> org.apache.jackrabbit.oak.jcr.observation.ObservationQueueFullWarnTest.testQueueFullThenFlushing(ObservationQueueFullWarnTest.java:312)
> {noformat}
> h4. Standard Output
> {noformat}
> storing: /testNode/local0
> storing: /testNode/local1
> storing: /testNode/local2
> storing: /testNode/local3
> storing: /testNode/local4
> storing: /testNode/local5
> GOT: 1 - COUNTER: 1
> - Event{type=4, path=/testNode/local0, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=0}, userID=admin,
> userData=null, date=1504862948917, external=false}
> GOT: 1 - COUNTER: 2
> - Event{type=4, path=/testNode/local1, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=1}, userID=admin,
> userData=null, date=1504862948918, external=false}
> GOT: 1 - COUNTER: 3
> - Event{type=4, path=/testNode/local2, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=2}, userID=admin,
> userData=null, date=1504862948919, external=false}
> GOT: 1 - COUNTER: 4
> - Event{type=4, path=/testNode/local3, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=3}, userID=admin,
> userData=null, date=1504862948919, external=false}
> GOT: 2 - COUNTER: 6
> - Event{type=4, path=/testNode/local4, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=4}, userID=oak:unknown,
> userData=null, date=1504862873156, external=true}
> - Event{type=4, path=/testNode/local5, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=5}, userID=oak:unknown,
> userData=null, date=1504862873156, external=true}
> {noformat}
>
> \[0]:
> https://lists.apache.org/thread.html/9c952201c132e2c6dce67b2d4fb13d9b0040d9874514885a9ed5bc9f@%3Coak-dev.jackrabbit.apache.org%3E
> \[1]: https://builds.apache.org/job/Jackrabbit%20Oak/722/
> \[2]:
> https://builds.apache.org/job/Jackrabbit%20Oak/722/org.apache.jackrabbit$oak-jcr/testReport/junit/org.apache.jackrabbit.oak.jcr.observation/ObservationQueueFullWarnTest/testQueueFullThenFlushing_SegmentTar_/
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (OAK-6639) ObservationQueueFullWarnTest.testQueueFullThenFlushing fails sometimes
[
https://issues.apache.org/jira/browse/OAK-6639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli reassigned OAK-6639:
Assignee: Stefan Egli (was: Vikas Saurabh)
> ObservationQueueFullWarnTest.testQueueFullThenFlushing fails sometimes
> --
>
> Key: OAK-6639
> URL: https://issues.apache.org/jira/browse/OAK-6639
> Project: Jackrabbit Oak
> Issue Type: Test
> Components: jcr
>Reporter: Vikas Saurabh
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: 1.8
>
> Attachments: archive.zip, console.txt
>
>
> Very intermittently,
> {{ObservationQueueFullWarnTest.testQueueFullThenFlushing}} fails. It had
> failed once in one of our internal CI setups. And recently (thankfully??) on
> apache setup \[0] \[1] \[2].
> Description from Apache failure:
>
> h4. Error Message
> Just filled queue must not convert local->external expected:<6> but was:<4>
> h4. Stacktrace
> {noformat}
> java.lang.AssertionError: Just filled queue must not convert local->external
> expected:<6> but was:<4>
> at
> org.apache.jackrabbit.oak.jcr.observation.ObservationQueueFullWarnTest.testQueueFullThenFlushing(ObservationQueueFullWarnTest.java:312)
> {noformat}
> h4. Standard Output
> {noformat}
> storing: /testNode/local0
> storing: /testNode/local1
> storing: /testNode/local2
> storing: /testNode/local3
> storing: /testNode/local4
> storing: /testNode/local5
> GOT: 1 - COUNTER: 1
> - Event{type=4, path=/testNode/local0, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=0}, userID=admin,
> userData=null, date=1504862948917, external=false}
> GOT: 1 - COUNTER: 2
> - Event{type=4, path=/testNode/local1, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=1}, userID=admin,
> userData=null, date=1504862948918, external=false}
> GOT: 1 - COUNTER: 3
> - Event{type=4, path=/testNode/local2, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=2}, userID=admin,
> userData=null, date=1504862948919, external=false}
> GOT: 1 - COUNTER: 4
> - Event{type=4, path=/testNode/local3, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=3}, userID=admin,
> userData=null, date=1504862948919, external=false}
> GOT: 2 - COUNTER: 6
> - Event{type=4, path=/testNode/local4, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=4}, userID=oak:unknown,
> userData=null, date=1504862873156, external=true}
> - Event{type=4, path=/testNode/local5, identifier=/testNode,
> info={jcr:primaryType=nt:unstructured, afterValue=5}, userID=oak:unknown,
> userData=null, date=1504862873156, external=true}
> {noformat}
>
> \[0]:
> https://lists.apache.org/thread.html/9c952201c132e2c6dce67b2d4fb13d9b0040d9874514885a9ed5bc9f@%3Coak-dev.jackrabbit.apache.org%3E
> \[1]: https://builds.apache.org/job/Jackrabbit%20Oak/722/
> \[2]:
> https://builds.apache.org/job/Jackrabbit%20Oak/722/org.apache.jackrabbit$oak-jcr/testReport/junit/org.apache.jackrabbit.oak.jcr.observation/ObservationQueueFullWarnTest/testQueueFullThenFlushing_SegmentTar_/
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (OAK-6221) Deprecate SecurityProviderImpl
[
https://issues.apache.org/jira/browse/OAK-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161338#comment-16161338
]
Alex Deparvu edited comment on OAK-6221 at 9/11/17 2:23 PM:
wip branch at:
https://github.com/apache/jackrabbit-oak/compare/trunk...stillalex:oak-6221
main problem I had was to find a way to deal with cases that live between the
configuration maps which the security bits rely on and the OGSi bindings. so
far I could not find a good working solution for:
* [oak-core] AuthorizationConfigurationImpl
setting the mountInfoProvider ref outside of OSGi, so far I went with
#bind/#unbind methods that would need to be manually called. also, this
reference looks like it should be optional but it's clearly needed - does it
make sense to dedicate an issue to checking usage of this reference only?
* [oak-auth-external] CugConfiguration
same as above, how to set the following outside of OSGi context:
mountInfoProvider, supportedPaths, exclude
* [oak-auth-external] ExternalPrincipalConfiguration
does simply not work outside of OSGi
[~anchela] if you have a few spare minutes, I'd appreciate your thoughts here.
was (Author: alex.parvulescu):
wip branch at:
https://github.com/apache/jackrabbit-oak/compare/trunk...stillalex:oak-6221
main problem I had was to find a way to deal with cases that live between the
configuration maps which the security bits rely on and the OGSi bindings. so
far I could not find a good working solution for:
* [oak-core] AuthorizationConfigurationImpl
- setting the mountInfoProvider ref outside of OSGi, so far I went with
#bind/#unbind methods that would need to be manually called. also, this
reference looks like it should be optional but it's clearly needed - does it
make sense to dedicate an issue to checking usage of this reference only?
* [oak-auth-external] CugConfiguration
- same as above, how to set the following outside of OSGi context:
mountInfoProvider, supportedPaths, exclude
* [oak-auth-external] ExternalPrincipalConfiguration
- does simply not work outside of OSGi
[~anchela] if you have a few spare minutes, I'd appreciate your thoughts here.
> Deprecate SecurityProviderImpl
> --
>
> Key: OAK-6221
> URL: https://issues.apache.org/jira/browse/OAK-6221
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, security
>Reporter: Alex Deparvu
>Assignee: Alex Deparvu
>
> As agreed on OAK-6172, the {{SecurityProviderImpl}} should be deprecated in
> favor of the {{InternalSecurityProvider}}.
> This should also cover coming up with a way to use the new version in tests
> while we figure out OSGi testing setups.
> fyi [~anchela]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6221) Deprecate SecurityProviderImpl
[
https://issues.apache.org/jira/browse/OAK-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161338#comment-16161338
]
Alex Deparvu commented on OAK-6221:
---
wip branch at:
https://github.com/apache/jackrabbit-oak/compare/trunk...stillalex:oak-6221
main problem I had was to find a way to deal with cases that live between the
configuration maps which the security bits rely on and the OGSi bindings. so
far I could not find a good working solution for:
* [oak-core] AuthorizationConfigurationImpl
- setting the mountInfoProvider ref outside of OSGi, so far I went with
#bind/#unbind methods that would need to be manually called. also, this
reference looks like it should be optional but it's clearly needed - does it
make sense to dedicate an issue to checking usage of this reference only?
* [oak-auth-external] CugConfiguration
- same as above, how to set the following outside of OSGi context:
mountInfoProvider, supportedPaths, exclude
* [oak-auth-external] ExternalPrincipalConfiguration
- does simply not work outside of OSGi
[~anchela] if you have a few spare minutes, I'd appreciate your thoughts here.
> Deprecate SecurityProviderImpl
> --
>
> Key: OAK-6221
> URL: https://issues.apache.org/jira/browse/OAK-6221
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, security
>Reporter: Alex Deparvu
>Assignee: Alex Deparvu
>
> As agreed on OAK-6172, the {{SecurityProviderImpl}} should be deprecated in
> favor of the {{InternalSecurityProvider}}.
> This should also cover coming up with a way to use the new version in tests
> while we figure out OSGi testing setups.
> fyi [~anchela]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OAK-6647) Reduce reads by RevisionGC
[
https://issues.apache.org/jira/browse/OAK-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved OAK-6647.
---
Resolution: Fixed
Fix Version/s: 1.7.8
Done in trunk: http://svn.apache.org/r1808028
> Reduce reads by RevisionGC
> --
>
> Key: OAK-6647
> URL: https://issues.apache.org/jira/browse/OAK-6647
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Minor
> Fix For: 1.8, 1.7.8
>
>
> The RevisionGC reads the {{revisionGC}} documents multiple times. Some of
> those reads can be avoided.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6647) Reduce reads by RevisionGC
Marcel Reutegger created OAK-6647:
-
Summary: Reduce reads by RevisionGC
Key: OAK-6647
URL: https://issues.apache.org/jira/browse/OAK-6647
Project: Jackrabbit Oak
Issue Type: Improvement
Components: documentmk
Reporter: Marcel Reutegger
Assignee: Marcel Reutegger
Priority: Minor
Fix For: 1.8
The RevisionGC reads the {{revisionGC}} documents multiple times. Some of those
reads can be avoided.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OAK-6644) Use ReadOnlyNodeBuilder for the read-only mounts
[ https://issues.apache.org/jira/browse/OAK-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomek Rękawek resolved OAK-6644. Resolution: Fixed > Use ReadOnlyNodeBuilder for the read-only mounts > > > Key: OAK-6644 > URL: https://issues.apache.org/jira/browse/OAK-6644 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: composite >Reporter: Tomek Rękawek > Fix For: 1.8, 1.7.8 > > > Using native node builder (Segment/DocumentNodeBuilder) may be a bit > expensive. Let's try to use ReadOnlyNodeBuilder for the non-default, > read-only mounts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6644) Use ReadOnlyNodeBuilder for the read-only mounts
[ https://issues.apache.org/jira/browse/OAK-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161263#comment-16161263 ] Tomek Rękawek commented on OAK-6644: Fixed for trunk in [r1808026|https://svn.apache.org/r1808026]. > Use ReadOnlyNodeBuilder for the read-only mounts > > > Key: OAK-6644 > URL: https://issues.apache.org/jira/browse/OAK-6644 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: composite >Reporter: Tomek Rękawek > Fix For: 1.8, 1.7.8 > > > Using native node builder (Segment/DocumentNodeBuilder) may be a bit > expensive. Let's try to use ReadOnlyNodeBuilder for the non-default, > read-only mounts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OAK-3150) Update Lucene to 6.x series
[ https://issues.apache.org/jira/browse/OAK-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili reassigned OAK-3150: Assignee: Tommaso Teofili > Update Lucene to 6.x series > --- > > Key: OAK-3150 > URL: https://issues.apache.org/jira/browse/OAK-3150 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Tommaso Teofili > Labels: technical_debt > Fix For: 1.8 > > > We should look into updating the Lucene version to 6.x. Java 8 is the minimum > Java version required > Note this is to be done for trunk only -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6646) Make it possible to set timeouts in Solr index connections
[ https://issues.apache.org/jira/browse/OAK-6646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved OAK-6646. -- Resolution: Fixed fixed in r1808022. > Make it possible to set timeouts in Solr index connections > -- > > Key: OAK-6646 > URL: https://issues.apache.org/jira/browse/OAK-6646 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: solr >Reporter: Tommaso Teofili >Assignee: Tommaso Teofili > Fix For: 1.8 > > > Currently socket and connection timeouts for remote Solr clients are not > configurable. However in some environments, e.g. with proxies / load > balancers in front or having network latencies, it'd be useful to be able to > tweak such timeouts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5885) segment-tar should have a tarmkrecovery command
[
https://issues.apache.org/jira/browse/OAK-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-5885:
---
Fix Version/s: (was: 1.7.9)
1.7.10
> segment-tar should have a tarmkrecovery command
> ---
>
> Key: OAK-5885
> URL: https://issues.apache.org/jira/browse/OAK-5885
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: run, segment-tar
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Labels: tooling
> Fix For: 1.8, 1.7.10
>
>
> {{oak-segment}} had a {{tarmkrecovery}} command responsible with listing
> candidates for head journal entries. We should re-enable this also for
> {{oak-segment-tar}}.
> /cc [~mduerig] [~frm]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5792) TarMK: Implement tooling to repair broken nodes
[
https://issues.apache.org/jira/browse/OAK-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-5792:
---
Fix Version/s: (was: 1.7.9)
1.7.10
> TarMK: Implement tooling to repair broken nodes
> ---
>
> Key: OAK-5792
> URL: https://issues.apache.org/jira/browse/OAK-5792
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: segment-tar
>Reporter: Michael Dürig
>Assignee: Andrei Dulceanu
> Labels: production, tooling
> Fix For: 1.8, 1.7.10
>
>
> With {{oak-run check}} we can determine the last good revision of a
> repository and use it to manually roll back a corrupted segment store.
> Complementary to this we should implement a tool to roll forward a broken
> revision to a fixed new revision. Such a tool needs to detect which items are
> affected by a corruption and replace these items with markers. With this the
> repository could brought back online and the markers could be used to
> identify the locations in the tree where further manual action might be
> needed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6373) oak-run check should also check checkpoints
[
https://issues.apache.org/jira/browse/OAK-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6373:
---
Fix Version/s: (was: 1.7.9)
1.7.10
> oak-run check should also check checkpoints
>
>
> Key: OAK-6373
> URL: https://issues.apache.org/jira/browse/OAK-6373
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Reporter: Michael Dürig
>Assignee: Andrei Dulceanu
> Labels: tooling
> Fix For: 1.8, 1.7.10
>
>
> {{oak-run check}} does currently *not* traverse and check the items in the
> checkpoint. I think we should change this and add an option to traverse all,
> some or none of the checkpoints. When doing this we need to keep in mind the
> interaction of this new feature with the {{filter}} option: the paths passed
> through this option need then be prefixed with {{/root}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6626) Replace standby blob chunk size configuration with feature flag
[
https://issues.apache.org/jira/browse/OAK-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6626:
---
Fix Version/s: (was: 1.7.8)
1.7.9
> Replace standby blob chunk size configuration with feature flag
> ---
>
> Key: OAK-6626
> URL: https://issues.apache.org/jira/browse/OAK-6626
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar, tarmk-standby
>Reporter: Michael Dürig
>Assignee: Andrei Dulceanu
> Labels: cold-standby, configuration
> Fix For: 1.8, 1.7.9
>
>
> We should remove the {{StandbyStoreService#BLOB_CHUNK_SIZE}} OSGi
> configuration and replace it with a feature flag. Rational: we expect
> customer to rarely change this thus not justifying the additional
> configuration complexity and testing overhead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6542) java.lang.NoClassDefFoundError: com/codahale/metrics/Reservoir
[ https://issues.apache.org/jira/browse/OAK-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-6542: --- Fix Version/s: 1.7.8 > java.lang.NoClassDefFoundError: com/codahale/metrics/Reservoir > -- > > Key: OAK-6542 > URL: https://issues.apache.org/jira/browse/OAK-6542 > Project: Jackrabbit Oak > Issue Type: Bug > Components: segment-tar >Affects Versions: 1.7.5 >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Andrei Dulceanu > Fix For: 1.7.8 > > > Upgrading to last 1.7.5. > I get this exception > java.lang.NoClassDefFoundError: com/codahale/metrics/Reservoir > at > org.apache.jackrabbit.oak.segment.SegmentNodeStore.(SegmentNodeStore.java:166) > at > org.apache.jackrabbit.oak.segment.SegmentNodeStore.(SegmentNodeStore.java:63) > at > org.apache.jackrabbit.oak.segment.SegmentNodeStore$SegmentNodeStoreBuilder.build(SegmentNodeStore.java:121) > Looking at the pom the dependency has a scope provided > (http://repo.maven.apache.org/maven2/org/apache/jackrabbit/oak-segment-tar/1.7.5/oak-segment-tar-1.7.5.pom) > IMHO it's a wrong dependency scope at it's definitely needed as there is no > usage of reflection to avoid loading of the classes -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6594) UpgradeIT produces unwanted output
[
https://issues.apache.org/jira/browse/OAK-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6594:
---
Fix Version/s: 1.7.9
> UpgradeIT produces unwanted output
> --
>
> Key: OAK-6594
> URL: https://issues.apache.org/jira/browse/OAK-6594
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Michael Dürig
>Priority: Minor
> Fix For: 1.8, 1.7.9
>
>
> When {{UpgradeIT}} is executed, the following output is produced.
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@75e01201
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@75e01201
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@75e01201
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ...
[jira] [Updated] (OAK-6641) test failure in org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT
[
https://issues.apache.org/jira/browse/OAK-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6641:
---
Fix Version/s: 1.7.8
> test failure in
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT
>
>
> Key: OAK-6641
> URL: https://issues.apache.org/jira/browse/OAK-6641
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar, tarmk-standby
>Reporter: Julian Reschke
>Assignee: Andrei Dulceanu
> Labels: cold-standby
> Fix For: 1.8, 1.7.8
>
>
> {noformat}
> Tests run: 10, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 99.858 sec
> <<< FAILURE! - in
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT
> testSyncBigBlob(org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT)
> Time elapsed: 71.122 sec <<< ERROR!
> java.lang.RuntimeException: Error occurred while obtaining InputStream for
> blobId
> [8098b6ac1491be80b7e58a85767ede178c432866d90caf6726f556406ecc84a4#1073741824]
> Caused by: java.io.IOException:
> org.apache.jackrabbit.core.data.DataStoreException: Record
> 8098b6ac1491be80b7e58a85767ede178c432866d90caf6726f556406ecc84a4 does not
> exist
> Caused by: org.apache.jackrabbit.core.data.DataStoreException: Record
> 8098b6ac1491be80b7e58a85767ede178c432866d90caf6726f556406ecc84a4 does not
> exist
> {noformat}
> (might be specific to Windows)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (OAK-6594) UpgradeIT produces unwanted output
[
https://issues.apache.org/jira/browse/OAK-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig reassigned OAK-6594:
--
Assignee: Michael Dürig
> UpgradeIT produces unwanted output
> --
>
> Key: OAK-6594
> URL: https://issues.apache.org/jira/browse/OAK-6594
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Michael Dürig
>Priority: Minor
> Fix For: 1.8, 1.7.9
>
>
> When {{UpgradeIT}} is executed, the following output is produced.
> {noformat}
> Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@75e01201
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@75e01201
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... }, node-5-8 = { ... }, node-5-5 = { ... }, node-5-0
> = { ... }, node-5-6 = { ... } }
> Apache Jackrabbit Oak 1.6.1
> ===> true
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook
> ===> org.apache.jackrabbit.oak.plugins.document.*,
> org.apache.jackrabbit.oak.plugins.segment.*,
> org.apache.jackrabbit.oak.segment.SegmentNodeBuilder,
> org.apache.jackrabbit.oak.spi.commit.EmptyHook,
> org.apache.jackrabbit.oak.spi.commit.CommitInfo
> ===> true
> ===> org.apache.jackrabbit.oak.segment.SegmentNodeStore@75e01201
> ===> SegmentNodeBuilder{path=/}
> ===> null
> ===> { property-name-5-0 = property-value-5-0, property-name-5-1 =
> property-value-5-1, property-name-5-2 = property-value-5-2, property-name-5-3
> = property-value-5-3, property-name-5-4 = property-value-5-4,
> property-name-5-5 = property-value-5-5, property-name-5-6 =
> property-value-5-6, property-name-5-7 = property-value-5-7, property-name-5-8
> = property-value-5-8, property-name-5-9 = property-value-5-9, node-5-3 = {
> ... }, node-5-4 = { ... }, node-5-9 = { ... }, node-5-1 = { ... }, node-5-2 =
> { ... }, node-5-7 = { ... },
[jira] [Updated] (OAK-6397) Move record implementations to their own package
[
https://issues.apache.org/jira/browse/OAK-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6397:
---
Fix Version/s: (was: 1.8)
> Move record implementations to their own package
>
>
> Key: OAK-6397
> URL: https://issues.apache.org/jira/browse/OAK-6397
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>
> Given the work done for OAK-6378, it is now possible to move the record
> implementation to their own package. These implementations can be implemented
> on top of the {{SegmentReader}}, {{SegmentWriter}} and {{BlobStore}}
> interfaces, and detached from other implementation classes from the
> {{o.a.j.o.segment}} package. I have already started working in [this
> branch|https://github.com/francescomari/jackrabbit-oak/tree/record-package]
> in GitHub.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6312) Unify NodeStore/DataStore configurations
[ https://issues.apache.org/jira/browse/OAK-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-6312: --- Fix Version/s: (was: 1.8) > Unify NodeStore/DataStore configurations > > > Key: OAK-6312 > URL: https://issues.apache.org/jira/browse/OAK-6312 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: blob, blob-plugins, composite, documentmk, rdbmk, > segment-tar >Reporter: Arek Kita > > I've noticed recently that with many different NodeStore > implementation (Segment, Document, Composite) but also DataStore > implementation (File, S3, Azure) and some composite ones like > (Hierarchical, Federated) it > becomes more and more difficult to set up everything correctly and be > able to know the current persistence state of repository (especially > with pretty aged repos). The factory code/required options are more complex > not only from user perspective but also from maintenance point. > We should have the same means of *describing* layouts of Oak repository no > matter if it is simple or more layered/composite instance. > Some work has already been done in scope of OAK-6210 so I guess we have good > foundations to continue working in that direction. > /cc [~mattvryan], [~chetanm] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5786) Memory based FileStore bootstrap
[ https://issues.apache.org/jira/browse/OAK-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-5786: --- Fix Version/s: (was: 1.8) > Memory based FileStore bootstrap > > > Key: OAK-5786 > URL: https://issues.apache.org/jira/browse/OAK-5786 > Project: Jackrabbit Oak > Issue Type: New Feature > Components: segment-tar >Reporter: Alex Deparvu >Assignee: Alex Deparvu > > A memory-based FileStore boot would reduce IO to zero (or as close as > possible) and provide more insight into the code bottlenecks (locks, > concurrency control, etc). > A very basic idea (with minimal changes to current code) is to boot a > FileStore that would > * disable mmaping > * have an unbounded segment cache (and/or other caches), with no size checks > * eagerly load all application state in memory on startup > * optionally flush everything to disk on shutdown only so the state is > persistent -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5521) CommunicationObserver and its MBeans need proper synchronization
[
https://issues.apache.org/jira/browse/OAK-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-5521:
---
Fix Version/s: 1.7.9
> CommunicationObserver and its MBeans need proper synchronization
>
>
> Key: OAK-5521
> URL: https://issues.apache.org/jira/browse/OAK-5521
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
> Fix For: 1.8, 1.7.9
>
>
> The {{CommunicationObserver}} used in Cold Standby might be called
> concurrently by multiple threads. The implementation of
> {{CommunicationObserver}} doesn't currently use any form of synchronization
> to protect its state.
> Moreover, the MBeans published by the {{CommunicationObserver}} might be
> concurrently read via JMX and updated via the {{CommunicationObserver}}. As
> such, further synchronization is also needed in the MBeans to protect
> concurrent access to shared data.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5103) Backup is not incremental i.e. previous tar files are duplicated
[
https://issues.apache.org/jira/browse/OAK-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-5103:
---
Fix Version/s: (was: 1.8)
> Backup is not incremental i.e. previous tar files are duplicated
>
>
> Key: OAK-5103
> URL: https://issues.apache.org/jira/browse/OAK-5103
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Affects Versions: 1.5.12
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Labels: operations, production, tooling
>
> Performing two backups via {{RepositoryManagementMBean.startBackup}},
> directory size increases not only with the delta, but also again with the
> size of existing tar files. This lead me to the conclusion that backup is not
> incremental.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-1576) SegmentMK: Implement refined conflict resolution for addExistingNode conflicts
[ https://issues.apache.org/jira/browse/OAK-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-1576: --- Fix Version/s: (was: 1.8) > SegmentMK: Implement refined conflict resolution for addExistingNode conflicts > -- > > Key: OAK-1576 > URL: https://issues.apache.org/jira/browse/OAK-1576 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: segment-tar >Reporter: Michael Dürig >Assignee: Michael Dürig > Labels: concurrency, resilience, scalability > > Implement refined conflict resolution for addExistingNode conflicts as > defined in the parent issue for the SegementMK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-1264) Avoid duplicating shared content in backup
[
https://issues.apache.org/jira/browse/OAK-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-1264:
---
Fix Version/s: (was: 1.8)
> Avoid duplicating shared content in backup
> --
>
> Key: OAK-1264
> URL: https://issues.apache.org/jira/browse/OAK-1264
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Reporter: Jukka Zitting
> Labels: backup, operations
>
> The backup feature from OAK-1159 is currently unable to detect cases where
> the same binary or some other piece of shared content is referenced from two
> or more places in the content tree, and ends up duplicating such content in
> the backup.
> It would be nice if the backup could automatically detect such cases and
> avoid the extra duplicates. See the {{testSharedContent}} test case in
> {{FileStoreBackupTest}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5506) Segment store apparently doesn't round trip node names with unpaired surrogates
[
https://issues.apache.org/jira/browse/OAK-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-5506:
---
Fix Version/s: (was: 1.8)
> Segment store apparently doesn't round trip node names with unpaired
> surrogates
> ---
>
> Key: OAK-5506
> URL: https://issues.apache.org/jira/browse/OAK-5506
> Project: Jackrabbit Oak
> Issue Type: Wish
> Components: segment-tar
>Affects Versions: 1.5.18
>Reporter: Julian Reschke
>Assignee: Francesco Mari
>Priority: Minor
> Attachments: OAK-5506-01.patch, OAK-5506-02.patch,
> OAK-5506-name-conversion.diff, ValidNamesTest.java
>
>
> Apparently, the following node name is accepted:
>{{"foo\ud800"}}
> but a subsequent {{getPath()}} call fails:
> {noformat}
> javax.jcr.InvalidItemStateException: This item [/test_node/foo?] does not
> exist anymore
> at
> org.apache.jackrabbit.oak.jcr.delegate.ItemDelegate.checkAlive(ItemDelegate.java:86)
> at
> org.apache.jackrabbit.oak.jcr.session.operation.ItemOperation.checkPreconditions(ItemOperation.java:34)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.prePerform(SessionDelegate.java:615)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:205)
> at
> org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:112)
> at
> org.apache.jackrabbit.oak.jcr.session.ItemImpl.getPath(ItemImpl.java:140)
> at
> org.apache.jackrabbit.oak.jcr.session.NodeImpl.getPath(NodeImpl.java:106)
> at
> org.apache.jackrabbit.oak.jcr.ValidNamesTest.nameTest(ValidNamesTest.java:271)
> at
> org.apache.jackrabbit.oak.jcr.ValidNamesTest.testUnpairedSurrogate(ValidNamesTest.java:259)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source){noformat}
> (test case follows)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-4582) Split Segment in a read-only and a read-write implementations
[
https://issues.apache.org/jira/browse/OAK-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-4582:
---
Fix Version/s: (was: 1.8)
> Split Segment in a read-only and a read-write implementations
> -
>
> Key: OAK-4582
> URL: https://issues.apache.org/jira/browse/OAK-4582
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
> Labels: technical_debt
> Attachments: benchmark-01.png, benchmark-01.txt
>
>
> {{Segment}} is central to the working of the Segment Store, but it currently
> serves two purposes:
> # It is a temporary storage location for the currently written segment,
> waiting to be full and flushed to disk.
> # It is a way to parse serialzed segments read from disk.
> To distinguish these two use cases, I suggest to promote {{Segment}} to the
> status of interface, and to create two different implementations for a
> read-only and a read-write segments.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-4104) Refactor reading records from segments
[
https://issues.apache.org/jira/browse/OAK-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-4104:
---
Fix Version/s: (was: 1.8)
> Refactor reading records from segments
> --
>
> Key: OAK-4104
> URL: https://issues.apache.org/jira/browse/OAK-4104
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: segment-tar
>Reporter: Michael Dürig
> Labels: technical_debt
>
> We should refactor how records (e.g. node states) are read from segments.
> Currently this is scattered and replicated across various places. All of
> which hard coding certain indexes into a byte buffer (see calls to
> {{Record.getOffset}} for how bad this is).
> The current implementation makes it very hard to maintain the code and evolve
> the segment format. We should optimally have one place per segment version
> defining the format as a single source of truth which is then reused by the
> various parts in of the SegmentMK, tooling and tests.
> We should also evaluate 3rd party data serialisation libraries, which could
> make our lives easier. Focus should be on ease of use, separation of concerns
> (schema vs. implementation), compactness of format, efficient en/decoding,
> support for schema evolution. Possible candidates include [protocol
> buffers|https://developers.google.com/protocol-buffers/] and [Apache
> Avro|http://avro.apache.org/].
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-4866) Design and implement a proper backup and restore API
[
https://issues.apache.org/jira/browse/OAK-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-4866:
---
Fix Version/s: (was: 1.8)
> Design and implement a proper backup and restore API
>
>
> Key: OAK-4866
> URL: https://issues.apache.org/jira/browse/OAK-4866
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Reporter: Francesco Mari
>Priority: Minor
> Labels: operations, production
>
> The current backup and restore API in {{org.apache.jackrabbit.oak.backup}}
> refers to classes and interfaces that should remain private to the
> oak-segment-tar bundle. This, in fact, is the reason why that package was not
> exported as part of the effort for OAK-4843. The current backup and restore
> API should be redesigned to be used from the outside of oak-segment-tar
> without exporting implementation details.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-4994) Implement additional record types
[ https://issues.apache.org/jira/browse/OAK-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161104#comment-16161104 ] Michael Dürig commented on OAK-4994: Linking to OAK-6584 as the additional record types are likely most useful for record level tooling. > Implement additional record types > - > > Key: OAK-4994 > URL: https://issues.apache.org/jira/browse/OAK-4994 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Francesco Mari > Labels: tooling > > The records written in the segment store should be augmented with additional > types. In OAK-2498 the following additional types were identified: > - List of property names. A list of strings, where every string is a property > name, is referenced by the template record. > - List of list of values. This list is pointed to by the node record and > contains the values for single\- and multi\- value properties of that node. > The double indirection is needed to support multi-value properties. > - Map from string to node. This map is referenced by the template and > represents the child relationship between nodes. > - Super root. This is a marker type identifying top-level records for the > repository super-roots. > Just adding these types doesn't improve the situation for the segment store, > though. Bucket and block records are not easily parseable because they have a > variable length and their size is not specified in the record value itself. > For record types to be used effectively, the way we serialize certain kind of > data has to be reviewed for further improvements. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-4103) Replace journal.log with an in place journal
[
https://issues.apache.org/jira/browse/OAK-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-4103:
---
Fix Version/s: (was: 1.8)
> Replace journal.log with an in place journal
>
>
> Key: OAK-4103
> URL: https://issues.apache.org/jira/browse/OAK-4103
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: segment-tar
>Reporter: Michael Dürig
>Assignee: Andrei Dulceanu
>Priority: Minor
> Labels: resilience
>
> Instead of writing the current head revision to the {{journal.log}} file we
> could make it an integral part of the node states: as OAK-3804 demonstrates
> we already have very good heuristics to reconstruct a lost journal. If we add
> the right annotations to the root node states this could replace the current
> approach. The latter is problematic as it relies on the flush thread properly
> and timely updating {{journal.log}}. See e.g. OAK-3303.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-4994) Implement additional record types
[ https://issues.apache.org/jira/browse/OAK-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-4994: --- Fix Version/s: (was: 1.8) > Implement additional record types > - > > Key: OAK-4994 > URL: https://issues.apache.org/jira/browse/OAK-4994 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Francesco Mari > Labels: tooling > > The records written in the segment store should be augmented with additional > types. In OAK-2498 the following additional types were identified: > - List of property names. A list of strings, where every string is a property > name, is referenced by the template record. > - List of list of values. This list is pointed to by the node record and > contains the values for single\- and multi\- value properties of that node. > The double indirection is needed to support multi-value properties. > - Map from string to node. This map is referenced by the template and > represents the child relationship between nodes. > - Super root. This is a marker type identifying top-level records for the > repository super-roots. > Just adding these types doesn't improve the situation for the segment store, > though. Bucket and block records are not easily parseable because they have a > variable length and their size is not specified in the record value itself. > For record types to be used effectively, the way we serialize certain kind of > data has to be reviewed for further improvements. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-4558) SegmentNodeState.fastEquals() can trigger two I/O operations
[
https://issues.apache.org/jira/browse/OAK-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-4558:
---
Fix Version/s: (was: 1.8)
> SegmentNodeState.fastEquals() can trigger two I/O operations
>
>
> Key: OAK-4558
> URL: https://issues.apache.org/jira/browse/OAK-4558
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Minor
> Labels: performance
>
> The implementation of {{SegmentNodeState.fastEquals()}} compares the stable
> IDs of two instances of {{SegmentNodeState}}. In some cases, reading the
> stable ID would trigger a read of an additional record, the block record
> containing the serialized version of the segment ID.
> This issue is about evaluating the performance implications of this strategy
> and, in particular, if it would be better to store the serialized stable ID
> in the node record itself.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-3893) SegmentWriter records cache could use thinner keys
[
https://issues.apache.org/jira/browse/OAK-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-3893:
---
Fix Version/s: (was: 1.8)
> SegmentWriter records cache could use thinner keys
> --
>
> Key: OAK-3893
> URL: https://issues.apache.org/jira/browse/OAK-3893
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Reporter: Alex Deparvu
>Assignee: Alex Deparvu
>Priority: Minor
> Labels: performance
> Attachments: OAK-3893.patch
>
>
> The SegmentWriter keeps a records deduplication cache ('records' map) that
> maintains 2 types of mappings:
> * template -> recordid
> * strings -> recordid
> For the first one (template-> recordid) we can come up with a thinner
> representation of a template (a hash function that is fast and not very
> collision prone) so we don't have to keep a reference to each template object.
> Same applies for second one, similar to what is happening in the StringsCache
> now, we could keep the string value up to a certain size and beyond that,
> hash it and use that for the deduplication map.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-4649) Move index files outside of the TAR files
[ https://issues.apache.org/jira/browse/OAK-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-4649: --- Fix Version/s: (was: 1.8) > Move index files outside of the TAR files > - > > Key: OAK-4649 > URL: https://issues.apache.org/jira/browse/OAK-4649 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Francesco Mari >Assignee: Francesco Mari > Labels: technical_debt > > TAR files currently embed three indexes: an index of the segments contained > in the TAR files, a graph index and an index of external binary references. > Index files are checked for consistency purposes at the startup of the > system. Normally, if an index file is corrupted it is recreated. Since the > index file is contained inside the TAR file, recreating them implies > rewriting the whole TAR file and appending the new index. > This process creates unnecessary backups, since the biggest part of the TAR > file is effectively immutable. Moreover, because index files are stored in > the TAR files, we can't treat TAR files as true read-only files. There is > always the possibility that they have to be opened again in write mode for > the recovery of the index file. > I propose to move those index files outside of the TAR files. TAR files will > end up being truly read-only files containing immutable data, and index files > will be granted their own physical files on the file system. Being index > files derived data, they now can be recreated at will without impacting the > read-only part of the segment store. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5859) Analyse and reduce IO amplification by OS
[ https://issues.apache.org/jira/browse/OAK-5859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-5859: --- Fix Version/s: (was: 1.7.8) > Analyse and reduce IO amplification by OS > - > > Key: OAK-5859 > URL: https://issues.apache.org/jira/browse/OAK-5859 > Project: Jackrabbit Oak > Issue Type: Task > Components: segment-tar >Reporter: Michael Dürig > Fix For: 1.8 > > > Certain operation system settings might result in too much data actually > being read from disk causing early setting on of thrashing. E.g. transparent > huge pages or too big read aheads might be contra productive in combination > with the TarMKs memory mapping model. > * Determine the ratio of data being read by the TarMK and actual data being > read from disk. Determine the impact of relevant OS parameters (e.g. > transparent huge pages) on this ratio. > * Compare memory mapped mode with file IO mode with an accordingly increased > segment cache. This would move prediction of what is likely to be read next > from the OS layer into our segment cache eviction strategy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5655) TarMK: Analyse locality of reference
[ https://issues.apache.org/jira/browse/OAK-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-5655: --- Fix Version/s: (was: 1.7.8) > TarMK: Analyse locality of reference > - > > Key: OAK-5655 > URL: https://issues.apache.org/jira/browse/OAK-5655 > Project: Jackrabbit Oak > Issue Type: Task > Components: segment-tar >Reporter: Michael Dürig > Labels: scalability > Fix For: 1.8 > > Attachments: segment-per-path-compacted-nocache.png, > segment-per-path-compacted-nostringcache.png, segment-per-path-compacted.png, > segment-per-path.png > > > We need to better understand the locality aspects of content stored in TarMK: > * How is related content spread over segments? > * What content do we consider related? > * How does locality of related content develop over time when changes are > applied? > * What changes do we consider typical? > * What is the impact of compaction on locality? > * What is the impact of the deduplication caches on locality (during normal > operation and during compaction)? > * How good are checkpoints deduplicated? Can we monitor this online? > * ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6371) Implement better tools for reparing a corrupt repository
[
https://issues.apache.org/jira/browse/OAK-6371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig resolved OAK-6371.
Resolution: Duplicate
Fix Version/s: (was: 1.7.9)
(was: 1.8)
> Implement better tools for reparing a corrupt repository
> -
>
> Key: OAK-6371
> URL: https://issues.apache.org/jira/browse/OAK-6371
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core, segment-tar
>Reporter: Michael Dürig
> Labels: tooling
>
> In a recent customer case we had the requirement to remove corrupted nodes
> from a repository (instead of rolling it back via {{oak-run check}} and
> subsequently editing the {{journal.log}}. The current ad-hoc way of doing so
> is via the
> [rmNode|https://gist.githubusercontent.com/stillalex/43c49af065e3dd1fd5bf/raw/9e726a59f75b46e7b474f7ac763b0888d5a3f0c3/rmNode.groovy]
> Groovy script. Since in that case the corrupted nodes where inside a
> checkpoint we couldn't use this approach though.
> Going forward we should implement more robust tooling around this use case:
> * Remove corrupt nodes and properties and log their path
> * Copy the repository (head state) to a new repository skipping all corrupt
> nodes and properties while logging their path.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5860) Compressed segments
[ https://issues.apache.org/jira/browse/OAK-5860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-5860: --- Fix Version/s: (was: 1.7.8) > Compressed segments > --- > > Key: OAK-5860 > URL: https://issues.apache.org/jira/browse/OAK-5860 > Project: Jackrabbit Oak > Issue Type: New Feature > Components: segment-tar >Reporter: Michael Dürig >Assignee: Andrei Dulceanu > Labels: scalability > Fix For: 1.8 > > > It would be interesting to see the effect of compressing the segments within > the tar files with a sufficiently effective and performant compression > algorithm: > * Can we increase overall throughput by trading CPU for IO? > * Can we scale to bigger repositories (in number of nodes) by squeezing in > more segments per MB and thus pushing out onset of thrashing? > * What would be a good compression algorithm/library? > * Can/should we make this optional? > * Migration and compatibility issues? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5792) TarMK: Implement tooling to repair broken nodes
[
https://issues.apache.org/jira/browse/OAK-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-5792:
---
Fix Version/s: 1.7.9
> TarMK: Implement tooling to repair broken nodes
> ---
>
> Key: OAK-5792
> URL: https://issues.apache.org/jira/browse/OAK-5792
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: segment-tar
>Reporter: Michael Dürig
>Assignee: Andrei Dulceanu
> Labels: production, tooling
> Fix For: 1.8, 1.7.9
>
>
> With {{oak-run check}} we can determine the last good revision of a
> repository and use it to manually roll back a corrupted segment store.
> Complementary to this we should implement a tool to roll forward a broken
> revision to a fixed new revision. Such a tool needs to detect which items are
> affected by a corruption and replace these items with markers. With this the
> repository could brought back online and the markers could be used to
> identify the locations in the tree where further manual action might be
> needed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OAK-6544) Enable active blob deletion feature by default
[ https://issues.apache.org/jira/browse/OAK-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Saurabh resolved OAK-6544. Resolution: Fixed Fix Version/s: 1.7.8 Set default interval for 12 hours in trunk at [r1808015|https://svn.apache.org/r1808015]. > Enable active blob deletion feature by default > -- > > Key: OAK-6544 > URL: https://issues.apache.org/jira/browse/OAK-6544 > Project: Jackrabbit Oak > Issue Type: Task > Components: lucene >Affects Versions: 1.7.1 >Reporter: Vikas Saurabh >Assignee: Vikas Saurabh > Fix For: 1.8, 1.7.8 > > > OAK-2808 allows for active deletion of blobs created by lucene indexing. > Currently, the feature is disabled by default. This task is to track enabling > it by default before doing stable release of the feature. > About the default enabled value: I think default interval to purge blobs can > be 6 hours be default. (Note, the purge logic, anyway won't purge blobs which > were deleted in recent past... 'recent'=24hours \[configurable via jvm > param]). > /cc [~chetanm] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OAK-5635) Revisit FileStoreStats mbean stats format
[ https://issues.apache.org/jira/browse/OAK-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig reassigned OAK-5635: -- Assignee: Michael Dürig > Revisit FileStoreStats mbean stats format > - > > Key: OAK-5635 > URL: https://issues.apache.org/jira/browse/OAK-5635 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Alex Deparvu >Assignee: Michael Dürig > Labels: monitoring > Fix For: 1.8, 1.7.9 > > > This is a bigger refactoring item to revisit the format of the exposed data, > moving towards having it in a more machine consumable friendly format. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6646) Make it possible to set timeouts in Solr index connections
Tommaso Teofili created OAK-6646: Summary: Make it possible to set timeouts in Solr index connections Key: OAK-6646 URL: https://issues.apache.org/jira/browse/OAK-6646 Project: Jackrabbit Oak Issue Type: Improvement Components: solr Reporter: Tommaso Teofili Assignee: Tommaso Teofili Fix For: 1.8 Currently socket and connection timeouts for remote Solr clients are not configurable. However in some environments, e.g. with proxies / load balancers in front or having network latencies, it'd be useful to be able to tweak such timeouts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6645) 1.7.7 release fails on javadoc
[
https://issues.apache.org/jira/browse/OAK-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella resolved OAK-6645.
---
Resolution: Fixed
> 1.7.7 release fails on javadoc
> --
>
> Key: OAK-6645
> URL: https://issues.apache.org/jira/browse/OAK-6645
> Project: Jackrabbit Oak
> Issue Type: Bug
>Reporter: Davide Giannella
>Assignee: Davide Giannella
>Priority: Blocker
> Fix For: 1.8, 1.7.7
>
>
> {noformat}
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:101:
> error: reference not found
> [INFO] [ERROR] * @see
> org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder
> [INFO] [ERROR] ^
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:115:
> error: reference not found
> [INFO] [ERROR] * @see
> org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder#copy(NodeStore,
> NodeStore)
> ...
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/writer/CommitMitigatingTieredMergePolicy.java:201:
> error: bad use of '>'
> [INFO] [ERROR] * NOTE: this value should be >= the {@link
> [INFO] [ERROR] ^
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/writer/CommitMitigatingTieredMergePolicy.java:45:
> error: bad use of '>'
> [INFO] [ERROR] /** Default noCFSRatio. If a merge's size is >= 10% of
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (OAK-6645) 1.7.7 release fails on javadoc
[
https://issues.apache.org/jira/browse/OAK-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161036#comment-16161036
]
Davide Giannella edited comment on OAK-6645 at 9/11/17 10:35 AM:
-
In trunk at
- http://svn.apache.org/r1808006
- http://svn.apache.org/r1808010
was (Author: edivad):
In trunk at http://svn.apache.org/r1808006
> 1.7.7 release fails on javadoc
> --
>
> Key: OAK-6645
> URL: https://issues.apache.org/jira/browse/OAK-6645
> Project: Jackrabbit Oak
> Issue Type: Bug
>Reporter: Davide Giannella
>Assignee: Davide Giannella
>Priority: Blocker
> Fix For: 1.8, 1.7.7
>
>
> {noformat}
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:101:
> error: reference not found
> [INFO] [ERROR] * @see
> org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder
> [INFO] [ERROR] ^
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:115:
> error: reference not found
> [INFO] [ERROR] * @see
> org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder#copy(NodeStore,
> NodeStore)
> ...
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/writer/CommitMitigatingTieredMergePolicy.java:201:
> error: bad use of '>'
> [INFO] [ERROR] * NOTE: this value should be >= the {@link
> [INFO] [ERROR] ^
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/writer/CommitMitigatingTieredMergePolicy.java:45:
> error: bad use of '>'
> [INFO] [ERROR] /** Default noCFSRatio. If a merge's size is >= 10% of
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6645) 1.7.7 release fails on javadoc
[
https://issues.apache.org/jira/browse/OAK-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6645:
--
Description:
{noformat}
[INFO] [ERROR]
/work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:101:
error: reference not found
[INFO] [ERROR] * @see
org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder
[INFO] [ERROR] ^
[INFO] [ERROR]
/work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:115:
error: reference not found
[INFO] [ERROR] * @see
org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder#copy(NodeStore,
NodeStore)
...
[INFO] [ERROR]
/work/sources/apache/releases/oak-svn-trunk/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/writer/CommitMitigatingTieredMergePolicy.java:201:
error: bad use of '>'
[INFO] [ERROR] * NOTE: this value should be >= the {@link
[INFO] [ERROR] ^
[INFO] [ERROR]
/work/sources/apache/releases/oak-svn-trunk/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/writer/CommitMitigatingTieredMergePolicy.java:45:
error: bad use of '>'
[INFO] [ERROR] /** Default noCFSRatio. If a merge's size is >= 10% of
{noformat}
was:
{noformat}
[INFO] [ERROR]
/work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:101:
error: reference not found
[INFO] [ERROR] * @see
org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder
[INFO] [ERROR] ^
[INFO] [ERROR]
/work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:115:
error: reference not found
[INFO] [ERROR] * @see
org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder#copy(NodeStore,
NodeStore)
{noformat}
> 1.7.7 release fails on javadoc
> --
>
> Key: OAK-6645
> URL: https://issues.apache.org/jira/browse/OAK-6645
> Project: Jackrabbit Oak
> Issue Type: Bug
>Reporter: Davide Giannella
>Assignee: Davide Giannella
>Priority: Blocker
> Fix For: 1.8, 1.7.7
>
>
> {noformat}
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:101:
> error: reference not found
> [INFO] [ERROR] * @see
> org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder
> [INFO] [ERROR] ^
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:115:
> error: reference not found
> [INFO] [ERROR] * @see
> org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder#copy(NodeStore,
> NodeStore)
> ...
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/writer/CommitMitigatingTieredMergePolicy.java:201:
> error: bad use of '>'
> [INFO] [ERROR] * NOTE: this value should be >= the {@link
> [INFO] [ERROR] ^
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/writer/CommitMitigatingTieredMergePolicy.java:45:
> error: bad use of '>'
> [INFO] [ERROR] /** Default noCFSRatio. If a merge's size is >= 10% of
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (OAK-6645) 1.7.7 release fails on javadoc
[
https://issues.apache.org/jira/browse/OAK-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella reopened OAK-6645:
---
> 1.7.7 release fails on javadoc
> --
>
> Key: OAK-6645
> URL: https://issues.apache.org/jira/browse/OAK-6645
> Project: Jackrabbit Oak
> Issue Type: Bug
>Reporter: Davide Giannella
>Assignee: Davide Giannella
>Priority: Blocker
> Fix For: 1.8, 1.7.7
>
>
> {noformat}
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:101:
> error: reference not found
> [INFO] [ERROR] * @see
> org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder
> [INFO] [ERROR] ^
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:115:
> error: reference not found
> [INFO] [ERROR] * @see
> org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder#copy(NodeStore,
> NodeStore)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6645) 1.7.7 release fails on javadoc
[
https://issues.apache.org/jira/browse/OAK-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161036#comment-16161036
]
Davide Giannella commented on OAK-6645:
---
In trunk at http://svn.apache.org/r1808006
> 1.7.7 release fails on javadoc
> --
>
> Key: OAK-6645
> URL: https://issues.apache.org/jira/browse/OAK-6645
> Project: Jackrabbit Oak
> Issue Type: Bug
>Reporter: Davide Giannella
>Assignee: Davide Giannella
>Priority: Blocker
> Fix For: 1.8, 1.7.7
>
>
> {noformat}
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:101:
> error: reference not found
> [INFO] [ERROR] * @see
> org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder
> [INFO] [ERROR] ^
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:115:
> error: reference not found
> [INFO] [ERROR] * @see
> org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder#copy(NodeStore,
> NodeStore)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OAK-6645) 1.7.7 release fails on javadoc
[
https://issues.apache.org/jira/browse/OAK-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella resolved OAK-6645.
---
Resolution: Fixed
> 1.7.7 release fails on javadoc
> --
>
> Key: OAK-6645
> URL: https://issues.apache.org/jira/browse/OAK-6645
> Project: Jackrabbit Oak
> Issue Type: Bug
>Reporter: Davide Giannella
>Assignee: Davide Giannella
>Priority: Blocker
> Fix For: 1.8, 1.7.7
>
>
> {noformat}
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:101:
> error: reference not found
> [INFO] [ERROR] * @see
> org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder
> [INFO] [ERROR] ^
> [INFO] [ERROR]
> /work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:115:
> error: reference not found
> [INFO] [ERROR] * @see
> org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder#copy(NodeStore,
> NodeStore)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6645) 1.7.7 release fails on javadoc
Davide Giannella created OAK-6645:
-
Summary: 1.7.7 release fails on javadoc
Key: OAK-6645
URL: https://issues.apache.org/jira/browse/OAK-6645
Project: Jackrabbit Oak
Issue Type: Bug
Reporter: Davide Giannella
Assignee: Davide Giannella
Priority: Blocker
Fix For: 1.8, 1.7.7
{noformat}
[INFO] [ERROR]
/work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:101:
error: reference not found
[INFO] [ERROR] * @see
org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder
[INFO] [ERROR] ^
[INFO] [ERROR]
/work/sources/apache/releases/oak-svn-trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/migration/NodeStateCopier.java:115:
error: reference not found
[INFO] [ERROR] * @see
org.apache.jackrabbit.oak.upgrade.nodestate.NodeStateCopier.Builder#copy(NodeStore,
NodeStore)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5975) Document enhancements in Observation in 1.6
[ https://issues.apache.org/jira/browse/OAK-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5975: -- Fix Version/s: (was: 1.7.7) 1.7.8 > Document enhancements in Observation in 1.6 > --- > > Key: OAK-5975 > URL: https://issues.apache.org/jira/browse/OAK-5975 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: doc >Reporter: Chetan Mehrotra > Fix For: 1.8, 1.7.8 > > > This task is meant to collect and refer work done in 1.6 release which needs > to be documented in Oak docs wrt JCR Observation area > * OAK-4796 - filter events before adding to ChangeProcessor's queue > * OAK-5020 - Improved support for node removals > * OAK-5021 - Improve observation of files -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5965) Support path exclusion in secondary nodestore
[ https://issues.apache.org/jira/browse/OAK-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5965: -- Fix Version/s: (was: 1.7.7) 1.7.8 > Support path exclusion in secondary nodestore > - > > Key: OAK-5965 > URL: https://issues.apache.org/jira/browse/OAK-5965 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Labels: secondary-nodestore > Fix For: 1.8, 1.7.8 > > > Secondary NodeStore feature (OAK-4180) for now currently supports path > inclusion. It would be useful to have support for path exclusion also. > Using this a user can can include all content under / but exclude > /oak:index/uuid/:index entries. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5884) Evaluate utility of RepositoryGrowthTest benchmark
[
https://issues.apache.org/jira/browse/OAK-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5884:
--
Fix Version/s: (was: 1.7.7)
1.7.8
> Evaluate utility of RepositoryGrowthTest benchmark
> --
>
> Key: OAK-5884
> URL: https://issues.apache.org/jira/browse/OAK-5884
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: run
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Fix For: 1.8, 1.7.8
>
>
> {{RepositoryGrowthTest}} is a benchmark which makes use of the deprecated
> {{SegmentFixture}}. Since OAK-5834 removes the old {{oak-segment}} module and
> the code associated with it, {{RepositoryGrowthTest}} was also removed. If
> there's value in it, we can adapt it to work with the new
> {{SegmentTarFixture}}.
> /cc [~chetanm]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6582) Review MBean interactions in a composite setup
[ https://issues.apache.org/jira/browse/OAK-6582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6582: -- Fix Version/s: (was: 1.7.7) 1.7.8 > Review MBean interactions in a composite setup > -- > > Key: OAK-6582 > URL: https://issues.apache.org/jira/browse/OAK-6582 > Project: Jackrabbit Oak > Issue Type: Task > Components: composite >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.8 > > > We should validate how the MBeans currently behave in a composite setup, > whether any unwelcome interactions arise due to that, and also see if we need > to add/change MBeans. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6644) Use ReadOnlyNodeBuilder for the read-only mounts
[ https://issues.apache.org/jira/browse/OAK-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6644: -- Fix Version/s: (was: 1.7.7) 1.7.8 > Use ReadOnlyNodeBuilder for the read-only mounts > > > Key: OAK-6644 > URL: https://issues.apache.org/jira/browse/OAK-6644 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: composite >Reporter: Tomek Rękawek > Fix For: 1.8, 1.7.8 > > > Using native node builder (Segment/DocumentNodeBuilder) may be a bit > expensive. Let's try to use ReadOnlyNodeBuilder for the non-default, > read-only mounts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6580) Ensure mounts are consistent with the node type registry
[ https://issues.apache.org/jira/browse/OAK-6580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6580: -- Fix Version/s: (was: 1.7.7) 1.7.8 > Ensure mounts are consistent with the node type registry > > > Key: OAK-6580 > URL: https://issues.apache.org/jira/browse/OAK-6580 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: composite >Reporter: Robert Munteanu >Assignee: Robert Munteanu > Fix For: 1.8, 1.7.8 > > Attachments: > 0001-OAK-6580-Ensure-mounts-are-consistent-with-the-node-.patch > > > When a mount is added, we should make sure that the nodes are: > * defined in the NodeTypeRegistry > * consistent with the node type definitions -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6483) Segment-based composite node store performance degradation
[
https://issues.apache.org/jira/browse/OAK-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6483:
--
Fix Version/s: (was: 1.7.7)
1.7.8
> Segment-based composite node store performance degradation
> --
>
> Key: OAK-6483
> URL: https://issues.apache.org/jira/browse/OAK-6483
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: composite
>Affects Versions: 1.7.4
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
>Priority: Critical
> Fix For: 1.8, 1.7.8
>
>
> It seems that the OAK-4732 is not compatible with the composite node store
> using a segment node store as the main (writeable) store. The OAK-4732
> measures how much does it usually take to apply commit hooks and merge the
> new root. However, the composite node store plugs into the commit hook and
> reads other node store states. As a result, it may take quite a while and the
> measured values are big. They are then used to tune the lock inside the
> LockBasedScheduler#getHeadNodeState() method. Since the times are big, the
> method also waits a long time for the semaphore before it gives up. This
> causes performance degradation.
> The {{-Doak.scheduler.fetch.commitDelayQuantile=0}} parameter can be used to
> disable the OAK-4732.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6579) Define how the counter index works in a composite setup
[ https://issues.apache.org/jira/browse/OAK-6579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-6579: -- Fix Version/s: (was: 1.7.7) 1.7.8 > Define how the counter index works in a composite setup > --- > > Key: OAK-6579 > URL: https://issues.apache.org/jira/browse/OAK-6579 > Project: Jackrabbit Oak > Issue Type: Task > Components: composite, indexing >Reporter: Robert Munteanu >Assignee: Robert Munteanu > Fix For: 1.8, 1.7.8 > > > We need to see if this index can or should be adjusted to work in a composite > environment. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5976) Document enhancements in 1.6 release
[ https://issues.apache.org/jira/browse/OAK-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5976: -- Fix Version/s: (was: 1.7.7) 1.7.8 > Document enhancements in 1.6 release > > > Key: OAK-5976 > URL: https://issues.apache.org/jira/browse/OAK-5976 > Project: Jackrabbit Oak > Issue Type: Documentation > Components: doc >Reporter: Chetan Mehrotra > Fix For: 1.8, 1.7.8 > > > We should document all the enhancement that have been done in Oak 1.6 release > and refer to them in main doc > * 1.6.0 Release Notes - > https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.6.0/RELEASE-NOTES.txt -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5877) Oak upgrade usage note refers to oak-run
[
https://issues.apache.org/jira/browse/OAK-5877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5877:
--
Fix Version/s: (was: 1.7.7)
1.7.8
> Oak upgrade usage note refers to oak-run
>
>
> Key: OAK-5877
> URL: https://issues.apache.org/jira/browse/OAK-5877
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: upgrade
>Reporter: Michael Dürig
>Priority: Minor
> Labels: production, tooling, usability
> Fix For: 1.8, 1.7.8
>
>
> Running {{java -jar oak-upgrade*.jar}} prints
> {noformat}
> Usage: java -jar oak-run-*-jr2.jar upgrade [options] jcr2_source [destination]
>(to upgrade a JCR 2 repository)
>java -jar oak-run-*-jr2.jar upgrade [options] source destination
>(to migrate an Oak repository)
> {noformat}
> Which incorrectly refers to {{oak-run upgrade}}. The latter will send me back
> to {{oak-run}}: "This command was moved to the oak-upgrade module".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6638) Add a composite-prepare command in oak-run
[
https://issues.apache.org/jira/browse/OAK-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-6638:
--
Fix Version/s: (was: 1.7.7)
1.7.8
> Add a composite-prepare command in oak-run
> --
>
> Key: OAK-6638
> URL: https://issues.apache.org/jira/browse/OAK-6638
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run
>Reporter: Robert Munteanu
> Fix For: 1.8, 1.7.8
>
>
> With OAK-6505 we know guard against referenceable nodes placed in mounts.
> These are still allowed with a WARN for certain node types, and currently we
> need to solve the situation of nt:resource nodes placed underneath nt:file
> nodes.
> One way out of this is to use oak:Resource nodes instead of nt:resource, and
> the most contained way of solving this is an oak-run command that can be used
> to convert certain paths from an existing NodeStore to use this pattern.
> The invocation should be something like
> {noformat}java -jar oak-run-1.8-SNAPSHOT.jar composite-prepare
> { | } | } --paths
> /libs,/apps{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5963) Disable S3 proactive caching by default
[ https://issues.apache.org/jira/browse/OAK-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5963: -- Fix Version/s: (was: 1.7.7) 1.7.8 > Disable S3 proactive caching by default > --- > > Key: OAK-5963 > URL: https://issues.apache.org/jira/browse/OAK-5963 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: blob >Reporter: Amit Jain >Assignee: Amit Jain > Labels: candidate_oak_1_2, candidate_oak_1_4, candidate_oak_1_6 > Fix For: 1.8, 1.7.8 > > > The older JR2 CachingDataStore which is extended by S3DataStore enables > proactive caching by default which leads to many binaries being downloaded > twice. This should be disabled by default in Oak. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5998) Clarify and complete missing stuff in current Oak documentation
[ https://issues.apache.org/jira/browse/OAK-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5998: -- Fix Version/s: (was: 1.7.7) 1.7.8 > Clarify and complete missing stuff in current Oak documentation > --- > > Key: OAK-5998 > URL: https://issues.apache.org/jira/browse/OAK-5998 > Project: Jackrabbit Oak > Issue Type: Documentation > Components: doc >Reporter: Chetan Mehrotra > Fix For: 1.8, 1.7.8 > > > Current Oak documentation [1] is missing details around certain aspects of > Oak which makes it difficult for a new person to get up and running and more > important operate Oak in productions easily. Purpose of this task is list out > topic which must be documented to enable easier usage of Oak > * Getting Started - Getting Oak with all features properly is tricky and not > easily possible with our [current getting > started|https://jackrabbit.apache.org/oak/docs/construct.html] specially for > prod setup. > ** Possibly refer or move doc of current examples here > ** For a new user not aware of JCR but aware of document storage a brief > overview on the JCR and how its the api for Oak which is to be used > * Maintenance and Operations - > ** Oak being MVCC storage requires certain maintenance task like RevisionGC > and BlobGC to be run periodically. > ** Then related MBean should be documented. Note some part is covered in > [Segment > docs|https://jackrabbit.apache.org/oak/docs/nodestore/segment/overview.html#garbage-collection] > but we need to complete it for Document and also provide an overview > ** System requirements in terms of RAM due to memory mapped usage, cloned > index files and persistent cache > * How clustering works in Oak - [Clustering > doc|https://jackrabbit.apache.org/oak/docs/clustering.html] should provide > details on > ** how it works > ** importance of background read and background write > ** Effect of eventual consistency in cluster setup > ** Sticky session requirement (as per usecase) > * Observation > ** How it works > ** How external and local events are generated > ** Queue behaviour and overflow > * Clarify requirement from host application wrt > ** scheduling singleton jobs used in Oak and how they should be executed > ** Scheduling maintenance operations via MBeans > * Document various OSGi config - May be generate a doc for all OSGi config in > Oak via some tooling > Note list above is tentative and would be edited to determine important > topics in coming days and then specific sub task can be created to complete > it. Once any list item is completed add (/) against the list entry > [1] https://jackrabbit.apache.org/oak/docs/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5896) fix typo in Not condition handling
[ https://issues.apache.org/jira/browse/OAK-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5896: -- Fix Version/s: (was: 1.7.7) 1.7.8 > fix typo in Not condition handling > -- > > Key: OAK-5896 > URL: https://issues.apache.org/jira/browse/OAK-5896 > Project: Jackrabbit Oak > Issue Type: Bug > Components: query >Affects Versions: 1.6.1 >Reporter: Dave Brosius >Assignee: Dave Brosius >Priority: Trivial > Fix For: 1.8, 1.7.8 > > Attachments: 5896.txt > > > code stutters the same condition twice, looks like a typo. patch attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5763) Improve LockException message on org.apache.jackrabbit.oak.jcr.lock.LockManagerImpl unlock
[
https://issues.apache.org/jira/browse/OAK-5763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5763:
--
Fix Version/s: (was: 1.7.7)
1.7.8
> Improve LockException message on
> org.apache.jackrabbit.oak.jcr.lock.LockManagerImpl unlock
> --
>
> Key: OAK-5763
> URL: https://issues.apache.org/jira/browse/OAK-5763
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
>Affects Versions: 1.3.3
>Reporter: Borja Clemente
> Fix For: 1.8, 1.7.8
>
>
> The error message on LockManagerImpl unlock method could also include
> information about the user attempting to unlock the node as well as the
> actual lock owner.
> Current exception is:
> {code}
> LockException("Not an owner of the lock " + path)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5455) Specify versions for maven plugins used in build for ensuring stable builds
[
https://issues.apache.org/jira/browse/OAK-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5455:
--
Fix Version/s: (was: 1.7.7)
1.7.8
> Specify versions for maven plugins used in build for ensuring stable builds
> ---
>
> Key: OAK-5455
> URL: https://issues.apache.org/jira/browse/OAK-5455
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: parent
>Reporter: Chetan Mehrotra
>Assignee: Julian Reschke
> Fix For: 1.8, 1.7.8
>
> Attachments: enforce.diff, OAK-5455-v1.patch
>
>
> Running a check for plugin versions used in oak build
> {noformat}
> mvn versions:display-plugin-updates
> {noformat}
> leads to following warning
> {noformat}
> [INFO] The following plugin updates are available:
> [INFO] org.apache.felix:maven-scr-plugin .. 1.16.0 -> 1.21.0
> [INFO]
> [WARNING] The following plugins do not have their version specified:
> [WARNING] maven-compiler-plugin .. 2.0.2
> [WARNING] maven-deploy-plugin . (from super-pom) 2.4
> [WARNING] maven-failsafe-plugin . 2.12.4
> [WARNING] maven-jar-plugin . 2.1
> [WARNING] maven-javadoc-plugin . 2.0
> [WARNING] maven-release-plugin . (from super-pom) 2.0-beta-4
> [WARNING] maven-resources-plugin ... 2.2
> [WARNING] maven-surefire-plugin .. 2.4.2
> [INFO]
> [WARNING] Project does not define minimum Maven version, default is: 2.0
> [INFO] Plugins require minimum Maven version of: 3.0.5
> [INFO] Note: the super-pom from Maven 3.3.9 defines some of the plugin
> [INFO] versions and may be influencing the plugins required minimum
> Maven
> [INFO] version.
> [INFO]
> [ERROR] Project does not define required minimum version of Maven.
> [ERROR] Update the pom.xml to contain
> [ERROR]
> [ERROR] 3.0.5
> [ERROR]
> {noformat}
> As a fix we should
> # Specify version for all maven plugin in use
> # Specify minimum version of maven to be used (version used in CI is 3.2.1)
> # Configure enforcer plugin to ensure that in future no plugin is used
> without specifying the version [1]
> [1] http://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5918) Document enhancements in DocumentNodeStore in 1.6
[ https://issues.apache.org/jira/browse/OAK-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-5918: -- Fix Version/s: (was: 1.7.7) 1.7.8 > Document enhancements in DocumentNodeStore in 1.6 > - > > Key: OAK-5918 > URL: https://issues.apache.org/jira/browse/OAK-5918 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: doc >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.8, 1.7.8 > > > This task is meant to collect and refer work done in 1.6 release which needs > to be documented in Oak docs. Specially those enhancements which impact > system administration or new features which need be to enabled as per > requirements should be documented > Issues in documentmk, mongomk, rdbmk > [jql|https://issues.apache.org/jira/issues/?jql=project%20%3D%20OAK%20AND%20fixVersion%20%3D%201.6.0%20and%20component%20in%20(documentmk%2C%20mongomk%2C%20rdbmk)%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC=200] > * OAK-1312 - Bundle nodes into a document (/) > * OAK-4180 - Use another NodeStore as a local cache for a remote Document > store (/) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6640) test failure in ResponseDecoderTest
[
https://issues.apache.org/jira/browse/OAK-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161005#comment-16161005
]
Julian Reschke commented on OAK-6640:
-
trunk: [r1808003|http://svn.apache.org/r1808003]
> test failure in ResponseDecoderTest
> ---
>
> Key: OAK-6640
> URL: https://issues.apache.org/jira/browse/OAK-6640
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Affects Versions: 1.7.6
>Reporter: Julian Reschke
>Assignee: Andrei Dulceanu
> Fix For: 1.8, 1.7.7
>
> Attachments: OAK-6640.diff
>
>
> apparently Windows only
> {noformat}
> [INFO] Running
> org.apache.jackrabbit.oak.segment.standby.codec.ResponseDecoderTest
> [ERROR] Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 0.348 s <<< FAILURE! - in
> org.apache.jackrabbit.oak.segment.standby.codec.ResponseDecoderTest
> [ERROR]
> shouldDecodeValidTwoChunksGetBlobResponses(org.apache.jackrabbit.oak.segment.standby.codec.ResponseDecoderTest)
> Time elapsed: 0.016 s <<< FAILURE!
> java.lang.AssertionError: expected:<4> but was:<7>
> at
> org.apache.jackrabbit.oak.segment.standby.codec.ResponseDecoderTest.shouldDecodeValidTwoChunksGetBlobResponses(ResponseDecoderTest.java:91)
> {noformat}
> First revision showing the bug is 1804512
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OAK-6640) test failure in ResponseDecoderTest
[
https://issues.apache.org/jira/browse/OAK-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved OAK-6640.
-
Resolution: Fixed
Fix Version/s: 1.7.7
Fixed by making sure the test closes the input stream.
> test failure in ResponseDecoderTest
> ---
>
> Key: OAK-6640
> URL: https://issues.apache.org/jira/browse/OAK-6640
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Affects Versions: 1.7.6
>Reporter: Julian Reschke
>Assignee: Andrei Dulceanu
> Fix For: 1.8, 1.7.7
>
> Attachments: OAK-6640.diff
>
>
> apparently Windows only
> {noformat}
> [INFO] Running
> org.apache.jackrabbit.oak.segment.standby.codec.ResponseDecoderTest
> [ERROR] Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 0.348 s <<< FAILURE! - in
> org.apache.jackrabbit.oak.segment.standby.codec.ResponseDecoderTest
> [ERROR]
> shouldDecodeValidTwoChunksGetBlobResponses(org.apache.jackrabbit.oak.segment.standby.codec.ResponseDecoderTest)
> Time elapsed: 0.016 s <<< FAILURE!
> java.lang.AssertionError: expected:<4> but was:<7>
> at
> org.apache.jackrabbit.oak.segment.standby.codec.ResponseDecoderTest.shouldDecodeValidTwoChunksGetBlobResponses(ResponseDecoderTest.java:91)
> {noformat}
> First revision showing the bug is 1804512
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6644) Use ReadOnlyNodeBuilder for the read-only mounts
Tomek Rękawek created OAK-6644: -- Summary: Use ReadOnlyNodeBuilder for the read-only mounts Key: OAK-6644 URL: https://issues.apache.org/jira/browse/OAK-6644 Project: Jackrabbit Oak Issue Type: Improvement Components: composite Reporter: Tomek Rękawek Fix For: 1.8, 1.7.7 Using native node builder (Segment/DocumentNodeBuilder) may be a bit expensive. Let's try to use ReadOnlyNodeBuilder for the non-default, read-only mounts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OAK-6640) test failure in ResponseDecoderTest
[
https://issues.apache.org/jira/browse/OAK-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Dulceanu reassigned OAK-6640:
Assignee: Andrei Dulceanu
> test failure in ResponseDecoderTest
> ---
>
> Key: OAK-6640
> URL: https://issues.apache.org/jira/browse/OAK-6640
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Affects Versions: 1.7.6
>Reporter: Julian Reschke
>Assignee: Andrei Dulceanu
> Fix For: 1.8
>
> Attachments: OAK-6640.diff
>
>
> apparently Windows only
> {noformat}
> [INFO] Running
> org.apache.jackrabbit.oak.segment.standby.codec.ResponseDecoderTest
> [ERROR] Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 0.348 s <<< FAILURE! - in
> org.apache.jackrabbit.oak.segment.standby.codec.ResponseDecoderTest
> [ERROR]
> shouldDecodeValidTwoChunksGetBlobResponses(org.apache.jackrabbit.oak.segment.standby.codec.ResponseDecoderTest)
> Time elapsed: 0.016 s <<< FAILURE!
> java.lang.AssertionError: expected:<4> but was:<7>
> at
> org.apache.jackrabbit.oak.segment.standby.codec.ResponseDecoderTest.shouldDecodeValidTwoChunksGetBlobResponses(ResponseDecoderTest.java:91)
> {noformat}
> First revision showing the bug is 1804512
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (OAK-5772) Test failure: segment.standby.MBeanIT.testClientAndServerEmptyConfig
[ https://issues.apache.org/jira/browse/OAK-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig reassigned OAK-5772: -- Assignee: Andrei Dulceanu (was: Michael Dürig) > Test failure: segment.standby.MBeanIT.testClientAndServerEmptyConfig > > > Key: OAK-5772 > URL: https://issues.apache.org/jira/browse/OAK-5772 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration, segment-tar >Affects Versions: 1.6.0, 1.8 >Reporter: Hudson >Assignee: Andrei Dulceanu > Labels: test-failure, windows > Fix For: 1.8, 1.6.6 > > > Jenkins Windows CI failure: https://builds.apache.org/job/Oak-Win/ > The build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) > 64-bit Windows only,nsfixtures=SEGMENT_TAR,profile=integrationTesting #472 > has failed. > First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited > security) 64-bit Windows > only,nsfixtures=SEGMENT_TAR,profile=integrationTesting > #472|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_TAR,profile=integrationTesting/472/] > [console > log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_TAR,profile=integrationTesting/472/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OAK-5772) Test failure: segment.standby.MBeanIT.testClientAndServerEmptyConfig
[ https://issues.apache.org/jira/browse/OAK-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig reassigned OAK-5772: -- Assignee: Michael Dürig (was: Chetan Mehrotra) > Test failure: segment.standby.MBeanIT.testClientAndServerEmptyConfig > > > Key: OAK-5772 > URL: https://issues.apache.org/jira/browse/OAK-5772 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration, segment-tar >Affects Versions: 1.6.0, 1.8 >Reporter: Hudson >Assignee: Michael Dürig > Labels: test-failure, windows > Fix For: 1.8, 1.6.6 > > > Jenkins Windows CI failure: https://builds.apache.org/job/Oak-Win/ > The build Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited security) > 64-bit Windows only,nsfixtures=SEGMENT_TAR,profile=integrationTesting #472 > has failed. > First failed run: [Oak-Win/Windows slaves=Windows,jdk=JDK 1.8 (unlimited > security) 64-bit Windows > only,nsfixtures=SEGMENT_TAR,profile=integrationTesting > #472|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_TAR,profile=integrationTesting/472/] > [console > log|https://builds.apache.org/job/Oak-Win/Windows%20slaves=Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-bit%20Windows%20only,nsfixtures=SEGMENT_TAR,profile=integrationTesting/472/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OAK-6535) Synchronous Lucene Property Indexes
[
https://issues.apache.org/jira/browse/OAK-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150257#comment-16150257
]
Chetan Mehrotra edited comment on OAK-6535 at 9/11/17 9:29 AM:
---
Feature branch
https://github.com/chetanmeh/jackrabbit-oak/compare/trunk...chetanmeh:OAK-6535
# Add {{PropertyUpdateCallback}} which is invoked for each indexed property
change (/)
# PropertyUpdateCallback based on property index
## For normal index
### Value pattern support (/)
## For unique index
### Check for unique ness constraint (/)
### Store the created time
# Cleanup support
# Query Support
was (Author: chetanm):
Feature branch
https://github.com/chetanmeh/jackrabbit-oak/compare/trunk...chetanmeh:OAK-6535
# Add {{PropertyUpdateCallback}} which is invoked for each indexed property
change (/)
# PropertyUpdateCallback based on property index
## For normal index
### Value pattern support
## For unique index
### Check for unique ness constraint
### Store the created time
# Cleanup support
# Query Support
> Synchronous Lucene Property Indexes
> ---
>
> Key: OAK-6535
> URL: https://issues.apache.org/jira/browse/OAK-6535
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: lucene, property-index
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
> Fix For: 1.8
>
>
> Oak 1.6 added support for Lucene Hybrid Index (OAK-4412). That enables near
> real time (NRT) support for Lucene based indexes. It also had a limited
> support for sync indexes. This feature aims to improve that to next level and
> enable support for sync property indexes.
> More details at
> https://wiki.apache.org/jackrabbit/Synchronous%20Lucene%20Property%20Indexes
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-1905) SegmentMK: Arch segment(s)
[ https://issues.apache.org/jira/browse/OAK-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-1905: --- Fix Version/s: (was: 1.8) > SegmentMK: Arch segment(s) > -- > > Key: OAK-1905 > URL: https://issues.apache.org/jira/browse/OAK-1905 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Jukka Zitting >Priority: Minor > Labels: perfomance, scalability > > There are a lot of constants and other commonly occurring name, values and > other data in a typical repository. To optimize storage space and access > speed, it would be useful to place such data in one or more constant "arch > segments" that are always cached in memory. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6193) IllegalStateException when closing the FileStore during garbage collection
[
https://issues.apache.org/jira/browse/OAK-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6193:
---
Fix Version/s: 1.7.8
> IllegalStateException when closing the FileStore during garbage collection
> --
>
> Key: OAK-6193
> URL: https://issues.apache.org/jira/browse/OAK-6193
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
> Labels: gc
> Fix For: 1.8, 1.7.8
>
>
> When the file store is shut down during gc compaction is properly aborted.
> Afterwards it will trigger a cleanup cycle though, which runs concurrently to
> the proceeding shutdown potentially causing an {{ISE}}:
> {noformat}
> at com.google.common.base.Preconditions.checkState(Preconditions.java:134)
> at org.apache.jackrabbit.oak.segment.file.TarWriter.close(TarWriter.java:333)
> at
> org.apache.jackrabbit.oak.segment.file.TarWriter.createNextGeneration(TarWriter.java:376)
> at
> org.apache.jackrabbit.oak.segment.file.FileStore.newWriter(FileStore.java:682)
> at
> org.apache.jackrabbit.oak.segment.file.FileStore.access$1700(FileStore.java:100)
> at
> org.apache.jackrabbit.oak.segment.file.FileStore$GarbageCollector.cleanup(FileStore.java:1069)
> at
> org.apache.jackrabbit.oak.segment.file.FileStore$GarbageCollector.cleanupGeneration(FileStore.java:1195)
> at
> org.apache.jackrabbit.oak.segment.file.FileStore$GarbageCollector.run(FileStore.java:803)
> at org.apache.jackrabbit.oak.segment.file.FileStore.gc(FileStore.java:387)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6606) Move BulkTransferBenchmark to oak-benchmarks module
[
https://issues.apache.org/jira/browse/OAK-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6606:
---
Fix Version/s: (was: 1.7.7)
1.7.8
> Move BulkTransferBenchmark to oak-benchmarks module
> ---
>
> Key: OAK-6606
> URL: https://issues.apache.org/jira/browse/OAK-6606
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: segment-tar
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Labels: cold-standby
> Fix For: 1.8, 1.7.8
>
>
> {{BulkTransferBenchmark}} should be moved from {{oak-segment-tar}} to
> {{oak-benchmarks}} to allow standard run of this cold standby related
> benchmark.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6615) Add --cold-standby [n] option for Oak-Segment-Tar* fixtures in benchmark mode
[
https://issues.apache.org/jira/browse/OAK-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6615:
---
Fix Version/s: (was: 1.7.7)
1.7.8
> Add --cold-standby [n] option for Oak-Segment-Tar* fixtures in benchmark mode
> -
>
> Key: OAK-6615
> URL: https://issues.apache.org/jira/browse/OAK-6615
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: benchmarks, segment-tar
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Labels: cold-standby
> Fix For: 1.8, 1.7.8
>
>
> It would be nice to have a new option for {{benchmark}} mode in
> {{oak-benchmarks}}, {{--cold-standby [n]}}. This will start a cold standby
> instance, syncing with the primary every {{n}} seconds. All the benchmarks
> specified via {{[testcases]}} argument will be run on primary instance, and
> all statistics and reports will be linked to primary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6643) Return a common format of excerpts independent of the highlighter used
[
https://issues.apache.org/jira/browse/OAK-6643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirk Rudolph updated OAK-6643:
--
Labels: excerpt (was: )
> Return a common format of excerpts independent of the highlighter used
> --
>
> Key: OAK-6643
> URL: https://issues.apache.org/jira/browse/OAK-6643
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
>Affects Versions: 1.6.1
>Reporter: Dirk Rudolph
>Priority: Minor
> Labels: excerpt
>
> While using {{rep:excerpt}} functionality we mentioned that the format of the
> {{PostingsHighlighter}} differs to the one of {{Highlighter}}. See the
> example below:
> {{PostingsHighlighter}}
> {quote}
> [In Central Eastern Europe and Asia Pacific Allianz is one of the
> leading international insurance companies. ]
> {quote}
> {{Highlighter}}
> {quote}
> Life Risk Insurance
> {quote}
> It would be great to have one single format, so that application doesn't have
> to handle those differences.
> Additionally the {{Arrays.toString(...)}} used to generated an excerpt string
> from the {{PostingsHighlighter}} causes the excerpt text to be wrapped in
> "[...]", I guess thats not intended.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6597) rep:excerpt not working for content indexed by aggregation in lucene
[
https://issues.apache.org/jira/browse/OAK-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirk Rudolph updated OAK-6597:
--
Labels: excerpt (was: )
> rep:excerpt not working for content indexed by aggregation in lucene
>
>
> Key: OAK-6597
> URL: https://issues.apache.org/jira/browse/OAK-6597
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
>Affects Versions: 1.6.1, 1.7.6
>Reporter: Dirk Rudolph
> Labels: excerpt
> Fix For: 1.8
>
> Attachments: excerpt-with-aggregation-test.patch
>
>
> I mentioned that properties that got indexed due to an aggregation are not
> considered for excerpts (highlighting) as they are not indexed as stored
> fields.
> See the attached patch that implements a test for excerpts in
> {{LuceneIndexAggregationTest2}}.
> It creates the following structure:
> {code}
> /content/foo [test:Page]
> + bar (String)
> - jcr:content [test:PageContent]
> + bar (String)
> {code}
> where both strings (the _bar_ property at _foo_ and the _bar_ property at
> _jcr:content_) contain different text.
> Afterwards it queries for 2 terms ("tinc*" and "aliq*") that either exist in
> _/content/foo/bar_ or _/content/foo/jcr:content/bar_ but not in both. For the
> former one the excerpt is properly provided for the later one it isn't.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
