[jira] [Assigned] (OAK-7025) Node isCheckedOut() when jcr:isCheckedOut = false throwing ContraintViolationException.

[Marcel Reutegger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcel Reutegger reassigned OAK-7025:
-

Assignee: Marcel Reutegger

> Node isCheckedOut() when jcr:isCheckedOut = false throwing 
> ContraintViolationException.
> ---
>
> Key: OAK-7025
> URL: https://issues.apache.org/jira/browse/OAK-7025
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core, jcr
>Affects Versions: 1.7.11
>Reporter: Jonathan Gurfinkel
>Assignee: Marcel Reutegger
>
> Working on versioning nodes.
> _line 1: VersionManager vm = session.getWorkspace().getVersionManager();  
>   
> line 2: Version firstVersion = vm.checkin(path);
> line 3: vm.checkout(path);
> line 4: System.out.println(componentNode.isCheckedOut());
> line 5: vm.checkin(path);
> line 6: 
> System.out.println(componentNode.getProperty("jcr:isCheckedOut").getString());
> line 7: System.out.println(componentNode.isCheckoutOut());_
> Line 4 prints "true" as expected.  Line 6 prints "false" as expected as 
> getting checkoutOut property via getProperty method, line 7 expect should 
> return "false" as per line 6 but throws constraint violation exception, as 
> per stack trace below.
> javax.jcr.nodetype.ConstraintViolationException: No matching node definition 
> found for testNode
>   at 
> org.apache.jackrabbit.oak.plugins.nodetype.EffectiveNodeTypeImpl.getNodeDefinition(EffectiveNodeTypeImpl.java:454)
>   at 
> org.apache.jackrabbit.oak.plugins.nodetype.ReadOnlyNodeTypeManager.getDefinition(ReadOnlyNodeTypeManager.java:396)
>   at 
> org.apache.jackrabbit.oak.jcr.version.VersionManagerImpl$3.perform(VersionManagerImpl.java:272)
>   at 
> org.apache.jackrabbit.oak.jcr.version.VersionManagerImpl$3.perform(VersionManagerImpl.java:254)
>   at 
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:208)
>   at 
> org.apache.jackrabbit.oak.jcr.version.VersionManagerImpl.isCheckedOut(VersionManagerImpl.java:254)
>   at 
> org.apache.jackrabbit.oak.jcr.session.NodeImpl.isCheckedOut(NodeImpl.java:1123)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OAK-7026) DataStoreCheckTes#testConsistencyVerbose* test failures

[Amit Jain (JIRA)]

Amit Jain created OAK-7026:
--

 Summary: DataStoreCheckTes#testConsistencyVerbose* test failures
 Key: OAK-7026
 URL: https://issues.apache.org/jira/browse/OAK-7026
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: run
Reporter: Amit Jain
Assignee: Amit Jain


Intermittently test failures (likely only on windows)

{noformat}
[INFO] Running org.apache.jackrabbit.oak.run.DataStoreCheckTest
[ERROR] Tests run: 12, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 2.02 s 
<<< FAILURE! - in org.apache.jackrabbit.oak.run.DataStoreCheckTest
[ERROR] 
testConsistencyVerbose(org.apache.jackrabbit.oak.run.DataStoreCheckTest)  Time 
elapsed: 0.26 s  <<< ERROR!
java.io.IOException: Unable to delete file: C:\tmp\ids5117643859629864856.tmp
at 
org.apache.jackrabbit.oak.run.DataStoreCheckTest.testAllParamsVerbose(DataStoreCheckTest.java:332)
at 
org.apache.jackrabbit.oak.run.DataStoreCheckTest.testConsistencyVerbose(DataStoreCheckTest.java:233)

[ERROR] 
testConsistencyVerboseWithDeleteTracker(org.apache.jackrabbit.oak.run.DataStoreCheckTest)
  Time elapsed: 0.172 s  <<< ERROR!
java.io.IOException: Unable to delete file: C:\tmp\ids7859857301677881810.tmp
at 
org.apache.jackrabbit.oak.run.DataStoreCheckTest.testAllParamsVerbose(DataStoreCheckTest.java:332)
at 
org.apache.jackrabbit.oak.run.DataStoreCheckTest.testConsistencyVerboseWithDeleteTracker(DataStoreCheckTest.java:297)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-7014) Test failure: EmbeddedSolrServerProviderTest.testEmbeddedSolrServerInitialization

