[jira] [Commented] (OAK-7446) RDB*Store: update SQLServer JDBC dependency to 6.4.0.jre*
[ https://issues.apache.org/jira/browse/OAK-7446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450334#comment-16450334 ] Julian Reschke commented on OAK-7446: - trunk: [r1830019|http://svn.apache.org/r1830019] > RDB*Store: update SQLServer JDBC dependency to 6.4.0.jre* > - > > Key: OAK-7446 > URL: https://issues.apache.org/jira/browse/OAK-7446 > Project: Jackrabbit Oak > Issue Type: Technical task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_8 > Fix For: 1.10, 1.9.1 > > > And it's even on Maven central! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7446) RDB*Store: update SQLServer JDBC dependency to 6.4.0.jre*
[ https://issues.apache.org/jira/browse/OAK-7446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-7446. - Resolution: Fixed Fix Version/s: 1.9.1 > RDB*Store: update SQLServer JDBC dependency to 6.4.0.jre* > - > > Key: OAK-7446 > URL: https://issues.apache.org/jira/browse/OAK-7446 > Project: Jackrabbit Oak > Issue Type: Technical task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_8 > Fix For: 1.10, 1.9.1 > > > And it's even on Maven central! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7446) RDB*Store: update SQLServer JDBC dependency to 6.4.0.jre*
[ https://issues.apache.org/jira/browse/OAK-7446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7446: Labels: candidate_oak_1_8 (was: ) > RDB*Store: update SQLServer JDBC dependency to 6.4.0.jre* > - > > Key: OAK-7446 > URL: https://issues.apache.org/jira/browse/OAK-7446 > Project: Jackrabbit Oak > Issue Type: Technical task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_8 > Fix For: 1.10, 1.9.1 > > > And it's even on Maven central! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7368) update to findbugs version compatible with jdk 10
[
https://issues.apache.org/jira/browse/OAK-7368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450237#comment-16450237
]
Julian Reschke commented on OAK-7368:
-
Ack.
And yes, disabling it with jdk10 for now may also be a good idea...
> update to findbugs version compatible with jdk 10
> --
>
> Key: OAK-7368
> URL: https://issues.apache.org/jira/browse/OAK-7368
> Project: Jackrabbit Oak
> Issue Type: Task
>Reporter: Alex Deparvu
>Priority: Minor
>
> Warnings running findbugs
> {noformat}
> [INFO] --- findbugs-maven-plugin:3.0.4:findbugs (findbugs) @ oak-commons ---
> [INFO] Fork Value is true
> [java] Warning: Unknown version of Java
> [java] edu.umd.cs.findbugs.JavaVersionException: Could not parse Java
> version string: 10
> [java] at edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:68)
> [java] at
> edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:44)
> [java] at
> edu.umd.cs.findbugs.DetectorFactory.isEnabledForCurrentJRE(DetectorFactory.java:248)
> [java] at
> edu.umd.cs.findbugs.FindBugs.isDetectorEnabled(FindBugs.java:256)
> [java] at edu.umd.cs.findbugs.FindBugs2$3.choose(FindBugs2.java:906)
> [java] at
> edu.umd.cs.findbugs.plan.ExecutionPlan.build(ExecutionPlan.java:179)
> [java] at
> edu.umd.cs.findbugs.FindBugs2.createExecutionPlan(FindBugs2.java:935)
> [java] at edu.umd.cs.findbugs.FindBugs2.execute(FindBugs2.java:241)
> [java] at edu.umd.cs.findbugs.FindBugs.runMain(FindBugs.java:402)
> [java] at edu.umd.cs.findbugs.FindBugs2.main(FindBugs2.java:1200)
> {noformat}
> it seems findbugs-maven-plugin 3.0.5 (latest release) does not fix this and I
> couldn't find an open issue related to java 10.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7368) update to findbugs version compatible with jdk 10
[
https://issues.apache.org/jira/browse/OAK-7368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450177#comment-16450177
]
Alex Deparvu commented on OAK-7368:
---
bq. making the findbugs version depend on the JDK.
maybe I didn't clarify this enough. _no findbugs version_ works on jdk10, the
community seems to have moved to a different project (a fork if you will). do
you mean disable it on jdk10 for now?
> update to findbugs version compatible with jdk 10
> --
>
> Key: OAK-7368
> URL: https://issues.apache.org/jira/browse/OAK-7368
> Project: Jackrabbit Oak
> Issue Type: Task
>Reporter: Alex Deparvu
>Priority: Minor
>
> Warnings running findbugs
> {noformat}
> [INFO] --- findbugs-maven-plugin:3.0.4:findbugs (findbugs) @ oak-commons ---
> [INFO] Fork Value is true
> [java] Warning: Unknown version of Java
> [java] edu.umd.cs.findbugs.JavaVersionException: Could not parse Java
> version string: 10
> [java] at edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:68)
> [java] at
> edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:44)
> [java] at
> edu.umd.cs.findbugs.DetectorFactory.isEnabledForCurrentJRE(DetectorFactory.java:248)
> [java] at
> edu.umd.cs.findbugs.FindBugs.isDetectorEnabled(FindBugs.java:256)
> [java] at edu.umd.cs.findbugs.FindBugs2$3.choose(FindBugs2.java:906)
> [java] at
> edu.umd.cs.findbugs.plan.ExecutionPlan.build(ExecutionPlan.java:179)
> [java] at
> edu.umd.cs.findbugs.FindBugs2.createExecutionPlan(FindBugs2.java:935)
> [java] at edu.umd.cs.findbugs.FindBugs2.execute(FindBugs2.java:241)
> [java] at edu.umd.cs.findbugs.FindBugs.runMain(FindBugs.java:402)
> [java] at edu.umd.cs.findbugs.FindBugs2.main(FindBugs2.java:1200)
> {noformat}
> it seems findbugs-maven-plugin 3.0.5 (latest release) does not fix this and I
> couldn't find an open issue related to java 10.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7446) RDB*Store: update SQLServer JDBC dependency to 6.4.0.jre*
[ https://issues.apache.org/jira/browse/OAK-7446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7446: Fix Version/s: 1.10 > RDB*Store: update SQLServer JDBC dependency to 6.4.0.jre* > - > > Key: OAK-7446 > URL: https://issues.apache.org/jira/browse/OAK-7446 > Project: Jackrabbit Oak > Issue Type: Technical task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.10 > > > And it's even on Maven central! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7446) RDB*Store: update SQLServer JDBC dependency to 6.4.0.jre*
[ https://issues.apache.org/jira/browse/OAK-7446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7446: Affects Version/s: (was: 1.10) > RDB*Store: update SQLServer JDBC dependency to 6.4.0.jre* > - > > Key: OAK-7446 > URL: https://issues.apache.org/jira/browse/OAK-7446 > Project: Jackrabbit Oak > Issue Type: Technical task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.10 > > > And it's even on Maven central! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7444) Allow collection of IOTraces during normal operation
[
https://issues.apache.org/jira/browse/OAK-7444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig resolved OAK-7444.
Resolution: Fixed
Fix Version/s: 1.9.1
Done at [http://svn.apache.org/viewvc?rev=1830012=rev]
IO reads are now logged at debug level using the
{{org.apache.jackrabbit.oak.segment.file.tar.SegmentTarWriter}} logger.
> Allow collection of IOTraces during normal operation
>
>
> Key: OAK-7444
> URL: https://issues.apache.org/jira/browse/OAK-7444
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
>Priority: Major
> Labels: monitoring, tooling
> Fix For: 1.10, 1.9.1
>
>
> The IO tracing facility introduced with OAK-5655 should also be available
> during normal operation. The idea is to log IO reads intercepted via an
> {{IOMonitor}} instance to a logger. If {{DEBUG}} logging is not enabled for
> that logger at the time when the {{FileStore}} is instantiated, then no
> tracing would take place.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OAK-7441) RDB*Store: update DB2 JDBC dependency to 4.19.72
[ https://issues.apache.org/jira/browse/OAK-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-7441. - Resolution: Fixed > RDB*Store: update DB2 JDBC dependency to 4.19.72 > > > Key: OAK-7441 > URL: https://issues.apache.org/jira/browse/OAK-7441 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_8 > Fix For: 1.10, 1.9.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7446) RDB*Store: update SQLServer JDBC dependency to 6.4.0.jre*
Julian Reschke created OAK-7446: --- Summary: RDB*Store: update SQLServer JDBC dependency to 6.4.0.jre* Key: OAK-7446 URL: https://issues.apache.org/jira/browse/OAK-7446 Project: Jackrabbit Oak Issue Type: Technical task Affects Versions: 1.10 Reporter: Julian Reschke Assignee: Julian Reschke And it's even on Maven central! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7445) Introduce a cleanup-first compaction strategy
[ https://issues.apache.org/jira/browse/OAK-7445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-7445. - Resolution: Fixed Fix Version/s: 1.9.1 > Introduce a cleanup-first compaction strategy > - > > Key: OAK-7445 > URL: https://issues.apache.org/jira/browse/OAK-7445 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Francesco Mari >Assignee: Francesco Mari >Priority: Major > Fix For: 1.10, 1.9.1 > > > OAK-7312 validated the feasibility of a strategy where cleanup runs before > the compaction phase. Now that OAK-7377 and follow-up issues allow to define > the garbage collection process in a more modular way, it should be relatively > easy to introduce a new compaction strategy. > The new strategy shouldn't reduce the default compaction strategy. Instead, > the new strategy should be hidden behind a feature flag in oder to exposes it > to power-users for testing purposes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7312) Evaluate the feasibility of running cleanup before compaction
[ https://issues.apache.org/jira/browse/OAK-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450054#comment-16450054 ] Francesco Mari commented on OAK-7312: - For future reference, I attached a patch containing the changes implemented in the GitHub branch referenced by my previous comment. > Evaluate the feasibility of running cleanup before compaction > - > > Key: OAK-7312 > URL: https://issues.apache.org/jira/browse/OAK-7312 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Francesco Mari >Assignee: Francesco Mari >Priority: Major > Attachments: 001.patch > > > Currently cleanup is run only after the compaction phase. Assuming that the > system is configured to retain the default value of two generations, it might > happen that, during the compaction phase, the system will need space for a > third generation, the one being currently compacted. > In order to provide better guarantees on the amount of used disk space, it > should be possible to optimistically perform cleanup before compaction, > getting rid of the oldest generation before a new one is constructed. > This issue tracks the feasibility of this approach, to be validated with a > simple proof of concept. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7312) Evaluate the feasibility of running cleanup before compaction
[ https://issues.apache.org/jira/browse/OAK-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7312: Attachment: 001.patch > Evaluate the feasibility of running cleanup before compaction > - > > Key: OAK-7312 > URL: https://issues.apache.org/jira/browse/OAK-7312 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Francesco Mari >Assignee: Francesco Mari >Priority: Major > Attachments: 001.patch > > > Currently cleanup is run only after the compaction phase. Assuming that the > system is configured to retain the default value of two generations, it might > happen that, during the compaction phase, the system will need space for a > third generation, the one being currently compacted. > In order to provide better guarantees on the amount of used disk space, it > should be possible to optimistically perform cleanup before compaction, > getting rid of the oldest generation before a new one is constructed. > This issue tracks the feasibility of this approach, to be validated with a > simple proof of concept. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7312) Evaluate the feasibility of running cleanup before compaction
[ https://issues.apache.org/jira/browse/OAK-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-7312. - Resolution: Done Fix Version/s: (was: 1.10) Resolving this issue as the feasibility of this new garbage collection strategy has been validated. The implementation has been cleaned up and is committed on trunk per OAK-7445. > Evaluate the feasibility of running cleanup before compaction > - > > Key: OAK-7312 > URL: https://issues.apache.org/jira/browse/OAK-7312 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Francesco Mari >Assignee: Francesco Mari >Priority: Major > > Currently cleanup is run only after the compaction phase. Assuming that the > system is configured to retain the default value of two generations, it might > happen that, during the compaction phase, the system will need space for a > third generation, the one being currently compacted. > In order to provide better guarantees on the amount of used disk space, it > should be possible to optimistically perform cleanup before compaction, > getting rid of the oldest generation before a new one is constructed. > This issue tracks the feasibility of this approach, to be validated with a > simple proof of concept. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7445) Introduce a cleanup-first compaction strategy
[ https://issues.apache.org/jira/browse/OAK-7445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450047#comment-16450047 ] Francesco Mari commented on OAK-7445: - Fixed at r1830010. > Introduce a cleanup-first compaction strategy > - > > Key: OAK-7445 > URL: https://issues.apache.org/jira/browse/OAK-7445 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Francesco Mari >Assignee: Francesco Mari >Priority: Major > Fix For: 1.10 > > > OAK-7312 validated the feasibility of a strategy where cleanup runs before > the compaction phase. Now that OAK-7377 and follow-up issues allow to define > the garbage collection process in a more modular way, it should be relatively > easy to introduce a new compaction strategy. > The new strategy shouldn't reduce the default compaction strategy. Instead, > the new strategy should be hidden behind a feature flag in oder to exposes it > to power-users for testing purposes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7445) Introduce a cleanup-first compaction strategy
[ https://issues.apache.org/jira/browse/OAK-7445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-7445: Description: OAK-7312 validated the feasibility of a strategy where cleanup runs before the compaction phase. Now that OAK-7377 and follow-up issues allow to define the garbage collection process in a more modular way, it should be relatively easy to introduce a new compaction strategy. The new strategy shouldn't reduce the default compaction strategy. Instead, the new strategy should be hidden behind a feature flag in oder to exposes it to power-users for testing purposes. was:OAK-7312 validated the feasibility of a strategy where cleanup runs before the compaction phase. Now that OAK-7377 and follow-up issues allow to define the garbage collection process in a more modular way, it should be relatively easy to introduce a new compaction strategy. > Introduce a cleanup-first compaction strategy > - > > Key: OAK-7445 > URL: https://issues.apache.org/jira/browse/OAK-7445 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Francesco Mari >Assignee: Francesco Mari >Priority: Major > Fix For: 1.10 > > > OAK-7312 validated the feasibility of a strategy where cleanup runs before > the compaction phase. Now that OAK-7377 and follow-up issues allow to define > the garbage collection process in a more modular way, it should be relatively > easy to introduce a new compaction strategy. > The new strategy shouldn't reduce the default compaction strategy. Instead, > the new strategy should be hidden behind a feature flag in oder to exposes it > to power-users for testing purposes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7445) Introduce a cleanup-first compaction strategy
Francesco Mari created OAK-7445: --- Summary: Introduce a cleanup-first compaction strategy Key: OAK-7445 URL: https://issues.apache.org/jira/browse/OAK-7445 Project: Jackrabbit Oak Issue Type: Improvement Components: segment-tar Reporter: Francesco Mari Assignee: Francesco Mari Fix For: 1.10 OAK-7312 validated the feasibility of a strategy where cleanup runs before the compaction phase. Now that OAK-7377 and follow-up issues allow to define the garbage collection process in a more modular way, it should be relatively easy to introduce a new compaction strategy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7435) Run travis build on MongoDB 3.6
[ https://issues.apache.org/jira/browse/OAK-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-7435. --- Resolution: Fixed Fix Version/s: 1.9.1 Done in trunk: http://svn.apache.org/r1829978 & http://svn.apache.org/r1829985 > Run travis build on MongoDB 3.6 > --- > > Key: OAK-7435 > URL: https://issues.apache.org/jira/browse/OAK-7435 > Project: Jackrabbit Oak > Issue Type: Task > Components: documentmk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 1.10, 1.9.1 > > > Trunk builds on travis-ci currently use MongoDB 3.4. They should instead use > the most recent stable release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7438) Expose mongo.url as build property
[ https://issues.apache.org/jira/browse/OAK-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-7438. --- Resolution: Fixed Fix Version/s: 1.9.1 Done in trunk: http://svn.apache.org/r182 > Expose mongo.url as build property > -- > > Key: OAK-7438 > URL: https://issues.apache.org/jira/browse/OAK-7438 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: parent >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 1.10, 1.9.1 > > > The oak-parent/pom.xml already contains some build properties to tweak the > connection to a MongoDB (host, port, db), but the entire url cannot be > overridden. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7443) remove jdk 1.6 specific findbugs profile from pom
[ https://issues.apache.org/jira/browse/OAK-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16449875#comment-16449875 ] Julian Reschke commented on OAK-7443: - trunk: [r1829998|http://svn.apache.org/r1829998] > remove jdk 1.6 specific findbugs profile from pom > - > > Key: OAK-7443 > URL: https://issues.apache.org/jira/browse/OAK-7443 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_8 > Fix For: 1.10, 1.9.1 > > > See OAK-2612. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7443) remove jdk 1.6 specific findbugs profile from pom
[ https://issues.apache.org/jira/browse/OAK-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-7443. - Resolution: Fixed Fix Version/s: 1.9.1 > remove jdk 1.6 specific findbugs profile from pom > - > > Key: OAK-7443 > URL: https://issues.apache.org/jira/browse/OAK-7443 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_8 > Fix For: 1.10, 1.9.1 > > > See OAK-2612. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7443) remove jdk 1.6 specific findbugs profile from pom
[ https://issues.apache.org/jira/browse/OAK-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7443: Labels: candidate_oak_1_8 (was: ) > remove jdk 1.6 specific findbugs profile from pom > - > > Key: OAK-7443 > URL: https://issues.apache.org/jira/browse/OAK-7443 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_8 > Fix For: 1.10, 1.9.1 > > > See OAK-2612. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7444) Allow collection of IOTraces during normal operation
Michael Dürig created OAK-7444:
--
Summary: Allow collection of IOTraces during normal operation
Key: OAK-7444
URL: https://issues.apache.org/jira/browse/OAK-7444
Project: Jackrabbit Oak
Issue Type: New Feature
Components: segment-tar
Reporter: Michael Dürig
Assignee: Michael Dürig
Fix For: 1.10
The IO tracing facility introduced with OAK-5655 should also be available
during normal operation. The idea is to log IO reads intercepted via an
{{IOMonitor}} instance to a logger. If {{DEBUG}} logging is not enabled for
that logger at the time when the {{FileStore}} is instantiated, then no tracing
would take place.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OAK-7440) Refactor the estimation code to its own components
[
https://issues.apache.org/jira/browse/OAK-7440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari resolved OAK-7440.
-
Resolution: Fixed
Fix Version/s: 1.9.1
Fixed at r1829996.
> Refactor the estimation code to its own components
> --
>
> Key: OAK-7440
> URL: https://issues.apache.org/jira/browse/OAK-7440
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
> Fix For: 1.10, 1.9.1
>
>
> The code performing cleanup, currently part of {{SizeDeltaGcEstimation}},
> could be split in two independent implementations. That piece of code
> currently implements two slightly different estimation strategies, for full
> and tail compaction respectively. It will be beneficial for
> {{DefaultGarbageCollectionStrategy}} to split {{SizeDeltaGcEstimation}} in
> two different implementations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OAK-7431) Build Jackrabbit Oak #1391 failed
[ https://issues.apache.org/jira/browse/OAK-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-7431. --- Resolution: Duplicate > Build Jackrabbit Oak #1391 failed > - > > Key: OAK-7431 > URL: https://issues.apache.org/jira/browse/OAK-7431 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1391 has failed. > First failed run: [Jackrabbit Oak > #1391|https://builds.apache.org/job/Jackrabbit%20Oak/1391/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1391/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OAK-7431) Build Jackrabbit Oak #1391 failed
[ https://issues.apache.org/jira/browse/OAK-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-7431. - > Build Jackrabbit Oak #1391 failed > - > > Key: OAK-7431 > URL: https://issues.apache.org/jira/browse/OAK-7431 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1391 has failed. > First failed run: [Jackrabbit Oak > #1391|https://builds.apache.org/job/Jackrabbit%20Oak/1391/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1391/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7429) Build Jackrabbit Oak #1388 failed
[ https://issues.apache.org/jira/browse/OAK-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-7429. --- Resolution: Duplicate > Build Jackrabbit Oak #1388 failed > - > > Key: OAK-7429 > URL: https://issues.apache.org/jira/browse/OAK-7429 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1388 has failed. > First failed run: [Jackrabbit Oak > #1388|https://builds.apache.org/job/Jackrabbit%20Oak/1388/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1388/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OAK-7429) Build Jackrabbit Oak #1388 failed
[ https://issues.apache.org/jira/browse/OAK-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-7429. - > Build Jackrabbit Oak #1388 failed > - > > Key: OAK-7429 > URL: https://issues.apache.org/jira/browse/OAK-7429 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1388 has failed. > First failed run: [Jackrabbit Oak > #1388|https://builds.apache.org/job/Jackrabbit%20Oak/1388/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1388/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OAK-7417) Build failure: Unable to start docker container
[
https://issues.apache.org/jira/browse/OAK-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger closed OAK-7417.
-
> Build failure: Unable to start docker container
> ---
>
> Key: OAK-7417
> URL: https://issues.apache.org/jira/browse/OAK-7417
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1379 has failed.
> First failed run: [Jackrabbit Oak
> #1379|https://builds.apache.org/job/Jackrabbit%20Oak/1379/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1379/console]
> {noformat}
> Error Message:
> Unable to start docker container: DockerConfig{name=oak-test-azurite}
> Stack Trace:
> java.lang.RuntimeException: Unable to start docker container:
> DockerConfig{name=oak-test-azurite}
> Caused by: com.spotify.docker.client.exceptions.DockerException: Unable to
> start container trekawek/azurite with id
> 143da1adbe30b57af680dc81e968ff1187130131053b8b7b0b4161e477a06b49
> Caused by: com.spotify.docker.client.exceptions.DockerRequestException:
> Request error: POST
> unix://localhost:80/containers/143da1adbe30b57af680dc81e968ff1187130131053b8b7b0b4161e477a06b49/start:
> 500, body: {"message":"endpoint with name oak-test-azurite already exists in
> network bridge"}
> Caused by:
> com.spotify.docker.client.shaded.javax.ws.rs.InternalServerErrorException:
> HTTP 500 Internal Server Error
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7417) Build failure: Unable to start docker container
[
https://issues.apache.org/jira/browse/OAK-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-7417:
--
Description:
No description is provided
The build Jackrabbit Oak #1379 has failed.
First failed run: [Jackrabbit Oak
#1379|https://builds.apache.org/job/Jackrabbit%20Oak/1379/] [console
log|https://builds.apache.org/job/Jackrabbit%20Oak/1379/console]
{noformat}
Error Message:
Unable to start docker container: DockerConfig{name=oak-test-azurite}
Stack Trace:
java.lang.RuntimeException: Unable to start docker container:
DockerConfig{name=oak-test-azurite}
Caused by: com.spotify.docker.client.exceptions.DockerException: Unable to
start container trekawek/azurite with id
143da1adbe30b57af680dc81e968ff1187130131053b8b7b0b4161e477a06b49
Caused by: com.spotify.docker.client.exceptions.DockerRequestException:
Request error: POST
unix://localhost:80/containers/143da1adbe30b57af680dc81e968ff1187130131053b8b7b0b4161e477a06b49/start:
500, body: {"message":"endpoint with name oak-test-azurite already exists in
network bridge"}
Caused by:
com.spotify.docker.client.shaded.javax.ws.rs.InternalServerErrorException: HTTP
500 Internal Server Error
{noformat}
was:
No description is provided
The build Jackrabbit Oak #1379 has failed.
First failed run: [Jackrabbit Oak
#1379|https://builds.apache.org/job/Jackrabbit%20Oak/1379/] [console
log|https://builds.apache.org/job/Jackrabbit%20Oak/1379/console]
> Build failure: Unable to start docker container
> ---
>
> Key: OAK-7417
> URL: https://issues.apache.org/jira/browse/OAK-7417
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1379 has failed.
> First failed run: [Jackrabbit Oak
> #1379|https://builds.apache.org/job/Jackrabbit%20Oak/1379/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1379/console]
> {noformat}
> Error Message:
> Unable to start docker container: DockerConfig{name=oak-test-azurite}
> Stack Trace:
> java.lang.RuntimeException: Unable to start docker container:
> DockerConfig{name=oak-test-azurite}
> Caused by: com.spotify.docker.client.exceptions.DockerException: Unable to
> start container trekawek/azurite with id
> 143da1adbe30b57af680dc81e968ff1187130131053b8b7b0b4161e477a06b49
> Caused by: com.spotify.docker.client.exceptions.DockerRequestException:
> Request error: POST
> unix://localhost:80/containers/143da1adbe30b57af680dc81e968ff1187130131053b8b7b0b4161e477a06b49/start:
> 500, body: {"message":"endpoint with name oak-test-azurite already exists in
> network bridge"}
> Caused by:
> com.spotify.docker.client.shaded.javax.ws.rs.InternalServerErrorException:
> HTTP 500 Internal Server Error
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OAK-7417) Build failure: Unable to start docker container
[
https://issues.apache.org/jira/browse/OAK-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved OAK-7417.
---
Resolution: Fixed
> Build failure: Unable to start docker container
> ---
>
> Key: OAK-7417
> URL: https://issues.apache.org/jira/browse/OAK-7417
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1379 has failed.
> First failed run: [Jackrabbit Oak
> #1379|https://builds.apache.org/job/Jackrabbit%20Oak/1379/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1379/console]
> {noformat}
> Error Message:
> Unable to start docker container: DockerConfig{name=oak-test-azurite}
> Stack Trace:
> java.lang.RuntimeException: Unable to start docker container:
> DockerConfig{name=oak-test-azurite}
> Caused by: com.spotify.docker.client.exceptions.DockerException: Unable to
> start container trekawek/azurite with id
> 143da1adbe30b57af680dc81e968ff1187130131053b8b7b0b4161e477a06b49
> Caused by: com.spotify.docker.client.exceptions.DockerRequestException:
> Request error: POST
> unix://localhost:80/containers/143da1adbe30b57af680dc81e968ff1187130131053b8b7b0b4161e477a06b49/start:
> 500, body: {"message":"endpoint with name oak-test-azurite already exists in
> network bridge"}
> Caused by:
> com.spotify.docker.client.shaded.javax.ws.rs.InternalServerErrorException:
> HTTP 500 Internal Server Error
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7417) Build failure: Unable to start docker container
[ https://issues.apache.org/jira/browse/OAK-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-7417: -- Summary: Build failure: Unable to start docker container (was: Build Jackrabbit Oak #1379 failed) > Build failure: Unable to start docker container > --- > > Key: OAK-7417 > URL: https://issues.apache.org/jira/browse/OAK-7417 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1379 has failed. > First failed run: [Jackrabbit Oak > #1379|https://builds.apache.org/job/Jackrabbit%20Oak/1379/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1379/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OAK-7413) Build Jackrabbit Oak #1376 failed
[ https://issues.apache.org/jira/browse/OAK-7413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-7413. - > Build Jackrabbit Oak #1376 failed > - > > Key: OAK-7413 > URL: https://issues.apache.org/jira/browse/OAK-7413 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1376 has failed. > First failed run: [Jackrabbit Oak > #1376|https://builds.apache.org/job/Jackrabbit%20Oak/1376/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1376/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7413) Build Jackrabbit Oak #1376 failed
[ https://issues.apache.org/jira/browse/OAK-7413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-7413. --- Resolution: Duplicate > Build Jackrabbit Oak #1376 failed > - > > Key: OAK-7413 > URL: https://issues.apache.org/jira/browse/OAK-7413 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1376 has failed. > First failed run: [Jackrabbit Oak > #1376|https://builds.apache.org/job/Jackrabbit%20Oak/1376/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1376/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7405) Build Jackrabbit Oak #1372 failed
[ https://issues.apache.org/jira/browse/OAK-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-7405. --- Resolution: Incomplete Log files not available anymore. > Build Jackrabbit Oak #1372 failed > - > > Key: OAK-7405 > URL: https://issues.apache.org/jira/browse/OAK-7405 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1372 has failed. > First failed run: [Jackrabbit Oak > #1372|https://builds.apache.org/job/Jackrabbit%20Oak/1372/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1372/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OAK-7405) Build Jackrabbit Oak #1372 failed
[ https://issues.apache.org/jira/browse/OAK-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-7405. - > Build Jackrabbit Oak #1372 failed > - > > Key: OAK-7405 > URL: https://issues.apache.org/jira/browse/OAK-7405 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1372 has failed. > First failed run: [Jackrabbit Oak > #1372|https://builds.apache.org/job/Jackrabbit%20Oak/1372/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1372/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7400) Build Jackrabbit Oak #1369 failed
[ https://issues.apache.org/jira/browse/OAK-7400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-7400. --- Resolution: Duplicate > Build Jackrabbit Oak #1369 failed > - > > Key: OAK-7400 > URL: https://issues.apache.org/jira/browse/OAK-7400 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1369 has failed. > First failed run: [Jackrabbit Oak > #1369|https://builds.apache.org/job/Jackrabbit%20Oak/1369/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1369/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OAK-7439) Build Jackrabbit Oak #1397 failed
[ https://issues.apache.org/jira/browse/OAK-7439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-7439. - > Build Jackrabbit Oak #1397 failed > - > > Key: OAK-7439 > URL: https://issues.apache.org/jira/browse/OAK-7439 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1397 has failed. > First failed run: [Jackrabbit Oak > #1397|https://builds.apache.org/job/Jackrabbit%20Oak/1397/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1397/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7439) Build Jackrabbit Oak #1397 failed
[ https://issues.apache.org/jira/browse/OAK-7439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-7439. --- Resolution: Duplicate > Build Jackrabbit Oak #1397 failed > - > > Key: OAK-7439 > URL: https://issues.apache.org/jira/browse/OAK-7439 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1397 has failed. > First failed run: [Jackrabbit Oak > #1397|https://builds.apache.org/job/Jackrabbit%20Oak/1397/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1397/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7443) remove jdk 1.6 specific findbugs profile from pom
[ https://issues.apache.org/jira/browse/OAK-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7443: Summary: remove jdk 1.6 specific findbugs profile from pom (was: remove jdk 1.6 specific profiles from pom) > remove jdk 1.6 specific findbugs profile from pom > - > > Key: OAK-7443 > URL: https://issues.apache.org/jira/browse/OAK-7443 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.10 > > > See OAK-2612. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7368) update to findbugs version compatible with jdk 10
[
https://issues.apache.org/jira/browse/OAK-7368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16449776#comment-16449776
]
Julian Reschke commented on OAK-7368:
-
FWIW, see OAK-2612 for an example making the findbugs version depend on the JDK.
> update to findbugs version compatible with jdk 10
> --
>
> Key: OAK-7368
> URL: https://issues.apache.org/jira/browse/OAK-7368
> Project: Jackrabbit Oak
> Issue Type: Task
>Reporter: Alex Deparvu
>Priority: Minor
>
> Warnings running findbugs
> {noformat}
> [INFO] --- findbugs-maven-plugin:3.0.4:findbugs (findbugs) @ oak-commons ---
> [INFO] Fork Value is true
> [java] Warning: Unknown version of Java
> [java] edu.umd.cs.findbugs.JavaVersionException: Could not parse Java
> version string: 10
> [java] at edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:68)
> [java] at
> edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:44)
> [java] at
> edu.umd.cs.findbugs.DetectorFactory.isEnabledForCurrentJRE(DetectorFactory.java:248)
> [java] at
> edu.umd.cs.findbugs.FindBugs.isDetectorEnabled(FindBugs.java:256)
> [java] at edu.umd.cs.findbugs.FindBugs2$3.choose(FindBugs2.java:906)
> [java] at
> edu.umd.cs.findbugs.plan.ExecutionPlan.build(ExecutionPlan.java:179)
> [java] at
> edu.umd.cs.findbugs.FindBugs2.createExecutionPlan(FindBugs2.java:935)
> [java] at edu.umd.cs.findbugs.FindBugs2.execute(FindBugs2.java:241)
> [java] at edu.umd.cs.findbugs.FindBugs.runMain(FindBugs.java:402)
> [java] at edu.umd.cs.findbugs.FindBugs2.main(FindBugs2.java:1200)
> {noformat}
> it seems findbugs-maven-plugin 3.0.5 (latest release) does not fix this and I
> couldn't find an open issue related to java 10.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OAK-7443) remove jdk 1.6 specific features from pom
Julian Reschke created OAK-7443: --- Summary: remove jdk 1.6 specific features from pom Key: OAK-7443 URL: https://issues.apache.org/jira/browse/OAK-7443 Project: Jackrabbit Oak Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 1.10 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7443) remove jdk 1.6 specific profiles from pom
[ https://issues.apache.org/jira/browse/OAK-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7443: Summary: remove jdk 1.6 specific profiles from pom (was: remove jdk 1.6 specific features from pom) > remove jdk 1.6 specific profiles from pom > - > > Key: OAK-7443 > URL: https://issues.apache.org/jira/browse/OAK-7443 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.10 > > > See OAK-2612. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7443) remove jdk 1.6 specific features from pom
[ https://issues.apache.org/jira/browse/OAK-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7443: Description: See OAK-2612. > remove jdk 1.6 specific features from pom > - > > Key: OAK-7443 > URL: https://issues.apache.org/jira/browse/OAK-7443 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.10 > > > See OAK-2612. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7441) RDB*Store: update DB2 JDBC dependency to 4.19.72
[ https://issues.apache.org/jira/browse/OAK-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16449757#comment-16449757 ] Julian Reschke commented on OAK-7441: - trunk: [r1829987|http://svn.apache.org/r1829987] > RDB*Store: update DB2 JDBC dependency to 4.19.72 > > > Key: OAK-7441 > URL: https://issues.apache.org/jira/browse/OAK-7441 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_8 > Fix For: 1.10, 1.9.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7441) RDB*Store: update DB2 JDBC dependency to 4.19.72
[ https://issues.apache.org/jira/browse/OAK-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7441: Labels: candidate_oak_1_8 (was: ) > RDB*Store: update DB2 JDBC dependency to 4.19.72 > > > Key: OAK-7441 > URL: https://issues.apache.org/jira/browse/OAK-7441 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_8 > Fix For: 1.10, 1.9.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7441) RDB*Store: update DB2 JDBC dependency to 4.19.72
[ https://issues.apache.org/jira/browse/OAK-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7441: Fix Version/s: 1.9.1 > RDB*Store: update DB2 JDBC dependency to 4.19.72 > > > Key: OAK-7441 > URL: https://issues.apache.org/jira/browse/OAK-7441 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_8 > Fix For: 1.10, 1.9.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7428) LdapIdentityProvider doesn't support creating external ids from custom attributes
[ https://issues.apache.org/jira/browse/OAK-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16449743#comment-16449743 ] angela commented on OAK-7428: - [~baedke], wouldn't it make sense to have the new configuration options you added in the documentation separated for users and groups? Looking that list of options it strikes me that most are separated by user and group configuration but not the 2 options you added. And btw: why two new configuration parameters?... reading the description I feel that the 'custom attributes' don't belong to this issue... cc: [~stillalex] > LdapIdentityProvider doesn't support creating external ids from custom > attributes > - > > Key: OAK-7428 > URL: https://issues.apache.org/jira/browse/OAK-7428 > Project: Jackrabbit Oak > Issue Type: Bug > Components: auth-ldap >Reporter: Manfred Baedke >Assignee: Manfred Baedke >Priority: Major > > The LdapIdentityProvider always uses the value of an authorizables DN to > create external ids. But DNs may change over time, while the external id of > an authorizable have to be stable because the property rep:externalID is > protected. > Therefore we need to add the option to use the value of a configurable LDAP > attribute to create external ids from it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7442) Remove dependency to commons-codec
Marcel Reutegger created OAK-7442: - Summary: Remove dependency to commons-codec Key: OAK-7442 URL: https://issues.apache.org/jira/browse/OAK-7442 Project: Jackrabbit Oak Issue Type: Improvement Components: documentmk Reporter: Marcel Reutegger Assignee: Marcel Reutegger Fix For: 1.10 The module oak-store-document currently only uses a single utility method from commons-codec. It shouldn't be too difficult to remove this dependency. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7441) RDB*Store: update DB2 JDBC dependency to 4.19.72
Julian Reschke created OAK-7441: --- Summary: RDB*Store: update DB2 JDBC dependency to 4.19.72 Key: OAK-7441 URL: https://issues.apache.org/jira/browse/OAK-7441 Project: Jackrabbit Oak Issue Type: Technical task Components: rdbmk Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 1.10 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7440) Refactor the estimation code to its own components
Francesco Mari created OAK-7440:
---
Summary: Refactor the estimation code to its own components
Key: OAK-7440
URL: https://issues.apache.org/jira/browse/OAK-7440
Project: Jackrabbit Oak
Issue Type: Improvement
Components: segment-tar
Reporter: Francesco Mari
Assignee: Francesco Mari
Fix For: 1.10
The code performing cleanup, currently part of {{SizeDeltaGcEstimation}}, could
be split in two independent implementations. That piece of code currently
implements two slightly different estimation strategies, for full and tail
compaction respectively. It will be beneficial for
{{DefaultGarbageCollectionStrategy}} to split {{SizeDeltaGcEstimation}} in two
different implementations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OAK-7439) Build Jackrabbit Oak #1397 failed
Hudson created OAK-7439: --- Summary: Build Jackrabbit Oak #1397 failed Key: OAK-7439 URL: https://issues.apache.org/jira/browse/OAK-7439 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit Oak #1397 has failed. First failed run: [Jackrabbit Oak #1397|https://builds.apache.org/job/Jackrabbit%20Oak/1397/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1397/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7438) Expose mongo.url as build property
Marcel Reutegger created OAK-7438: - Summary: Expose mongo.url as build property Key: OAK-7438 URL: https://issues.apache.org/jira/browse/OAK-7438 Project: Jackrabbit Oak Issue Type: Sub-task Components: parent Reporter: Marcel Reutegger Assignee: Marcel Reutegger Fix For: 1.10 The oak-parent/pom.xml already contains some build properties to tweak the connection to a MongoDB (host, port, db), but the entire url cannot be overridden. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7435) Run travis build on MongoDB 3.6
[ https://issues.apache.org/jira/browse/OAK-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16449606#comment-16449606 ] Marcel Reutegger commented on OAK-7435: --- Travis CI currently only has MongoDB up to 3.4 whitelisted on its [apt source|https://github.com/travis-ci/apt-source-whitelist/blob/master/ubuntu.json]. I'll change the MongoDB setup on travis-ci to commands executed during the install phase using mlaunch (part of [mtools|https://github.com/rueckstiess/mtools]). This also allows us to easily start a replica set if necessary. > Run travis build on MongoDB 3.6 > --- > > Key: OAK-7435 > URL: https://issues.apache.org/jira/browse/OAK-7435 > Project: Jackrabbit Oak > Issue Type: Task > Components: documentmk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 1.10 > > > Trunk builds on travis-ci currently use MongoDB 3.4. They should instead use > the most recent stable release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7431) Build Jackrabbit Oak #1391 failed
[ https://issues.apache.org/jira/browse/OAK-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16449601#comment-16449601 ] Hudson commented on OAK-7431: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #1396|https://builds.apache.org/job/Jackrabbit%20Oak/1396/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1396/console] > Build Jackrabbit Oak #1391 failed > - > > Key: OAK-7431 > URL: https://issues.apache.org/jira/browse/OAK-7431 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1391 has failed. > First failed run: [Jackrabbit Oak > #1391|https://builds.apache.org/job/Jackrabbit%20Oak/1391/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1391/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (OAK-6405) Cleanup the o.a.j.o.segment.file.tar package
[
https://issues.apache.org/jira/browse/OAK-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig reopened OAK-6405:
Assignee: (was: Francesco Mari)
Reopening for ease of tracking technical debt.
> Cleanup the o.a.j.o.segment.file.tar package
>
>
> Key: OAK-6405
> URL: https://issues.apache.org/jira/browse/OAK-6405
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Reporter: Francesco Mari
>Priority: Major
> Labels: technical_debt
>
> This issue tracks the cleanup and rearrangement of the internals of the
> {{o.a.j.o.segment.file.tar}} package.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (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 reopened OAK-4649: Assignee: (was: Francesco Mari) Reopening for ease of tracking technical debt. > 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 >Priority: Major > 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 (v7.6.3#76005)
[jira] [Reopened] (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 reopened OAK-4994: Reopening for ease of tracking technical debt. > 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 >Priority: Minor > Labels: technical_debt, 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 (v7.6.3#76005)
[jira] [Reopened] (OAK-2606) Remove code duplicated from commons-io
[
https://issues.apache.org/jira/browse/OAK-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig reopened OAK-2606:
Assignee: (was: Michael Dürig)
Reopening for ease of tracking technical debt.
> Remove code duplicated from commons-io
> --
>
> Key: OAK-2606
> URL: https://issues.apache.org/jira/browse/OAK-2606
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segmentmk
>Reporter: Michael Dürig
>Priority: Minor
> Labels: technical_debt
>
> OAK-2605 implements a workaround to IO-471 by duplicating the respective
> classes from commons-io with the IO-471 fix applied. We should revert back to
> using the classes from commons-io directly once there is a new release.
> See {{FIXME}} tags in http://svn.apache.org/r1665833 for where this applies.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (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 reopened OAK-6397:
Assignee: (was: Francesco Mari)
Reopening for ease of tracking technical debt.
> 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
>Priority: Major
> Labels: technical_debt
>
> 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
(v7.6.3#76005)
[jira] [Reopened] (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 reopened OAK-4582:
Assignee: (was: Francesco Mari)
Reopening for ease of tracking technical debt.
> 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: Task
> Components: segment-tar
>Reporter: Francesco Mari
>Priority: Major
> 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
(v7.6.3#76005)
[jira] [Created] (OAK-7437) SimpleExcerptProvider highlighting should be case insensitive
Thomas Mueller created OAK-7437: --- Summary: SimpleExcerptProvider highlighting should be case insensitive Key: OAK-7437 URL: https://issues.apache.org/jira/browse/OAK-7437 Project: Jackrabbit Oak Issue Type: Improvement Components: query Reporter: Thomas Mueller Assignee: Thomas Mueller Fix For: 1.10 The SimpleExcerptProvider is used if the index doesn't provide the excerpt. Highlighting should be case-insensitive. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7436) Refactor cleanup implementation in its own component
[ https://issues.apache.org/jira/browse/OAK-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-7436. - Resolution: Fixed Fix Version/s: 1.9.1 Fixed at r1829974. > Refactor cleanup implementation in its own component > > > Key: OAK-7436 > URL: https://issues.apache.org/jira/browse/OAK-7436 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Francesco Mari >Assignee: Francesco Mari >Priority: Major > Fix For: 1.10, 1.9.1 > > > The code performing cleanup (now part of DefaultGarbageCollectionStrategy per > OAK-7377) should be extracted as an independent building block. This level of > encapsulation enables the composition of the compaction and the cleanup > phases in different combinations, which is a prerequisite to experiment with > new garbage collection strategies with minimal code duplication. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7436) Refactor cleanup implementation in its own component
Francesco Mari created OAK-7436: --- Summary: Refactor cleanup implementation in its own component Key: OAK-7436 URL: https://issues.apache.org/jira/browse/OAK-7436 Project: Jackrabbit Oak Issue Type: Improvement Components: segment-tar Reporter: Francesco Mari Assignee: Francesco Mari Fix For: 1.10 The code performing cleanup (now part of DefaultGarbageCollectionStrategy per OAK-7377) should be extracted as an independent building block. This level of encapsulation enables the composition of the compaction and the cleanup phases in different combinations, which is a prerequisite to experiment with new garbage collection strategies with minimal code duplication. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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: --- Labels: concurrency resilience scalability technical_debt (was: concurrency resilience scalability) > 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 >Priority: Major > Labels: concurrency, resilience, scalability, technical_debt > > Implement refined conflict resolution for addExistingNode conflicts as > defined in the parent issue for the SegementMK. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7435) Run travis build on MongoDB 3.6
Marcel Reutegger created OAK-7435: - Summary: Run travis build on MongoDB 3.6 Key: OAK-7435 URL: https://issues.apache.org/jira/browse/OAK-7435 Project: Jackrabbit Oak Issue Type: Task Components: documentmk Reporter: Marcel Reutegger Assignee: Marcel Reutegger Fix For: 1.10 Trunk builds on travis-ci currently use MongoDB 3.4. They should instead use the most recent stable release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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:
---
Labels: operations production technical_debt (was: operations production)
> 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, technical_debt
>
> 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
(v7.6.3#76005)
[jira] [Resolved] (OAK-4914) Interrupt online revision cleanup on segmentmk
[
https://issues.apache.org/jira/browse/OAK-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig resolved OAK-4914.
Resolution: Won't Fix
> Interrupt online revision cleanup on segmentmk
> --
>
> Key: OAK-4914
> URL: https://issues.apache.org/jira/browse/OAK-4914
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: segmentmk
>Reporter: Alex Deparvu
>Priority: Major
> Labels: management
>
> Sub task of OAK-4835 for the {{segmentmk}} specific changes
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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: --- Labels: configuration production technical_debt (was: configuration production) > 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 >Priority: Major > Labels: configuration, production, technical_debt > > 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 (v7.6.3#76005)
[jira] [Updated] (OAK-6770) Convert oak-segment-tar to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-6770: --- Labels: osgi technical_debt (was: osgi) > Convert oak-segment-tar to OSGi R6 annotations > -- > > Key: OAK-6770 > URL: https://issues.apache.org/jira/browse/OAK-6770 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: segment-tar >Reporter: Robert Munteanu >Assignee: Francesco Mari >Priority: Minor > Labels: osgi, technical_debt > Fix For: 1.10 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-6674) Create a more complex IT for cold standby
[
https://issues.apache.org/jira/browse/OAK-6674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6674:
---
Labels: cold-standby technical_debt test (was: cold-standby test)
> Create a more complex IT for cold standby
> -
>
> Key: OAK-6674
> URL: https://issues.apache.org/jira/browse/OAK-6674
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: segment-tar, tarmk-standby
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Major
> Labels: cold-standby, technical_debt, test
>
> At the moment all integration tests for cold standby are using the same
> scenario in their tests: some content is created on the server (including
> binaries), a standby sync cycle is started and then the content is checked on
> the client. The only twist here is using/not using a data store for storing
> binaries.
> Although good, this model could be extended to cover many more cases. For
> example, {{StandbyDiff}} covers the following 6 cases node/property
> added/changed/deleted. From these, with the scenario described, the removal
> part is never tested (and the change part is covered in only one test).
> It would be nice to have an IT which would add content on the server, do a
> sync, remove some of the content, do a sync and then call OnRC. This way all
> cases will be covered, including if cleanup works as expected on the client.
> /cc [~frm]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-6941) Compatibility matrix for oak-run compact
[
https://issues.apache.org/jira/browse/OAK-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6941:
---
Labels: documentation technical_debt tooling (was: documentation tooling)
> Compatibility matrix for oak-run compact
>
>
> Key: OAK-6941
> URL: https://issues.apache.org/jira/browse/OAK-6941
> Project: Jackrabbit Oak
> Issue Type: Documentation
> Components: doc, run, segment-tar
>Reporter: Valentin Olteanu
>Priority: Major
> Labels: documentation, technical_debt, tooling
> Fix For: 1.10
>
>
> h4. Problem statement
> For compacting the segmentstore using {{oak-run}}, the safest option is to
> use the same version of {{oak-run}} as the Oak version used to generate the
> repository. Yet, sometimes, a newer {{oak-run}} version is recommended to
> benefit of bug fixes and improvements, but not every combination of source
> repo and oak-run is safe to use and the user needs a way to check the
> compatibility. Thus, the users need a tool that guides the decision of which
> version to use.
> h4. Requirements
> * Easy to decide what {{oak-run}} version should be used for a certain Oak
> version
> * Up to date with the latest releases
> * Machine readable for scripting
> * Include details on the benefits of using a certain version (release notes)
> * Blacklist of versions that should not be used (with alternatives)
> h4. Solution
> TBD
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7279) segment-tar update from java 7 to java 8 may break persisted names using invalid characters
[
https://issues.apache.org/jira/browse/OAK-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-7279:
---
Labels: tech-debt (was: )
> segment-tar update from java 7 to java 8 may break persisted names using
> invalid characters
> ---
>
> Key: OAK-7279
> URL: https://issues.apache.org/jira/browse/OAK-7279
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Priority: Minor
> Labels: tech-debt
>
> segment-tar relies on {{String.getBytes()}} when persisting strings such as
> item names.
> The problem is that the behavior for this has been changed in Java 8 with
> respect to invalid strings (here: null characters and unpaired surrogates).
> In Java 7, these would roundtrip, as Java was using the so-called "modified
> UTF-8" encoding (see
> https://docs.oracle.com/javase/6/docs/api/java/io/DataInput.html#modified-utf-8).
> This will produce byte sequence that are *not* valid UTF-8.
> Java 7 will read them back, but Java 8 will map the non-conforming byte
> sequences to the Unicode replacement character. Note that in particular,
> multiple child entries might get identical names as a consequence.
> I'm not sure about the severity of this, and whether something needs to be
> done about it. AFAIC, this is another good reason to reject invalid strings
> as early as possible in the stack.
> cc [~mduerig]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7425) Add discovery mechanism for tooling implementations
[
https://issues.apache.org/jira/browse/OAK-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-7425:
---
Labels: technical_debt (was: )
> Add discovery mechanism for tooling implementations
> ---
>
> Key: OAK-7425
> URL: https://issues.apache.org/jira/browse/OAK-7425
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Major
> Labels: technical_debt
> Fix For: 1.10
>
> Attachments: 001.patch
>
>
> This issue proposes an idea for discovering implementations of tooling for
> the Segment Store. Developing a tool for the Segment Store should include the
> following step.
> * The tool compiles against the {{NodeStore}} API and the API exposed through
> the oak-segment-tar-tool-api. In particular, the tool uses the
> {{ToolingSupportFactory}} and related interfaces to instantiate a NodeStore
> and, optionally, a {{NodeState}} for the proc tree.
> * The tool runs with an implementation-dependent uber-jar in the classpath.
> The uber-jar includes the {{ToolingSupportFactory}} API, its implementation,
> and every other class required for the implementation to work. No other JARs
> is required to use the {{ToolingSupportFactory}} API. The tool uses the
> Java's {{ServiceLoader}} to instantiate an implementation of
> {{ToolingSupportFactory}}. The uber-jar is the {{oak-segment-tar-tool}}
> module.
> The patch falls short of fully implementing the use case because
> {{oak-segment-tar-tool-api}} is not versioned independently from Oak. This
> can't happen at the moment because {{oak-store-spi}} and its dependencies are
> not independently versioned either. The workflow described above could still
> work, but only because the {{NodeStore}} and {{NodeState}} API are quite
> stable. A cleaner solution to dependency management is required in the long
> run.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7423) Document the proc tree
[ https://issues.apache.org/jira/browse/OAK-7423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-7423: --- Labels: technical_debt (was: ) > Document the proc tree > -- > > Key: OAK-7423 > URL: https://issues.apache.org/jira/browse/OAK-7423 > Project: Jackrabbit Oak > Issue Type: Documentation > Components: segment-tar >Reporter: Francesco Mari >Assignee: Francesco Mari >Priority: Major > Labels: technical_debt > Fix For: 1.10 > > > The proc tree, contributed in OAK-7416, lacks Javadoc and high-level > documentation. In particular, the exposed content structure should be > described in greater detail. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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: --- Labels: technical_debt tooling (was: 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 >Priority: Minor > Labels: technical_debt, 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 (v7.6.3#76005)
[jira] [Resolved] (OAK-7402) Expose UI for collecting IO traces
[
https://issues.apache.org/jira/browse/OAK-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig resolved OAK-7402.
Resolution: Fixed
Fix Version/s: 1.9.1
Fixed at http://svn.apache.org/viewvc?rev=1829969=rev
> Expose UI for collecting IO traces
> --
>
> Key: OAK-7402
> URL: https://issues.apache.org/jira/browse/OAK-7402
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: oak-run, segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
>Priority: Major
> Labels: tooling
> Fix For: 1.10, 1.9.1
>
>
> [http://svn.apache.org/viewvc?view=revision=1827841] introduced
> utility classes to collect IO traces. See e.g.
> https://issues.apache.org/jira/browse/OAK-5655?focusedCommentId=16415730=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16415730.
> Currently the only way to run such traces is via code or JUnit (see
> {{IOTracerRunner}}).
> Going forward we should wire this functionality to {{oak-run}} to make it
> more generally useful.
>
> [~frm], FYI.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