[Marcel Reutegger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcel Reutegger updated OAK-7014:
--
Summary: Test failure: 
EmbeddedSolrServerProviderTest.testEmbeddedSolrServerInitialization  (was: 
Build Jackrabbit Oak #1027 failed)

> Test failure: 
> EmbeddedSolrServerProviderTest.testEmbeddedSolrServerInitialization
> -
>
> Key: OAK-7014
> URL: https://issues.apache.org/jira/browse/OAK-7014
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, solr
>Reporter: Hudson
>
> No description is provided
> The build Jackrabbit Oak #1027 has failed.
> First failed run: [Jackrabbit Oak 
> #1027|https://builds.apache.org/job/Jackrabbit%20Oak/1027/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1027/console]
> {noformat}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.571 
> s <<< FAILURE! - in 
> org.apache.jackrabbit.oak.plugins.index.solr.server.EmbeddedSolrServerProviderTest
> [ERROR] 
> testEmbeddedSolrServerInitialization(org.apache.jackrabbit.oak.plugins.index.solr.server.EmbeddedSolrServerProviderTest)
>   Time elapsed: 1.571 s  <<< ERROR!
> org.apache.solr.common.SolrException: SolrCore 'oak' is not available due to 
> init failure: Error loading class 'solr.JsonUpdateRequestHandler'
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (OAK-7014) Test failure: EmbeddedSolrServerProviderTest.testEmbeddedSolrServerInitialization

[Marcel Reutegger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcel Reutegger resolved OAK-7014.
---
Resolution: Fixed

> Test failure: 
> EmbeddedSolrServerProviderTest.testEmbeddedSolrServerInitialization
> -
>
> Key: OAK-7014
> URL: https://issues.apache.org/jira/browse/OAK-7014
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, solr
>Reporter: Hudson
>
> No description is provided
> The build Jackrabbit Oak #1027 has failed.
> First failed run: [Jackrabbit Oak 
> #1027|https://builds.apache.org/job/Jackrabbit%20Oak/1027/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1027/console]
> {noformat}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.571 
> s <<< FAILURE! - in 
> org.apache.jackrabbit.oak.plugins.index.solr.server.EmbeddedSolrServerProviderTest
> [ERROR] 
> testEmbeddedSolrServerInitialization(org.apache.jackrabbit.oak.plugins.index.solr.server.EmbeddedSolrServerProviderTest)
>   Time elapsed: 1.571 s  <<< ERROR!
> org.apache.solr.common.SolrException: SolrCore 'oak' is not available due to 
> init failure: Error loading class 'solr.JsonUpdateRequestHandler'
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (OAK-7014) Test failure: EmbeddedSolrServerProviderTest.testEmbeddedSolrServerInitialization

[Marcel Reutegger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcel Reutegger closed OAK-7014.
-

> Test failure: 
> EmbeddedSolrServerProviderTest.testEmbeddedSolrServerInitialization
> -
>
> Key: OAK-7014
> URL: https://issues.apache.org/jira/browse/OAK-7014
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, solr
>Reporter: Hudson
>
> No description is provided
> The build Jackrabbit Oak #1027 has failed.
> First failed run: [Jackrabbit Oak 
> #1027|https://builds.apache.org/job/Jackrabbit%20Oak/1027/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1027/console]
> {noformat}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.571 
> s <<< FAILURE! - in 
> org.apache.jackrabbit.oak.plugins.index.solr.server.EmbeddedSolrServerProviderTest
> [ERROR] 
> testEmbeddedSolrServerInitialization(org.apache.jackrabbit.oak.plugins.index.solr.server.EmbeddedSolrServerProviderTest)
>   Time elapsed: 1.571 s  <<< ERROR!
> org.apache.solr.common.SolrException: SolrCore 'oak' is not available due to 
> init failure: Error loading class 'solr.JsonUpdateRequestHandler'
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-7014) Build Jackrabbit Oak #1027 failed

[Marcel Reutegger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcel Reutegger updated OAK-7014:
--
Description: 
No description is provided

The build Jackrabbit Oak #1027 has failed.
First failed run: [Jackrabbit Oak 
#1027|https://builds.apache.org/job/Jackrabbit%20Oak/1027/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1027/console]

{noformat}
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.571 s 
<<< FAILURE! - in 
org.apache.jackrabbit.oak.plugins.index.solr.server.EmbeddedSolrServerProviderTest
[ERROR] 
testEmbeddedSolrServerInitialization(org.apache.jackrabbit.oak.plugins.index.solr.server.EmbeddedSolrServerProviderTest)
  Time elapsed: 1.571 s  <<< ERROR!
org.apache.solr.common.SolrException: SolrCore 'oak' is not available due to 
init failure: Error loading class 'solr.JsonUpdateRequestHandler'
{noformat}

  was:
No description is provided

The build Jackrabbit Oak #1027 has failed.
First failed run: [Jackrabbit Oak 
#1027|https://builds.apache.org/job/Jackrabbit%20Oak/1027/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1027/console]

Component/s: solr

Most likely caused by OAK-4318. The build went back to green once those changes 
were reverted.

> Build Jackrabbit Oak #1027 failed
> -
>
> Key: OAK-7014
> URL: https://issues.apache.org/jira/browse/OAK-7014
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, solr
>Reporter: Hudson
>
> No description is provided
> The build Jackrabbit Oak #1027 has failed.
> First failed run: [Jackrabbit Oak 
> #1027|https://builds.apache.org/job/Jackrabbit%20Oak/1027/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1027/console]
> {noformat}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.571 
> s <<< FAILURE! - in 
> org.apache.jackrabbit.oak.plugins.index.solr.server.EmbeddedSolrServerProviderTest
> [ERROR] 
> testEmbeddedSolrServerInitialization(org.apache.jackrabbit.oak.plugins.index.solr.server.EmbeddedSolrServerProviderTest)
>   Time elapsed: 1.571 s  <<< ERROR!
> org.apache.solr.common.SolrException: SolrCore 'oak' is not available due to 
> init failure: Error loading class 'solr.JsonUpdateRequestHandler'
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (OAK-6586) [oak-run] Add option to datastorecheck command to report misconfigured external binary references

[Julian Reschke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-6586:

Comment: was deleted

(was: trunk: [r1816810|http://svn.apache.org/r1816810] 
[r1816808|http://svn.apache.org/r1816808] 
[r1816800|http://svn.apache.org/r1816800]
)

> [oak-run] Add option to datastorecheck command to report misconfigured 
> external binary references
> -
>
> Key: OAK-6586
> URL: https://issues.apache.org/jira/browse/OAK-6586
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: run
>Reporter: Arek Kita
>Assignee: Amit Jain
> Fix For: 1.8, 1.7.12
>
>
> It would be good if we could create OOTB check in oak-run that could scan Oak 
> repositories looking for any binaries that might be missing mostly due to 2 
> reasons:
> * binaries that are not inlined _when_ BlobStore/DataStore is not defined 
> (the assumption is we have *+only+* inlined binaries and we would like to 
> verify such hypothesis, external reference exists but shouldn't and no DS is 
> known, i.e. a result of misconfiguration)
> * missing binaries in defined BlobStore/DataStore (external references exist 
> but no binary is present at DataStore)
> _This might also be also very helpful debugging repository in the future with 
> CompositeBlobStore layouts._
> I see that this is is often the case and it causes problems during migration 
> (upgrades, sidegrades) of stores. The knowledge which JCR paths are affected 
> would be a great help for Oak users.
> The following groovy script does this but I thought about something built-in.
> {code}
> // usage:
> // java -jar oak-run-1.4.6.jar console --fds-path 
> crx-quickstart/repository/datastore crx-quickstart/repository/segmentstore 
> ":load find-missing-blobs.groovy"
> import org.apache.jackrabbit.oak.api.PropertyState
> import org.apache.jackrabbit.oak.api.Type
> import org.apache.jackrabbit.oak.commons.PathUtils
> import org.apache.jackrabbit.oak.spi.state.ChildNodeEntry
> import org.apache.jackrabbit.oak.spi.state.NodeState
> org.slf4j.LoggerFactory.getLogger(ch.qos.logback.classic.Logger.ROOT_LOGGER_NAME).setLevel(ch.qos.logback.classic.Level.OFF)
> class MissingBlobFinder {
> static checkProperties(state, String path) {
> for (PropertyState p : state.properties) {
> try {
> if (p.type == Type.BINARY) {
> InputStream is = p.getValue(Type.BINARY).newStream
> is.read()
> is.close()
> } else if (p.type == Type.BINARIES && p.count() > 0) {
> InputStream is = 
> p.getValue(Type.BINARIES).iterator().next().newStream
> is.read()
> is.close()
> }
> } catch (Exception e) {
> System.out.println(PathUtils.concat(path, p.name))
> }
> }
> }
> static traverse(NodeState state, String path) {
> checkProperties(state, path)
> for (ChildNodeEntry c : state.childNodeEntries) {
> traverse(c.nodeState, PathUtils.concat(path, c.name))
> }
> }
> static runFixer(session) {
> System.out.println("---")
> System.out.println("List of missing blobs:")
> System.out.println()
> traverse(session.store.root, "/")
> System.out.println("---")
> null
> }
> }
> MissingBlobFinder.runFixer(session)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-6586) [oak-run] Add option to datastorecheck command to report misconfigured external binary references

[Julian Reschke (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278114#comment-16278114
 ] 

Julian Reschke commented on OAK-6586:
-

trunk: [r1816810|http://svn.apache.org/r1816810] 
[r1816808|http://svn.apache.org/r1816808] 
[r1816800|http://svn.apache.org/r1816800]


> [oak-run] Add option to datastorecheck command to report misconfigured 
> external binary references
> -
>
> Key: OAK-6586
> URL: https://issues.apache.org/jira/browse/OAK-6586
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: run
>Reporter: Arek Kita
>Assignee: Amit Jain
> Fix For: 1.8, 1.7.12
>
>
> It would be good if we could create OOTB check in oak-run that could scan Oak 
> repositories looking for any binaries that might be missing mostly due to 2 
> reasons:
> * binaries that are not inlined _when_ BlobStore/DataStore is not defined 
> (the assumption is we have *+only+* inlined binaries and we would like to 
> verify such hypothesis, external reference exists but shouldn't and no DS is 
> known, i.e. a result of misconfiguration)
> * missing binaries in defined BlobStore/DataStore (external references exist 
> but no binary is present at DataStore)
> _This might also be also very helpful debugging repository in the future with 
> CompositeBlobStore layouts._
> I see that this is is often the case and it causes problems during migration 
> (upgrades, sidegrades) of stores. The knowledge which JCR paths are affected 
> would be a great help for Oak users.
> The following groovy script does this but I thought about something built-in.
> {code}
> // usage:
> // java -jar oak-run-1.4.6.jar console --fds-path 
> crx-quickstart/repository/datastore crx-quickstart/repository/segmentstore 
> ":load find-missing-blobs.groovy"
> import org.apache.jackrabbit.oak.api.PropertyState
> import org.apache.jackrabbit.oak.api.Type
> import org.apache.jackrabbit.oak.commons.PathUtils
> import org.apache.jackrabbit.oak.spi.state.ChildNodeEntry
> import org.apache.jackrabbit.oak.spi.state.NodeState
> org.slf4j.LoggerFactory.getLogger(ch.qos.logback.classic.Logger.ROOT_LOGGER_NAME).setLevel(ch.qos.logback.classic.Level.OFF)
> class MissingBlobFinder {
> static checkProperties(state, String path) {
> for (PropertyState p : state.properties) {
> try {
> if (p.type == Type.BINARY) {
> InputStream is = p.getValue(Type.BINARY).newStream
> is.read()
> is.close()
> } else if (p.type == Type.BINARIES && p.count() > 0) {
> InputStream is = 
> p.getValue(Type.BINARIES).iterator().next().newStream
> is.read()
> is.close()
> }
> } catch (Exception e) {
> System.out.println(PathUtils.concat(path, p.name))
> }
> }
> }
> static traverse(NodeState state, String path) {
> checkProperties(state, path)
> for (ChildNodeEntry c : state.childNodeEntries) {
> traverse(c.nodeState, PathUtils.concat(path, c.name))
> }
> }
> static runFixer(session) {
> System.out.println("---")
> System.out.println("List of missing blobs:")
> System.out.println()
> traverse(session.store.root, "/")
> System.out.println("---")
> null
> }
> }
> MissingBlobFinder.runFixer(session)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-3426) MultiplexingDocumentStore implementation

[Chetan Mehrotra (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277982#comment-16277982
 ] 

Chetan Mehrotra commented on OAK-3426:
--

I think this feature would still be useful to provide a path based sharding 
support for Oak deployments on DocumentNodeStore. Something we can revisit for 
1.10 work

> MultiplexingDocumentStore implementation
> 
>
> Key: OAK-3426
> URL: https://issues.apache.org/jira/browse/OAK-3426
> Project: Jackrabbit Oak
>  Issue Type: Story
>  Components: core, mongomk, rdbmk
>Reporter: Robert Munteanu
>
> Create a MultiplexingDocumentStore implementation ( see OAK-3401 for details 
> ). Feature is developed for now at 
> https://github.com/rombert/jackrabbit-oak/tree/features/docstore-multiplex



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-7025) Node isCheckedOut() when jcr:isCheckedOut = false throwing ContraintViolationException.

[Jonathan Gurfinkel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Gurfinkel updated OAK-7025:

Affects Version/s: 1.7.11
  Component/s: jcr
   core

> Node isCheckedOut() when jcr:isCheckedOut = false throwing 
> ContraintViolationException.
> ---
>
> Key: OAK-7025
> URL: https://issues.apache.org/jira/browse/OAK-7025
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core, jcr
>Affects Versions: 1.7.11
>Reporter: Jonathan Gurfinkel
>
> Working on versioning nodes.
> _line 1: VersionManager vm = session.getWorkspace().getVersionManager();  
>   
> line 2: Version firstVersion = vm.checkin(path);
> line 3: vm.checkout(path);
> line 4: System.out.println(componentNode.isCheckedOut());
> line 5: vm.checkin(path);
> line 6: 
> System.out.println(componentNode.getProperty("jcr:isCheckedOut").getString());
> line 7: System.out.println(componentNode.isCheckoutOut());_
> Line 4 prints "true" as expected.  Line 6 prints "false" as expected as 
> getting checkoutOut property via getProperty method, line 7 expect should 
> return "false" as per line 6 but throws constraint violation exception, as 
> per stack trace below.
> javax.jcr.nodetype.ConstraintViolationException: No matching node definition 
> found for testNode
>   at 
> org.apache.jackrabbit.oak.plugins.nodetype.EffectiveNodeTypeImpl.getNodeDefinition(EffectiveNodeTypeImpl.java:454)
>   at 
> org.apache.jackrabbit.oak.plugins.nodetype.ReadOnlyNodeTypeManager.getDefinition(ReadOnlyNodeTypeManager.java:396)
>   at 
> org.apache.jackrabbit.oak.jcr.version.VersionManagerImpl$3.perform(VersionManagerImpl.java:272)
>   at 
> org.apache.jackrabbit.oak.jcr.version.VersionManagerImpl$3.perform(VersionManagerImpl.java:254)
>   at 
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:208)
>   at 
> org.apache.jackrabbit.oak.jcr.version.VersionManagerImpl.isCheckedOut(VersionManagerImpl.java:254)
>   at 
> org.apache.jackrabbit.oak.jcr.session.NodeImpl.isCheckedOut(NodeImpl.java:1123)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-7025) Node isCheckedOut() when jcr:isCheckedOut = false throwing ContraintViolationException.

[Jonathan Gurfinkel (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Gurfinkel updated OAK-7025:

Description: 
Working on versioning nodes.

_line 1: VersionManager vm = session.getWorkspace().getVersionManager();
line 2: Version firstVersion = vm.checkin(path);
line 3: vm.checkout(path);
line 4: System.out.println(componentNode.isCheckedOut());
line 5: vm.checkin(path);
line 6: 
System.out.println(componentNode.getProperty("jcr:isCheckedOut").getString());
line 7: System.out.println(componentNode.isCheckoutOut());_

Line 4 prints "true" as expected.  Line 6 prints "false" as expected as getting 
checkoutOut property via getProperty method, line 7 expect should return 
"false" as per line 6 but throws constraint violation exception, as per stack 
trace below.

javax.jcr.nodetype.ConstraintViolationException: No matching node definition 
found for testNode
at 
org.apache.jackrabbit.oak.plugins.nodetype.EffectiveNodeTypeImpl.getNodeDefinition(EffectiveNodeTypeImpl.java:454)
at 
org.apache.jackrabbit.oak.plugins.nodetype.ReadOnlyNodeTypeManager.getDefinition(ReadOnlyNodeTypeManager.java:396)
at 
org.apache.jackrabbit.oak.jcr.version.VersionManagerImpl$3.perform(VersionManagerImpl.java:272)
at 
org.apache.jackrabbit.oak.jcr.version.VersionManagerImpl$3.perform(VersionManagerImpl.java:254)
at 
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:208)
at 
org.apache.jackrabbit.oak.jcr.version.VersionManagerImpl.isCheckedOut(VersionManagerImpl.java:254)
at 
org.apache.jackrabbit.oak.jcr.session.NodeImpl.isCheckedOut(NodeImpl.java:1123)



> Node isCheckedOut() when jcr:isCheckedOut = false throwing 
> ContraintViolationException.
> ---
>
> Key: OAK-7025
> URL: https://issues.apache.org/jira/browse/OAK-7025
> Project: Jackrabbit Oak
>  Issue Type: Bug
>Reporter: Jonathan Gurfinkel
>
> Working on versioning nodes.
> _line 1: VersionManager vm = session.getWorkspace().getVersionManager();  
>   
> line 2: Version firstVersion = vm.checkin(path);
> line 3: vm.checkout(path);
> line 4: System.out.println(componentNode.isCheckedOut());
> line 5: vm.checkin(path);
> line 6: 
> System.out.println(componentNode.getProperty("jcr:isCheckedOut").getString());
> line 7: System.out.println(componentNode.isCheckoutOut());_
> Line 4 prints "true" as expected.  Line 6 prints "false" as expected as 
> getting checkoutOut property via getProperty method, line 7 expect should 
> return "false" as per line 6 but throws constraint violation exception, as 
> per stack trace below.
> javax.jcr.nodetype.ConstraintViolationException: No matching node definition 
> found for testNode
>   at 
> org.apache.jackrabbit.oak.plugins.nodetype.EffectiveNodeTypeImpl.getNodeDefinition(EffectiveNodeTypeImpl.java:454)
>   at 
> org.apache.jackrabbit.oak.plugins.nodetype.ReadOnlyNodeTypeManager.getDefinition(ReadOnlyNodeTypeManager.java:396)
>   at 
> org.apache.jackrabbit.oak.jcr.version.VersionManagerImpl$3.perform(VersionManagerImpl.java:272)
>   at 
> org.apache.jackrabbit.oak.jcr.version.VersionManagerImpl$3.perform(VersionManagerImpl.java:254)
>   at 
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:208)
>   at 
> org.apache.jackrabbit.oak.jcr.version.VersionManagerImpl.isCheckedOut(VersionManagerImpl.java:254)
>   at 
> org.apache.jackrabbit.oak.jcr.session.NodeImpl.isCheckedOut(NodeImpl.java:1123)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OAK-7025) Node isCheckedOut() when jcr:isCheckedOut = false throwing ContraintViolationException.

[Jonathan Gurfinkel (JIRA)]

Jonathan Gurfinkel created OAK-7025:
---

 Summary: Node isCheckedOut() when jcr:isCheckedOut = false 
throwing ContraintViolationException.
 Key: OAK-7025
 URL: https://issues.apache.org/jira/browse/OAK-7025
 Project: Jackrabbit Oak
  Issue Type: Bug
Reporter: Jonathan Gurfinkel






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Reopened] (OAK-3426) MultiplexingDocumentStore implementation

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu reopened OAK-3426:
--

> MultiplexingDocumentStore implementation
> 
>
> Key: OAK-3426
> URL: https://issues.apache.org/jira/browse/OAK-3426
> Project: Jackrabbit Oak
>  Issue Type: Story
>  Components: core, mongomk, rdbmk
>Reporter: Robert Munteanu
>
> Create a MultiplexingDocumentStore implementation ( see OAK-3401 for details 
> ). Feature is developed for now at 
> https://github.com/rombert/jackrabbit-oak/tree/features/docstore-multiplex



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (OAK-3426) MultiplexingDocumentStore implementation

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved OAK-3426.
--
Resolution: Won't Fix

> MultiplexingDocumentStore implementation
> 
>
> Key: OAK-3426
> URL: https://issues.apache.org/jira/browse/OAK-3426
> Project: Jackrabbit Oak
>  Issue Type: Story
>  Components: core, mongomk, rdbmk
>Reporter: Robert Munteanu
>
> Create a MultiplexingDocumentStore implementation ( see OAK-3401 for details 
> ). Feature is developed for now at 
> https://github.com/rombert/jackrabbit-oak/tree/features/docstore-multiplex



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (OAK-3426) MultiplexingDocumentStore implementation

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved OAK-3426.
--
Resolution: Fixed

> MultiplexingDocumentStore implementation
> 
>
> Key: OAK-3426
> URL: https://issues.apache.org/jira/browse/OAK-3426
> Project: Jackrabbit Oak
>  Issue Type: Story
>  Components: core, mongomk, rdbmk
>Reporter: Robert Munteanu
>
> Create a MultiplexingDocumentStore implementation ( see OAK-3401 for details 
> ). Feature is developed for now at 
> https://github.com/rombert/jackrabbit-oak/tree/features/docstore-multiplex



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (OAK-3746) Enforce that a commit should not span across multiple DocumentStores

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved OAK-3746.
--
Resolution: Won't Fix

> Enforce that a commit should not span across multiple DocumentStores
> 
>
> Key: OAK-3746
> URL: https://issues.apache.org/jira/browse/OAK-3746
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>  Components: documentmk
>Reporter: Chetan Mehrotra
>
> For multiplexing to work properly it needs to be ensured that a single commit 
> must not span across multiple document stores if one of the document store is 
> private one.
> In case all the mounts are shared then this restriction does not apply



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (OAK-3428) Support setting a 'creator' store for multiplexed document stores

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved OAK-3428.
--
Resolution: Won't Fix

> Support setting a 'creator' store for multiplexed document stores
> -
>
> Key: OAK-3428
> URL: https://issues.apache.org/jira/browse/OAK-3428
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>  Components: core
>Reporter: Robert Munteanu
>
> When creating a document in a multiplexed document store ( e.g. a 
> MongoDocumentStore ), the document has a reference to the MongoDocumentStore, 
> but it should have a reference to the MultiplexingDocumentStore instead.
> This should be supported out-of-the box as a prerequisite for multiplexing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (OAK-3430) Provide tooling or documentation for creating mounts

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved OAK-3430.
--
Resolution: Won't Fix

> Provide tooling or documentation for creating mounts
> 
>
> Key: OAK-3430
> URL: https://issues.apache.org/jira/browse/OAK-3430
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>  Components: core, mongomk, rdbmk
>Reporter: Robert Munteanu
>
> It should be possible to quickly extract one of more sub-paths from an 
> existing repository and create a standalone collection from them, so it can 
> be mounted at startup.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (OAK-3427) Create a MultiplexingDocumentStore implementation

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved OAK-3427.
--
Resolution: Won't Fix

> Create a MultiplexingDocumentStore implementation
> -
>
> Key: OAK-3427
> URL: https://issues.apache.org/jira/browse/OAK-3427
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>  Components: core, mongomk, rdbmk
>Reporter: Robert Munteanu
>
> This task tracks the actual implementation of the MultiplexingDocumentStore:
> - Configuration API
> - Logic for delegating calls to mounted stores
> - Additional tests / fixtures required to validate the implementation



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-3426) MultiplexingDocumentStore implementation

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277575#comment-16277575
 ] 

Robert Munteanu commented on OAK-3426:
--

[~mreutegg] - I think not and I definitely don't plan on working on this 
anymore. Will resolve this and sub-tasks as _Won't fix_

> MultiplexingDocumentStore implementation
> 
>
> Key: OAK-3426
> URL: https://issues.apache.org/jira/browse/OAK-3426
> Project: Jackrabbit Oak
>  Issue Type: Story
>  Components: core, mongomk, rdbmk
>Reporter: Robert Munteanu
>
> Create a MultiplexingDocumentStore implementation ( see OAK-3401 for details 
> ). Feature is developed for now at 
> https://github.com/rombert/jackrabbit-oak/tree/features/docstore-multiplex



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (OAK-3429) Support determining the original document path when handling split documents

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved OAK-3429.
--
Resolution: Won't Fix

> Support determining the original document path when handling split documents
> 
>
> Key: OAK-3429
> URL: https://issues.apache.org/jira/browse/OAK-3429
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>  Components: core
>Reporter: Robert Munteanu
>
> Once a NodeDocument reaches a certain size it is split into multiple 
> sub-documents. These UpdateOp instances which are created do not have a 
> path-based id, so we should enhance them to point which document they are 
> tied to, so the multiplexing logic can work.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-7014) Build Jackrabbit Oak #1027 failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277467#comment-16277467
 ] 

Hudson commented on OAK-7014:
-

Previously failing build now is OK.
 Passed run: [Jackrabbit Oak 
#1045|https://builds.apache.org/job/Jackrabbit%20Oak/1045/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1045/console]

> Build Jackrabbit Oak #1027 failed
> -
>
> Key: OAK-7014
> URL: https://issues.apache.org/jira/browse/OAK-7014
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>
> No description is provided
> The build Jackrabbit Oak #1027 has failed.
> First failed run: [Jackrabbit Oak 
> #1027|https://builds.apache.org/job/Jackrabbit%20Oak/1027/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1027/console]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-7014) Build Jackrabbit Oak #1027 failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277295#comment-16277295
 ] 

Hudson commented on OAK-7014:
-

Previously failing build now is OK.
 Passed run: [Jackrabbit Oak 
#1044|https://builds.apache.org/job/Jackrabbit%20Oak/1044/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1044/console]

> Build Jackrabbit Oak #1027 failed
> -
>
> Key: OAK-7014
> URL: https://issues.apache.org/jira/browse/OAK-7014
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>
> No description is provided
> The build Jackrabbit Oak #1027 has failed.
> First failed run: [Jackrabbit Oak 
> #1027|https://builds.apache.org/job/Jackrabbit%20Oak/1027/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1027/console]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-7014) Build Jackrabbit Oak #1027 failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277153#comment-16277153
 ] 

Hudson commented on OAK-7014:
-

Previously failing build now is OK.
 Passed run: [Jackrabbit Oak 
#1043|https://builds.apache.org/job/Jackrabbit%20Oak/1043/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1043/console]

> Build Jackrabbit Oak #1027 failed
> -
>
> Key: OAK-7014
> URL: https://issues.apache.org/jira/browse/OAK-7014
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>
> No description is provided
> The build Jackrabbit Oak #1027 has failed.
> First failed run: [Jackrabbit Oak 
> #1027|https://builds.apache.org/job/Jackrabbit%20Oak/1027/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1027/console]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-7014) Build Jackrabbit Oak #1027 failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276985#comment-16276985
 ] 

Hudson commented on OAK-7014:
-

Previously failing build now is OK.
 Passed run: [Jackrabbit Oak 
#1042|https://builds.apache.org/job/Jackrabbit%20Oak/1042/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1042/console]

> Build Jackrabbit Oak #1027 failed
> -
>
> Key: OAK-7014
> URL: https://issues.apache.org/jira/browse/OAK-7014
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>
> No description is provided
> The build Jackrabbit Oak #1027 has failed.
> First failed run: [Jackrabbit Oak 
> #1027|https://builds.apache.org/job/Jackrabbit%20Oak/1027/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1027/console]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-6880) Build fails on a fresh m2 repo

[Julian Reschke (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-6880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276929#comment-16276929
 ] 

Julian Reschke commented on OAK-6880:
-

FWIW, I'm getting for {{mvn dependency:list-repositories}}:

{noformat}
[WARNING] Missing POM for org.restlet.jee:org.restlet:jar:2.1.1
[WARNING] Missing POM for org.restlet.jee:org.restlet.ext.servlet:jar:2.1.1
[INFO] Repositories Used by this build:
[INFO]   id: maven-restlet
  url: http://maven.restlet.org
   layout: default
snapshots: [enabled => true, update => daily]
 releases: [enabled => true, update => daily]
{noformat}

> Build fails on a fresh m2 repo
> --
>
> Key: OAK-6880
> URL: https://issues.apache.org/jira/browse/OAK-6880
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: parent
>Affects Versions: 1.8
>Reporter: Christian Schneider
>
> When I build from a fresh m2 repo with no special settings.xml I get this 
> failure:
> {noformat}
> [ERROR] Failed to execute goal on project oak-solr-core: Could not resolve 
> dependencies for project 
> org.apache.jackrabbit:oak-solr-core:bundle:1.8-SNAPSHOT: The following 
> artifacts could not be resolved: org.restlet.jee:org.restlet:jar:2.1.1, 
> org.restlet.jee:org.restlet.ext.servlet:jar:2.1.1: Failure to find 
> org.restlet.jee:org.restlet:jar:2.1.1 in https://repo.maven.apache.org/maven2 
> was cached in the local repository, resolution will not be reattempted until 
> the update interval of central has elapsed or updates are forced -> [Help 1]
> {noformat}
> It seems the restlet jars are only in the restlet maven repo.
> I will provide a PR.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-6880) Build fails on a fresh m2 repo

[Julian Reschke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-6880:

Description: 
When I build from a fresh m2 repo with no special settings.xml I get this 
failure:
{noformat}
[ERROR] Failed to execute goal on project oak-solr-core: Could not resolve 
dependencies for project 
org.apache.jackrabbit:oak-solr-core:bundle:1.8-SNAPSHOT: The following 
artifacts could not be resolved: org.restlet.jee:org.restlet:jar:2.1.1, 
org.restlet.jee:org.restlet.ext.servlet:jar:2.1.1: Failure to find 
org.restlet.jee:org.restlet:jar:2.1.1 in https://repo.maven.apache.org/maven2 
was cached in the local repository, resolution will not be reattempted until 
the update interval of central has elapsed or updates are forced -> [Help 1]
{noformat}

It seems the restlet jars are only in the restlet maven repo.
I will provide a PR.

  was:
When I build from a fresh m2 repo with no special settings.xml I get this 
failure:
[ERROR] Failed to execute goal on project oak-solr-core: Could not resolve 
dependencies for project 
org.apache.jackrabbit:oak-solr-core:bundle:1.8-SNAPSHOT: The following 
artifacts could not be resolved: org.restlet.jee:org.restlet:jar:2.1.1, 
org.restlet.jee:org.restlet.ext.servlet:jar:2.1.1: Failure to find 
org.restlet.jee:org.restlet:jar:2.1.1 in https://repo.maven.apache.org/maven2 
was cached in the local repository, resolution will not be reattempted until 
the update interval of central has elapsed or updates are forced -> [Help 1]

It seems the restlet jars are only in the restlet maven repo.
I will provide a PR.


> Build fails on a fresh m2 repo
> --
>
> Key: OAK-6880
> URL: https://issues.apache.org/jira/browse/OAK-6880
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: parent
>Affects Versions: 1.8
>Reporter: Christian Schneider
>
> When I build from a fresh m2 repo with no special settings.xml I get this 
> failure:
> {noformat}
> [ERROR] Failed to execute goal on project oak-solr-core: Could not resolve 
> dependencies for project 
> org.apache.jackrabbit:oak-solr-core:bundle:1.8-SNAPSHOT: The following 
> artifacts could not be resolved: org.restlet.jee:org.restlet:jar:2.1.1, 
> org.restlet.jee:org.restlet.ext.servlet:jar:2.1.1: Failure to find 
> org.restlet.jee:org.restlet:jar:2.1.1 in https://repo.maven.apache.org/maven2 
> was cached in the local repository, resolution will not be reattempted until 
> the update interval of central has elapsed or updates are forced -> [Help 1]
> {noformat}
> It seems the restlet jars are only in the restlet maven repo.
> I will provide a PR.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-7023) Replacement for DocumentMK.Builder

[Marcel Reutegger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcel Reutegger updated OAK-7023:
--
Attachment: OAK-7023.patch

Proposed changes in [^OAK-7023.patch].

The patch introduced three replacement classes for {{DocumentMK.Builder}}:
- {{DocumentNodeStoreBuilder}}: this is a generic builder with a default 
in-memory backend, primarily used for testing.
- {{MongoDocumentNodeStoreBuilder}}: this is a builder for the MongoDB backend, 
extending {{DocumentNodeStoreBuilder}}. It adds MongoDB specific methods to the 
base builder.
- {{RDBDocumentNodeStoreBuilder}}: this is a builder for the RDB backend, 
extending {{DocumentNodeStoreBuilder}}. It adds RDB specific methods to the 
base builder.

Usages of {{DocumentMK.Builder}} are replaced in production classes but test 
classes still use the now deprecated {{DocumentMK.Builder}}. The plan is to 
move the builder to test as well after the 1.8 release and at the same time 
remove the deprecation again.

> Replacement for DocumentMK.Builder
> --
>
> Key: OAK-7023
> URL: https://issues.apache.org/jira/browse/OAK-7023
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>  Components: documentmk
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
> Fix For: 1.8
>
> Attachments: OAK-7023.patch
>
>
> In order to move the class {{DocumentMK}} to test, the enclosed {{Builder}} 
> must be replaced.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-6880) Build fails on a fresh m2 repo

[Manfred Baedke (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-6880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276909#comment-16276909
 ] 

Manfred Baedke commented on OAK-6880:
-

FYI: I could reproduce this on Win10. The workaround suggested by Julian helps. 
I have no idea why it happens, though.

> Build fails on a fresh m2 repo
> --
>
> Key: OAK-6880
> URL: https://issues.apache.org/jira/browse/OAK-6880
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: parent
>Affects Versions: 1.8
>Reporter: Christian Schneider
>
> When I build from a fresh m2 repo with no special settings.xml I get this 
> failure:
> [ERROR] Failed to execute goal on project oak-solr-core: Could not resolve 
> dependencies for project 
> org.apache.jackrabbit:oak-solr-core:bundle:1.8-SNAPSHOT: The following 
> artifacts could not be resolved: org.restlet.jee:org.restlet:jar:2.1.1, 
> org.restlet.jee:org.restlet.ext.servlet:jar:2.1.1: Failure to find 
> org.restlet.jee:org.restlet:jar:2.1.1 in https://repo.maven.apache.org/maven2 
> was cached in the local repository, resolution will not be reattempted until 
> the update interval of central has elapsed or updates are forced -> [Help 1]
> It seems the restlet jars are only in the restlet maven repo.
> I will provide a PR.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OAK-7024) java.security.acl deprecated in Java 10, marked for removal in Java 11

[Julian Reschke (JIRA)]

Julian Reschke created OAK-7024:
---

 Summary: java.security.acl deprecated in Java 10, marked for 
removal in Java 11
 Key: OAK-7024
 URL: https://issues.apache.org/jira/browse/OAK-7024
 Project: Jackrabbit Oak
  Issue Type: Task
  Components: security
Reporter: Julian Reschke


See  and 
.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-7024) java.security.acl deprecated in Java 10, marked for removal in Java 11

[Julian Reschke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-7024:

Fix Version/s: 1.10

> java.security.acl deprecated in Java 10, marked for removal in Java 11
> --
>
> Key: OAK-7024
> URL: https://issues.apache.org/jira/browse/OAK-7024
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: security
>Reporter: Julian Reschke
> Fix For: 1.10
>
>
> See  and 
> .



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-4318) Upgrade oak-solr to Solr 5.x

[Tommaso Teofili (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276768#comment-16276768
 ] 

Tommaso Teofili commented on OAK-4318:
--

revert done in r1817091.

> Upgrade oak-solr to Solr 5.x
> 
>
> Key: OAK-4318
> URL: https://issues.apache.org/jira/browse/OAK-4318
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: solr
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 1.7.12
>
> Attachments: OAK-4318.patch
>
>
> Since we support JDK 1.7+ we can upgrade Solr to 5.x versions (not 6.0 as it 
> requires java 8 though).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-4318) Upgrade oak-solr to Solr 5.x

[Tommaso Teofili (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276765#comment-16276765
 ] 

Tommaso Teofili commented on OAK-4318:
--

given the current issues caused by this upgrade, I'll revert the changes 
outlined by [~reschke].
The plan is to include these changes again when unexpected side effects are 
fixed or mitigated.

> Upgrade oak-solr to Solr 5.x
> 
>
> Key: OAK-4318
> URL: https://issues.apache.org/jira/browse/OAK-4318
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: solr
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 1.7.12
>
> Attachments: OAK-4318.patch
>
>
> Since we support JDK 1.7+ we can upgrade Solr to 5.x versions (not 6.0 as it 
> requires java 8 though).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OAK-7023) Replacement for DocumentMK.Builder

[Marcel Reutegger (JIRA)]

Marcel Reutegger created OAK-7023:
-

 Summary: Replacement for DocumentMK.Builder
 Key: OAK-7023
 URL: https://issues.apache.org/jira/browse/OAK-7023
 Project: Jackrabbit Oak
  Issue Type: Technical task
  Components: documentmk
Reporter: Marcel Reutegger
Assignee: Marcel Reutegger
 Fix For: 1.8


In order to move the class {{DocumentMK}} to test, the enclosed {{Builder}} 
must be replaced.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (OAK-5028) Remove DocumentStore.update()

[Davide Giannella (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davide Giannella closed OAK-5028.
-

Bulk close 1.6.7

> Remove DocumentStore.update()
> -
>
> Key: OAK-5028
> URL: https://issues.apache.org/jira/browse/OAK-5028
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: documentmk, mongomk, rdbmk
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>  Labels: technical_debt
> Fix For: 1.8, 1.7.12, 1.6.7
>
>
> OAK-3018 removed the single production usage of DocumentStore.update(). I 
> propose we remove the method to reduce maintenance.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (OAK-6454) Inaccurate data in the oak-upgrade progress logger

[Davide Giannella (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davide Giannella closed OAK-6454.
-

Bulk close 1.6.7

> Inaccurate data in the oak-upgrade progress logger
> --
>
> Key: OAK-6454
> URL: https://issues.apache.org/jira/browse/OAK-6454
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: upgrade
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
> Fix For: 1.8, 1.2.28, 1.0.40, 1.4.19, 1.7.12, 1.6.7
>
>
> After recent oak-upgrade improvements related to the checkpoint migration, 
> the node counter inside the progress logger displays 2 times higher values.
> The progress logger should be fixed to provide more accurate values.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (OAK-6971) Remove composite node store-related features from the oak-upgrade

[Davide Giannella (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davide Giannella closed OAK-6971.
-

Bulk close 1.6.7

> Remove composite node store-related features from the oak-upgrade
> -
>
> Key: OAK-6971
> URL: https://issues.apache.org/jira/browse/OAK-6971
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: upgrade
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
> Fix For: 1.8, 1.0.40, 1.4.19, 1.7.12, 1.6.7
>
>
> Following features were added to the oak-upgrade so it can be used to prepare 
> the composite node store repository:
> * include-index
> * fragment-paths
> * exclude-fragments
> However, since the InitialContentMigrator exists, oak-upgrade doesn't need to 
> be used for this purpose, so the features can be removed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (OAK-6860) RDB*Store: update Derby to release 10.14

[Davide Giannella (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davide Giannella closed OAK-6860.
-

Bulk close 1.6.7

> RDB*Store: update Derby to release 10.14
> 
>
> Key: OAK-6860
> URL: https://issues.apache.org/jira/browse/OAK-6860
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>  Components: rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.8, 1.7.12, 1.6.7
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (OAK-6953) CacheLIRS cannot be disabled

[Davide Giannella (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davide Giannella closed OAK-6953.
-

Bulk close 1.6.7

> CacheLIRS cannot be disabled
> 
>
> Key: OAK-6953
> URL: https://issues.apache.org/jira/browse/OAK-6953
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: documentmk
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Minor
> Fix For: 1.8, 1.2.28, 1.0.40, 1.4.19, 1.7.12, 1.6.7
>
>
> The CacheLIRS cannot be disabled by setting the maxWeight to zero whereas the 
> Guava implementation can be disabled this way. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (OAK-6784) Exceptions are inhibited in oak-run compact

[Davide Giannella (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davide Giannella closed OAK-6784.
-

Bulk close 1.6.7

> Exceptions are inhibited in oak-run compact
> ---
>
> Key: OAK-6784
> URL: https://issues.apache.org/jira/browse/OAK-6784
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run, segment-tar
>Affects Versions: 1.7.8, 1.6.5
>Reporter: Valentin Olteanu
>Assignee: Francesco Mari
>  Labels: compaction, gc, tooling
> Fix For: 1.8, 1.7.12, 1.6.7
>
>
> Exceptions thrown by {{oak-run compact}} are inhibited so the exit code of 
> the command is not correct in case of error. 
> Example: 
> {code}
> $ java -jar oak-run-1.7.8-R1809845.jar compact test-oak-run/
> Apache Jackrabbit Oak 1.7.8-R1809845
> Compacting test-oak-run-6.3.0
> With default access mode
> before
> Thu Oct 05 15:14:22 CEST 2017, journal.log
> Thu Oct 05 15:14:23 CEST 2017, data0a.tar
> Thu Oct 05 15:14:23 CEST 2017, manifest
> Thu Oct 05 15:14:23 CEST 2017, repo.lock
> size 119.1 MB (119133142 bytes)
> -> compacting
> org.apache.jackrabbit.oak.segment.file.InvalidFileStoreVersionException: 
> Using a too recent version of oak-segment-tar
>   at 
> org.apache.jackrabbit.oak.segment.file.ManifestChecker.checkStoreVersion(ManifestChecker.java:81)
>   at 
> org.apache.jackrabbit.oak.segment.file.ManifestChecker.checkManifest(ManifestChecker.java:70)
>   at 
> org.apache.jackrabbit.oak.segment.file.ManifestChecker.checkAndUpdateManifest(ManifestChecker.java:51)
>   at 
> org.apache.jackrabbit.oak.segment.file.FileStore.(FileStore.java:191)
>   at 
> org.apache.jackrabbit.oak.segment.file.FileStoreBuilder.build(FileStoreBuilder.java:343)
>   at 
> org.apache.jackrabbit.oak.segment.tool.Compact.newFileStore(Compact.java:165)
>   at 
> org.apache.jackrabbit.oak.segment.tool.Compact.compact(Compact.java:135)
>   at org.apache.jackrabbit.oak.segment.tool.Compact.run(Compact.java:128)
>   at 
> org.apache.jackrabbit.oak.run.SegmentTarUtils.compact(SegmentTarUtils.java:183)
>   at 
> org.apache.jackrabbit.oak.run.CompactCommand.execute(CompactCommand.java:93)
>   at org.apache.jackrabbit.oak.run.Main.main(Main.java:49)
> after
> Thu Oct 05 15:14:22 CEST 2017, journal.log
> Thu Oct 05 15:14:23 CEST 2017, data0a.tar
> Thu Oct 05 15:14:23 CEST 2017, manifest
> Thu Oct 05 15:14:23 CEST 2017, repo.lock
> size 119.1 MB (119133142 bytes)
> removed files []
> added files []
> Compaction succeeded in 211.9 ms (0s).
> {code}
> A quick fix would be to wrap the exception into a {{RuntimeException}}:
> {code}
> --- 
> a/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/tool/Compact.java
> +++ 
> b/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/tool/Compact.java
> @@ -127,7 +127,7 @@ public class Compact implements Runnable {
>  try {
>  compact();
>  } catch (Exception e) {
> -e.printStackTrace();
> +throw new RuntimeException("Failed to run compact", e);
>  }
>  }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (OAK-6931) Enable the -Dcache of offline compaction

[Davide Giannella (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davide Giannella closed OAK-6931.
-

Bulk close 1.6.7

> Enable the -Dcache of offline compaction
> 
>
> Key: OAK-6931
> URL: https://issues.apache.org/jira/browse/OAK-6931
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: segment-tar
>Affects Versions: 1.6.7
>Reporter: Michael Dürig
>Assignee: Michael Dürig
>  Labels: compaction, gc, tooling
> Fix For: 1.8, 1.7.12, 1.6.7
>
> Attachments: OAK-6931.patch
>
>
> The {{-Dcache}} option currently has no effect when used in conjunction with 
> the {{compact}} run mode of {{oak-run}}. However we should enable users to 
> configure the segment cache size through this option if necessary. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (OAK-6872) Update Oak 1.6 to Jackrabbit 2.14.4

[Davide Giannella (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davide Giannella closed OAK-6872.
-

Bulk close 1.6.7

> Update Oak 1.6 to Jackrabbit 2.14.4
> ---
>
> Key: OAK-6872
> URL: https://issues.apache.org/jira/browse/OAK-6872
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.6.7
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (OAK-6985) RDBDocumentStoreJDBC: remove unused parameter

[Davide Giannella (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davide Giannella closed OAK-6985.
-

Bulk close 1.6.7

> RDBDocumentStoreJDBC: remove unused parameter
> -
>
> Key: OAK-6985
> URL: https://issues.apache.org/jira/browse/OAK-6985
> Project: Jackrabbit Oak
>  Issue Type: Technical task
>  Components: rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Trivial
>  Labels: candidate_oak_1_4
> Fix For: 1.8, 1.7.12, 1.6.7
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-4318) Upgrade oak-solr to Solr 5.x

[Julian Reschke (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276689#comment-16276689
 ] 

Julian Reschke commented on OAK-4318:
-

trunk: [r1817076|http://svn.apache.org/r1817076] 
[r1816834|http://svn.apache.org/r1816834] 
[r1816721|http://svn.apache.org/r1816721]


> Upgrade oak-solr to Solr 5.x
> 
>
> Key: OAK-4318
> URL: https://issues.apache.org/jira/browse/OAK-4318
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: solr
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 1.7.12
>
> Attachments: OAK-4318.patch
>
>
> Since we support JDK 1.7+ we can upgrade Solr to 5.x versions (not 6.0 as it 
> requires java 8 though).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-7014) Build Jackrabbit Oak #1027 failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276683#comment-16276683
 ] 

Hudson commented on OAK-7014:
-

Build is still failing.
Failed run: [Jackrabbit Oak 
#1040|https://builds.apache.org/job/Jackrabbit%20Oak/1040/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1040/console]

> Build Jackrabbit Oak #1027 failed
> -
>
> Key: OAK-7014
> URL: https://issues.apache.org/jira/browse/OAK-7014
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>
> No description is provided
> The build Jackrabbit Oak #1027 has failed.
> First failed run: [Jackrabbit Oak 
> #1027|https://builds.apache.org/job/Jackrabbit%20Oak/1027/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1027/console]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (OAK-2907) Move DocumentMK to test

[Marcel Reutegger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcel Reutegger reassigned OAK-2907:
-

Assignee: Marcel Reutegger  (was: Thomas Mueller)

> Move DocumentMK to test
> ---
>
> Key: OAK-2907
> URL: https://issues.apache.org/jira/browse/OAK-2907
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: documentmk
>Reporter: Thomas Mueller
>Assignee: Marcel Reutegger
>  Labels: technical_debt
>
> The DocumentMK class is not directly used (when using the JCR API), but it is 
> only really used by tests. So it should be moved to tests.
> The DocumentMK.Builder class needs to be moved first (to a top level class 
> for example).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-7014) Build Jackrabbit Oak #1027 failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276616#comment-16276616
 ] 

Hudson commented on OAK-7014:
-

Build is still failing.
Failed run: [Jackrabbit Oak 
#1039|https://builds.apache.org/job/Jackrabbit%20Oak/1039/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1039/console]

> Build Jackrabbit Oak #1027 failed
> -
>
> Key: OAK-7014
> URL: https://issues.apache.org/jira/browse/OAK-7014
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>
> No description is provided
> The build Jackrabbit Oak #1027 has failed.
> First failed run: [Jackrabbit Oak 
> #1027|https://builds.apache.org/job/Jackrabbit%20Oak/1027/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1027/console]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (OAK-3658) Test failures: JackrabbitNodeTest#testRename and testRenameEventHandling

[Amit Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276530#comment-16276530
 ] 

Amit Jain edited comment on OAK-3658 at 12/4/17 10:25 AM:
--

I re-enabled the tests with http://svn.apache.org/viewvc?rev=1817075&view=rev 
as they are passing locally for me.

UPDATE: Disabled again as failing 
https://builds.apache.org/job/Jackrabbit%20Oak/1038/


was (Author: amitjain):
I re-enabled the tests with http://svn.apache.org/viewvc?rev=1817075&view=rev 
as they are passing locally for me.

> Test failures: JackrabbitNodeTest#testRename and testRenameEventHandling
> 
>
> Key: OAK-3658
> URL: https://issues.apache.org/jira/browse/OAK-3658
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: jcr
>Reporter: Amit Jain
>Assignee: Amit Jain
>Priority: Minor
> Fix For: 1.8
>
>
> Tests fail regularly on trunk - {{JackrabbitNodeTest#testRename}} and 
> {{JackrabbitNodeTest#testRenameEventHandling}}.
> {noformat}
> Test set: org.apache.jackrabbit.oak.jcr.JackrabbitNodeTest
> ---
> Tests run: 8, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 0.106 sec <<< 
> FAILURE!
> testRenameEventHandling(org.apache.jackrabbit.oak.jcr.JackrabbitNodeTest)  
> Time elapsed: 0.01 sec  <<< ERROR!
> javax.jcr.nodetype.ConstraintViolationException: Item is protected.
>   at 
> org.apache.jackrabbit.oak.jcr.session.ItemImpl$ItemWriteOperation.checkPreconditions(ItemImpl.java:98)
>   at 
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.prePerform(SessionDelegate.java:614)
>   at 
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.performVoid(SessionDelegate.java:270)
>   at 
> org.apache.jackrabbit.oak.jcr.session.NodeImpl.rename(NodeImpl.java:1485)
>   at 
> org.apache.jackrabbit.oak.jcr.JackrabbitNodeTest.testRenameEventHandling(JackrabbitNodeTest.java:124)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at 
> org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:464)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> testRename(org.apache.jackrabbit.oak.jcr.JackrabbitNodeTest)  Time elapsed: 
> 0.007 sec  <<< FAILURE!
> junit.framework.ComparisonFailure: expected:<[a]> but was:<[rep:policy]>
>   at junit.framework.Assert.assertEquals(Assert.java:100)
>   at junit.framework.Assert.assertEquals(Assert.java:107)
>   at junit.framework.TestCase.assertEquals(TestCase.java:269)
>   at 
> org.apache.jackrabbit.oak.jcr.JackrabbitNodeTest.testRename(JackrabbitNodeTest.java:74)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun

[jira] [Commented] (OAK-7014) Build Jackrabbit Oak #1027 failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276588#comment-16276588
 ] 

Hudson commented on OAK-7014:
-

Build is still failing.
Failed run: [Jackrabbit Oak 
#1038|https://builds.apache.org/job/Jackrabbit%20Oak/1038/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1038/console]

> Build Jackrabbit Oak #1027 failed
> -
>
> Key: OAK-7014
> URL: https://issues.apache.org/jira/browse/OAK-7014
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>
> No description is provided
> The build Jackrabbit Oak #1027 has failed.
> First failed run: [Jackrabbit Oak 
> #1027|https://builds.apache.org/job/Jackrabbit%20Oak/1027/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1027/console]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-6702) Improve cold standby resiliency to incoherent configs

[JIRA]

 [ 
https://issues.apache.org/jira/browse/OAK-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Dürig updated OAK-6702:
---
Fix Version/s: (was: 1.8)

> Improve cold standby resiliency to incoherent configs
> -
>
> Key: OAK-6702
> URL: https://issues.apache.org/jira/browse/OAK-6702
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: segment-tar, tarmk-standby
>Affects Versions: 1.7.0
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>  Labels: cold-standby, resilience
>
> In order to correctly configure cold standby there are two OSGi 
> configurations that need to be provided. Among other settings, 
> {{org.apache.jackrabbit.oak.segment.SegmentNodeStoreService.config}} needs 
> {{standby=B"true"}} and 
> {{org.apache.jackrabbit.oak.segment.standby.store.StandbyStoreService.config}}
>  needs {{mode="standby"}}. The problem is that sometimes we have 
> {{mode="standby"}} in {{StandbyStoreService}} and {{standby=B"false"}} in 
> {{SegmentNodeStoreService}} which leads to starting a problematic standby 
> instance (with primary behaviour enabled, e.g. indexing, etc.). This problem 
> stems from the fact that there are two components whose configuration should 
> be coordinated. Proposals to mitigate this:
> # Keep the {{mode="standby"}}, but merge the configuration of 
> {{StandbyStoreService}} in the one for {{SegmentNodeStoreService}} and 
> eliminate {{StandbyStoreService}} altogether
> # {{StandbyStoreService}} should derive {{mode="standby"}} from 
> {{"standby=B"true"}} in {{SegmentNodeStoreService}}
> # {{SegmentNodeStoreService}} should derive {{"standby=B"true"}} from 
> {{mode="standby"}} in {{StandbyStoreService}} even if this is backwards when 
> compared to how the synchronization currently happens, with 
> {{StandbyStoreService}} waiting for for a proper initialisation of 
> {{SegmentNodeStoreService}}
> # Make {{StandbyStoreService}} configuration mandatory, but require a 
> {{mode="off"}} setting. This way the removal of {{standby=B"true"}} from 
> {{SegmentNodeStoreService}} would be guaranteed and any synchronization 
> between the two components would be avoided.
> /cc  [~frm], [~volteanu], [~mduerig]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OAK-7022) Prepare for usage of Root/TreeProvider in security tests

[angela (JIRA)]

angela created OAK-7022:
---

 Summary: Prepare for usage of Root/TreeProvider in security tests
 Key: OAK-7022
 URL: https://issues.apache.org/jira/browse/OAK-7022
 Project: Jackrabbit Oak
  Issue Type: Sub-task
  Components: core
Reporter: angela
Assignee: angela






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-7021) Collect DocumentStore stats as part of status zip

[Chetan Mehrotra (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276542#comment-16276542
 ] 

Chetan Mehrotra commented on OAK-7021:
--

[~mreutegg] [~catholicon] [~julian.resc...@gmx.de] Probably we can add a 
generic method to DocumentStore

{noformat}
void dumpStats(PrintWriter printWriter)
{noformat}

And have implementation for both stores. This can then be used by an 
InventoryPrinter implementation to include this info with config zip. Also same 
can be exposed via JMX

> Collect DocumentStore stats as part of status zip
> -
>
> Key: OAK-7021
> URL: https://issues.apache.org/jira/browse/OAK-7021
> Project: Jackrabbit Oak
>  Issue Type: New Feature
>  Components: documentmk
>Reporter: Chetan Mehrotra
> Fix For: 1.8
>
>
> Many times while investigating issue we request customer to provide Mongo db 
> stats. It would be useful if there is an InventoryPrinter for DocumentStore 
> which dumps various stats
> Some useful stats would be
> * Number of entries in "nodes" collection
> * Index memory size
> * Node collection size on disk
> * Number of cluster members which are active
> See OAK-6179 for inventory printer related details



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OAK-7021) Collect DocumentStore stats as part of status zip

[Chetan Mehrotra (JIRA)]

Chetan Mehrotra created OAK-7021:


 Summary: Collect DocumentStore stats as part of status zip
 Key: OAK-7021
 URL: https://issues.apache.org/jira/browse/OAK-7021
 Project: Jackrabbit Oak
  Issue Type: New Feature
  Components: documentmk
Reporter: Chetan Mehrotra
 Fix For: 1.8


Many times while investigating issue we request customer to provide Mongo db 
stats. It would be useful if there is an InventoryPrinter for DocumentStore 
which dumps various stats

Some useful stats would be
* Number of entries in "nodes" collection
* Index memory size
* Node collection size on disk
* Number of cluster members which are active

See OAK-6179 for inventory printer related details



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-7014) Build Jackrabbit Oak #1027 failed

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276533#comment-16276533
 ] 

Hudson commented on OAK-7014:
-

Build is still failing.
Failed run: [Jackrabbit Oak 
#1037|https://builds.apache.org/job/Jackrabbit%20Oak/1037/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/1037/console]

> Build Jackrabbit Oak #1027 failed
> -
>
> Key: OAK-7014
> URL: https://issues.apache.org/jira/browse/OAK-7014
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>
> No description is provided
> The build Jackrabbit Oak #1027 has failed.
> First failed run: [Jackrabbit Oak 
> #1027|https://builds.apache.org/job/Jackrabbit%20Oak/1027/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1027/console]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OAK-3658) Test failures: JackrabbitNodeTest#testRename and testRenameEventHandling

[Amit Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276530#comment-16276530
 ] 

Amit Jain commented on OAK-3658:


I re-enabled the tests with http://svn.apache.org/viewvc?rev=1817075&view=rev 
as they are passing locally for me.

> Test failures: JackrabbitNodeTest#testRename and testRenameEventHandling
> 
>
> Key: OAK-3658
> URL: https://issues.apache.org/jira/browse/OAK-3658
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: jcr
>Reporter: Amit Jain
>Assignee: Amit Jain
>Priority: Minor
> Fix For: 1.8
>
>
> Tests fail regularly on trunk - {{JackrabbitNodeTest#testRename}} and 
> {{JackrabbitNodeTest#testRenameEventHandling}}.
> {noformat}
> Test set: org.apache.jackrabbit.oak.jcr.JackrabbitNodeTest
> ---
> Tests run: 8, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 0.106 sec <<< 
> FAILURE!
> testRenameEventHandling(org.apache.jackrabbit.oak.jcr.JackrabbitNodeTest)  
> Time elapsed: 0.01 sec  <<< ERROR!
> javax.jcr.nodetype.ConstraintViolationException: Item is protected.
>   at 
> org.apache.jackrabbit.oak.jcr.session.ItemImpl$ItemWriteOperation.checkPreconditions(ItemImpl.java:98)
>   at 
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.prePerform(SessionDelegate.java:614)
>   at 
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.performVoid(SessionDelegate.java:270)
>   at 
> org.apache.jackrabbit.oak.jcr.session.NodeImpl.rename(NodeImpl.java:1485)
>   at 
> org.apache.jackrabbit.oak.jcr.JackrabbitNodeTest.testRenameEventHandling(JackrabbitNodeTest.java:124)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at 
> org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:464)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> testRename(org.apache.jackrabbit.oak.jcr.JackrabbitNodeTest)  Time elapsed: 
> 0.007 sec  <<< FAILURE!
> junit.framework.ComparisonFailure: expected:<[a]> but was:<[rep:policy]>
>   at junit.framework.Assert.assertEquals(Assert.java:100)
>   at junit.framework.Assert.assertEquals(Assert.java:107)
>   at junit.framework.TestCase.assertEquals(TestCase.java:269)
>   at 
> org.apache.jackrabbit.oak.jcr.JackrabbitNodeTest.testRename(JackrabbitNodeTest.java:74)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at j

[jira] [Commented] (OAK-7007) Test failure: FacetTest.testFacetsNA()

[Marcel Reutegger (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-7007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276463#comment-16276463
 ] 

Marcel Reutegger commented on OAK-7007:
---

No, I was unable to reproduce this locally. Please also keep in mind the 
environment on travis. The 1.4 branch is building with OpenJDK 7. Unfortunately 
it's not that easy to get files from a travis build, but what you could try is 
running a build on a fork where the log messages are written to the console.

> Test failure: FacetTest.testFacetsNA()
> --
>
> Key: OAK-7007
> URL: https://issues.apache.org/jira/browse/OAK-7007
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: lucene
> Environment: OpenJDK 7
>Reporter: Marcel Reutegger
>Assignee: Vikas Saurabh
> Fix For: 1.4.19
>
>
> Builds on travis fail rather consistently on the 1.4 branch.
> Most recently https://travis-ci.org/apache/jackrabbit-oak/builds/305370560
> The failure is:
> {noformat}
> java.lang.RuntimeException: java.lang.RuntimeException: 
> java.lang.NullPointerException
>   at 
> org.apache.jackrabbit.oak.query.facet.FacetResult.(FacetResult.java:63)
>   at 
> org.apache.jackrabbit.oak.jcr.query.FacetTest.testFacetsNA(FacetTest.java:115)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at 
> org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:464)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.lang.RuntimeException: java.lang.NullPointerException
>   at 
> org.apache.jackrabbit.oak.plugins.index.lucene.LucenePropertyIndex$LucenePathCursor$2.getValue(LucenePropertyIndex.java:1628)
>   at 
> org.apache.jackrabbit.oak.query.ast.SelectorImpl.currentOakProperty(SelectorImpl.java:679)
>   at 
> org.apache.jackrabbit.oak.query.ast.SelectorImpl.currentOakProperty(SelectorImpl.java:652)
>   at 
> org.apache.jackrabbit.oak.query.ast.SelectorImpl.currentOakProperty(SelectorImpl.java:584)
>   at 
> org.apache.jackrabbit.oak.query.ast.FacetColumnImpl.currentProperty(FacetColumnImpl.java:33)
>   at 
> org.apache.jackrabbit.oak.query.QueryImpl.currentRow(QueryImpl.java:885)
>   at 
> org.apache.jackrabbit.oak.query.QueryImpl$RowIterator.fetchNext(QueryImpl.java:826)
>   at 
> org.apache.jackrabbit.oak.query.QueryImpl$RowIterator.hasNext(QueryImpl.java:849)
>   at 
> org.apache.jackrabbit.oak.jcr.query.QueryResultImpl$1.fetch(QueryResultImpl.java:98)
>   at 
> org.apache.jackrabbit.oak.jcr.query.QueryResultImpl$1.(QueryResultImpl.java:94)
>   at 
> org.apache.jackrabbit.oak.jcr.query.QueryResultImpl.getRows(QueryResultImpl.java:78)
>   at 
> org.apache.jackrabbit.oak.query.facet.FacetResult.(FacetResult.java:48)
>   ... 27 more
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.jackrabbit.oak.plugins.index.lucene.util.

[jira] [Comment Edited] (OAK-6551) Add an option to datastorecheck command to include path details in the missing blobs report

[Amit Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/OAK-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276449#comment-16276449
 ] 

Amit Jain edited comment on OAK-6551 at 12/4/17 8:44 AM:
-

Done with http://svn.apache.org/viewvc?rev=1817067&view=rev & 
http://svn.apache.org/viewvc?rev=1817069&view=rev


was (Author: amitjain):
Done with http://svn.apache.org/viewvc?rev=1817067&view=rev

> Add an option to datastorecheck command to include path details in the 
> missing blobs report
> ---
>
> Key: OAK-6551
> URL: https://issues.apache.org/jira/browse/OAK-6551
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: run
>Reporter: Amit Jain
>Assignee: Amit Jain
> Fix For: 1.8, 1.7.12
>
>
> Currently, the path information is not reported for missing blobs identified 
> for the SegmentNodeStore which makes any remedial action on the missing blobs 
> quite difficult . This is due to the fact that the references are retrieved 
> using Segment tar's optimized index. 
> To have the path info a new option (slower mode, name to TBD) should be added 
> which when specified would also iterate over the node structure to identify 
> the blob references along with the path information. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (OAK-6551) Add an option to datastorecheck command to include path details in the missing blobs report

[Amit Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amit Jain resolved OAK-6551.

   Resolution: Fixed
Fix Version/s: 1.7.12

Done with http://svn.apache.org/viewvc?rev=1817067&view=rev

> Add an option to datastorecheck command to include path details in the 
> missing blobs report
> ---
>
> Key: OAK-6551
> URL: https://issues.apache.org/jira/browse/OAK-6551
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: run
>Reporter: Amit Jain
>Assignee: Amit Jain
> Fix For: 1.8, 1.7.12
>
>
> Currently, the path information is not reported for missing blobs identified 
> for the SegmentNodeStore which makes any remedial action on the missing blobs 
> quite difficult . This is due to the fact that the references are retrieved 
> using Segment tar's optimized index. 
> To have the path info a new option (slower mode, name to TBD) should be added 
> which when specified would also iterate over the node structure to identify 
> the blob references along with the path information. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-6899) Add explicit dependency versions for aws-java-sdk in oak-run

[Amit Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amit Jain updated OAK-6899:
---
Fix Version/s: (was: 1.7.13)
   1.7.12

> Add explicit dependency versions for aws-java-sdk in oak-run
> 
>
> Key: OAK-6899
> URL: https://issues.apache.org/jira/browse/OAK-6899
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: run
>Reporter: Amit Jain
>Assignee: Amit Jain
> Fix For: 1.8, 1.7.12
>
>
> Versions of jars required by aws-java-sdk should be explicitly defined in 
> oak-run



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OAK-6489) Datastorecheck command should output the path of missing datastore

[Amit Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amit Jain updated OAK-6489:
---
Fix Version/s: (was: 1.7.13)
   1.7.12

> Datastorecheck command should output the path of missing datastore
> --
>
> Key: OAK-6489
> URL: https://issues.apache.org/jira/browse/OAK-6489
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: run
>Affects Versions: 1.4.17
>Reporter: Ankush Bangroo
>Assignee: Amit Jain
> Fix For: 1.8, 1.7.12
>
>
> Datastorecheck command should output the path of missing datastore. Currently 
> it prints only blobIds.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (OAK-6586) [oak-run] Add option to datastorecheck command to report misconfigured external binary references

[Amit Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OAK-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amit Jain resolved OAK-6586.

   Resolution: Fixed
Fix Version/s: (was: 1.7.13)
   1.7.12

> [oak-run] Add option to datastorecheck command to report misconfigured 
> external binary references
> -
>
> Key: OAK-6586
> URL: https://issues.apache.org/jira/browse/OAK-6586
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: run
>Reporter: Arek Kita
>Assignee: Amit Jain
> Fix For: 1.8, 1.7.12
>
>
> It would be good if we could create OOTB check in oak-run that could scan Oak 
> repositories looking for any binaries that might be missing mostly due to 2 
> reasons:
> * binaries that are not inlined _when_ BlobStore/DataStore is not defined 
> (the assumption is we have *+only+* inlined binaries and we would like to 
> verify such hypothesis, external reference exists but shouldn't and no DS is 
> known, i.e. a result of misconfiguration)
> * missing binaries in defined BlobStore/DataStore (external references exist 
> but no binary is present at DataStore)
> _This might also be also very helpful debugging repository in the future with 
> CompositeBlobStore layouts._
> I see that this is is often the case and it causes problems during migration 
> (upgrades, sidegrades) of stores. The knowledge which JCR paths are affected 
> would be a great help for Oak users.
> The following groovy script does this but I thought about something built-in.
> {code}
> // usage:
> // java -jar oak-run-1.4.6.jar console --fds-path 
> crx-quickstart/repository/datastore crx-quickstart/repository/segmentstore 
> ":load find-missing-blobs.groovy"
> import org.apache.jackrabbit.oak.api.PropertyState
> import org.apache.jackrabbit.oak.api.Type
> import org.apache.jackrabbit.oak.commons.PathUtils
> import org.apache.jackrabbit.oak.spi.state.ChildNodeEntry
> import org.apache.jackrabbit.oak.spi.state.NodeState
> org.slf4j.LoggerFactory.getLogger(ch.qos.logback.classic.Logger.ROOT_LOGGER_NAME).setLevel(ch.qos.logback.classic.Level.OFF)
> class MissingBlobFinder {
> static checkProperties(state, String path) {
> for (PropertyState p : state.properties) {
> try {
> if (p.type == Type.BINARY) {
> InputStream is = p.getValue(Type.BINARY).newStream
> is.read()
> is.close()
> } else if (p.type == Type.BINARIES && p.count() > 0) {
> InputStream is = 
> p.getValue(Type.BINARIES).iterator().next().newStream
> is.read()
> is.close()
> }
> } catch (Exception e) {
> System.out.println(PathUtils.concat(path, p.name))
> }
> }
> }
> static traverse(NodeState state, String path) {
> checkProperties(state, path)
> for (ChildNodeEntry c : state.childNodeEntries) {
> traverse(c.nodeState, PathUtils.concat(path, c.name))
> }
> }
> static runFixer(session) {
> System.out.println("---")
> System.out.println("List of missing blobs:")
> System.out.println()
> traverse(session.store.root, "/")
> System.out.println("---")
> null
> }
> }
> MissingBlobFinder.runFixer(session)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)