[jira] [Created] (OAK-6830) RDBDocumentStore: allow schema evolution part 3: default to version 1 for creation, improve RDBHelper
Julian Reschke created OAK-6830:
---
Summary: RDBDocumentStore: allow schema evolution part 3: default
to version 1 for creation, improve RDBHelper
Key: OAK-6830
URL: https://issues.apache.org/jira/browse/OAK-6830
Project: Jackrabbit Oak
Issue Type: Bug
Components: rdbmk
Reporter: Julian Reschke
Assignee: Julian Reschke
- set initial version to "1" (upgrade is covered by
{{RDBDocumentStoreSchemaUpgradeTest}})
- improve {{RDBHelper}} to print out upgrade statements
- add link to {{RDBHelper}} in {{RDBDocumentStore}} javadoc
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6830) RDBDocumentStore: allow schema evolution part 3: default to version 1 for creation, improve RDBHelper
[
https://issues.apache.org/jira/browse/OAK-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-6830:
Issue Type: Improvement (was: Bug)
> RDBDocumentStore: allow schema evolution part 3: default to version 1 for
> creation, improve RDBHelper
> -
>
> Key: OAK-6830
> URL: https://issues.apache.org/jira/browse/OAK-6830
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>
> - set initial version to "1" (upgrade is covered by
> {{RDBDocumentStoreSchemaUpgradeTest}})
> - improve {{RDBHelper}} to print out upgrade statements
> - add link to {{RDBHelper}} in {{RDBDocumentStore}} javadoc
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6207) RDBDocumentStore: allow schema evolution part 2: record schema version when updating/inserting rows
[ https://issues.apache.org/jira/browse/OAK-6207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6207: Issue Type: Improvement (was: Technical task) Parent: (was: OAK-1266) > RDBDocumentStore: allow schema evolution part 2: record schema version when > updating/inserting rows > --- > > Key: OAK-6207 > URL: https://issues.apache.org/jira/browse/OAK-6207 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk, rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, > candidate_oak_1_6 > Fix For: 1.7.0, 1.8 > > Attachments: OAK-6207.diff, OAK-6207.diff, OAK-6207.diff > > > Currently, new/extra columns get reported on startup but then are ignored. > This allows evolving the schema without immediately breaking existing > installs. However, we won't know whether a value in a new column was put > there deliberately or just wasn't updated properly by old code. > Idea: > - add a new "VERSION" column > - when inserting/updating rows, record the DB schema version understood by > the code doing the update > Advantages: > - allows relatively easy check what versions of code are writing to the DB > - inexpensive > - helps finding rows that need a migration step > Disadvantage: > - the row itself will be unreliably until all instances connecting to the DB > maintain it -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-3739) RDBDocumentStore: allow schema evolution part 1: check for required columns, log unexpected new columns
[ https://issues.apache.org/jira/browse/OAK-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-3739: Issue Type: Improvement (was: Technical task) Parent: (was: OAK-1266) > RDBDocumentStore: allow schema evolution part 1: check for required columns, > log unexpected new columns > --- > > Key: OAK-3739 > URL: https://issues.apache.org/jira/browse/OAK-3739 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: rdbmk >Affects Versions: 1.0.25, 1.2.9, 1.3.13 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.0.26, 1.2.10, 1.3.14, 1.4 > > > In the future, we may have to add new table columns (for instance, see > OAK-3730). > We can somewhat decouple database changes from code changes by only using new > columns when they are present. > However, we need to make sure that once the columns have been added and the > system has started to use them, no older code writes to the DB (potentially > causing inconsistencies because of not updating these columns). > To prevent this, code could check that it understands all columns it finds on > startup. If there are unknown columns, it would need to abort and log an > error that explains the compatibility issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6206) ExternalPrivateStoreIT.testProxyFlippedIntermediateByteChange2 failing
[
https://issues.apache.org/jira/browse/OAK-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-6206:
Attachment: (was:
org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT-output.txt)
> ExternalPrivateStoreIT.testProxyFlippedIntermediateByteChange2 failing
> --
>
> Key: OAK-6206
> URL: https://issues.apache.org/jira/browse/OAK-6206
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: tarmk-standby
>Affects Versions: 1.4.15, 1.6.1
>Reporter: Julian Reschke
>
> This test currently fails for me frequently with:
> {noformat}
> testProxyFlippedIntermediateByteChange2(org.apache.jackrabbit.oak.plugins.segment.standby.ExternalPrivateStoreIT)
> Time elapsed: 0.794 sec <<< FAILURE!
> java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { }
> }>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> org.apache.jackrabbit.oak.plugins.segment.standby.DataStoreTestBase.useProxy(DataStoreTestBase.java:224)
> at
> org.apache.jackrabbit.oak.plugins.segment.standby.DataStoreTestBase.testProxyFlippedIntermediateByteChange2(DataStoreTestBase.java:189)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6206) ExternalPrivateStoreIT.testProxyFlippedIntermediateByteChange2 failing
[
https://issues.apache.org/jira/browse/OAK-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-6206:
Attachment: (was:
org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT-output.txt)
> ExternalPrivateStoreIT.testProxyFlippedIntermediateByteChange2 failing
> --
>
> Key: OAK-6206
> URL: https://issues.apache.org/jira/browse/OAK-6206
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: tarmk-standby
>Affects Versions: 1.4.15, 1.6.1
>Reporter: Julian Reschke
>
> This test currently fails for me frequently with:
> {noformat}
> testProxyFlippedIntermediateByteChange2(org.apache.jackrabbit.oak.plugins.segment.standby.ExternalPrivateStoreIT)
> Time elapsed: 0.794 sec <<< FAILURE!
> java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { }
> }>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> org.apache.jackrabbit.oak.plugins.segment.standby.DataStoreTestBase.useProxy(DataStoreTestBase.java:224)
> at
> org.apache.jackrabbit.oak.plugins.segment.standby.DataStoreTestBase.testProxyFlippedIntermediateByteChange2(DataStoreTestBase.java:189)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6829) ExternalPrivateStoreIT/ExternalSharedStoreIT.testSyncBigBlob failures
[
https://issues.apache.org/jira/browse/OAK-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-6829:
Attachment:
org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT-output.txt
org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT-output.txt
TEST-org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT.xml
TEST-org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT.xml
> ExternalPrivateStoreIT/ExternalSharedStoreIT.testSyncBigBlob failures
> -
>
> Key: OAK-6829
> URL: https://issues.apache.org/jira/browse/OAK-6829
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Affects Versions: 1.7.9
>Reporter: Julian Reschke
> Attachments:
> TEST-org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT.xml,
> TEST-org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT.xml,
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT-output.txt,
> org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT-output.txt
>
>
> {noformat}
> testSyncBigBlob(org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT)
> Time elapsed: 27.921 sec <<< FAILURE!
> java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { }
> }>
> Running org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT
> Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 93.353 sec
> <<< FAILURE! - in
> org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT
> testSyncBigBlob(org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT)
> Time elapsed: 30.772 sec <<< FAILURE!
> java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { }
> }>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6206) ExternalPrivateStoreIT.testProxyFlippedIntermediateByteChange2 failing
[
https://issues.apache.org/jira/browse/OAK-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-6206:
Attachment: (was:
TEST-org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT.xml)
> ExternalPrivateStoreIT.testProxyFlippedIntermediateByteChange2 failing
> --
>
> Key: OAK-6206
> URL: https://issues.apache.org/jira/browse/OAK-6206
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: tarmk-standby
>Affects Versions: 1.4.15, 1.6.1
>Reporter: Julian Reschke
>
> This test currently fails for me frequently with:
> {noformat}
> testProxyFlippedIntermediateByteChange2(org.apache.jackrabbit.oak.plugins.segment.standby.ExternalPrivateStoreIT)
> Time elapsed: 0.794 sec <<< FAILURE!
> java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { }
> }>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> org.apache.jackrabbit.oak.plugins.segment.standby.DataStoreTestBase.useProxy(DataStoreTestBase.java:224)
> at
> org.apache.jackrabbit.oak.plugins.segment.standby.DataStoreTestBase.testProxyFlippedIntermediateByteChange2(DataStoreTestBase.java:189)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6206) ExternalPrivateStoreIT.testProxyFlippedIntermediateByteChange2 failing
[
https://issues.apache.org/jira/browse/OAK-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-6206:
Attachment: (was:
TEST-org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT.xml)
> ExternalPrivateStoreIT.testProxyFlippedIntermediateByteChange2 failing
> --
>
> Key: OAK-6206
> URL: https://issues.apache.org/jira/browse/OAK-6206
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: tarmk-standby
>Affects Versions: 1.4.15, 1.6.1
>Reporter: Julian Reschke
>
> This test currently fails for me frequently with:
> {noformat}
> testProxyFlippedIntermediateByteChange2(org.apache.jackrabbit.oak.plugins.segment.standby.ExternalPrivateStoreIT)
> Time elapsed: 0.794 sec <<< FAILURE!
> java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { }
> }>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> org.apache.jackrabbit.oak.plugins.segment.standby.DataStoreTestBase.useProxy(DataStoreTestBase.java:224)
> at
> org.apache.jackrabbit.oak.plugins.segment.standby.DataStoreTestBase.testProxyFlippedIntermediateByteChange2(DataStoreTestBase.java:189)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6206) ExternalPrivateStoreIT.testProxyFlippedIntermediateByteChange2 failing
[
https://issues.apache.org/jira/browse/OAK-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-6206:
Attachment:
org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT-output.txt
org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT-output.txt
TEST-org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT.xml
TEST-org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT.xml
> ExternalPrivateStoreIT.testProxyFlippedIntermediateByteChange2 failing
> --
>
> Key: OAK-6206
> URL: https://issues.apache.org/jira/browse/OAK-6206
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: tarmk-standby
>Affects Versions: 1.4.15, 1.6.1
>Reporter: Julian Reschke
> Attachments:
> TEST-org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT.xml,
> TEST-org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT.xml,
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT-output.txt,
> org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT-output.txt
>
>
> This test currently fails for me frequently with:
> {noformat}
> testProxyFlippedIntermediateByteChange2(org.apache.jackrabbit.oak.plugins.segment.standby.ExternalPrivateStoreIT)
> Time elapsed: 0.794 sec <<< FAILURE!
> java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { }
> }>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> org.apache.jackrabbit.oak.plugins.segment.standby.DataStoreTestBase.useProxy(DataStoreTestBase.java:224)
> at
> org.apache.jackrabbit.oak.plugins.segment.standby.DataStoreTestBase.testProxyFlippedIntermediateByteChange2(DataStoreTestBase.java:189)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6829) ExternalPrivateStoreIT/ExternalSharedStoreIT.testSyncBigBlob failures
Julian Reschke created OAK-6829:
---
Summary:
ExternalPrivateStoreIT/ExternalSharedStoreIT.testSyncBigBlob failures
Key: OAK-6829
URL: https://issues.apache.org/jira/browse/OAK-6829
Project: Jackrabbit Oak
Issue Type: Bug
Components: segment-tar
Affects Versions: 1.7.9
Reporter: Julian Reschke
{noformat}
testSyncBigBlob(org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT)
Time elapsed: 27.921 sec <<< FAILURE!
java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { } }>
Running org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT
Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 93.353 sec <<<
FAILURE! - in org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT
testSyncBigBlob(org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT)
Time elapsed: 30.772 sec <<< FAILURE!
java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { } }>
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OAK-6825) oak-examples/standalone test failure on Java 9
[
https://issues.apache.org/jira/browse/OAK-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra resolved OAK-6825.
--
Resolution: Fixed
Fix Version/s: 1.7.10
1.8
Fixed via OAK-6113
> oak-examples/standalone test failure on Java 9
> --
>
> Key: OAK-6825
> URL: https://issues.apache.org/jira/browse/OAK-6825
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: examples
>Reporter: Julian Reschke
>Assignee: Chetan Mehrotra
> Fix For: 1.8, 1.7.10
>
>
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.985 sec <<<
> FAILURE! - in org.apache.jackrabbit.oak.standalone.RepositoryBootIT
> repositoryLogin(org.apache.jackrabbit.oak.standalone.RepositoryBootIT) Time
> elapsed: 0.008 sec <<< ERROR!
> java.lang.IllegalStateException: Failed to load ApplicationContext
> Caused by: org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name
> 'org.springframework.boot.autoconfigure.mongo.MongoAutoConfiguration':
> Injection of autowired dependencies failed; nested exception is
> org.springframework.beans.factory.BeanCreationException: Could not autowire
> field: private org.springframework.boot.autoconfigure.mongo.MongoProperties
> org.springframework.boot.autoconfigure.mongo.MongoAutoConfiguration.properties;
> nested exception is org.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'spring.data.mongodb.CONFIGURATION_PROPERTIES':
> Initialization of bean failed; nested exception is
> java.lang.NoClassDefFoundError: javax/xml/bind/ValidationException
> Caused by: org.springframework.beans.factory.BeanCreationException: Could not
> autowire field: private
> org.springframework.boot.autoconfigure.mongo.MongoProperties
> org.springframework.boot.autoconfigure.mongo.MongoAutoConfiguration.properties;
> nested exception is org.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'spring.data.mongodb.CONFIGURATION_PROPERTIES':
> Initialization of bean failed; nested exception is
> java.lang.NoClassDefFoundError: javax/xml/bind/ValidationException
> Caused by: org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'spring.data.mongodb.CONFIGURATION_PROPERTIES':
> Initialization of bean failed; nested exception is
> java.lang.NoClassDefFoundError: javax/xml/bind/ValidationException
> Caused by: java.lang.NoClassDefFoundError: javax/xml/bind/ValidationException
> Caused by: java.lang.ClassNotFoundException:
> javax.xml.bind.ValidationException
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6828) IndexDefinitionBuilder should provide a way to control ordering of indexRules
Chetan Mehrotra created OAK-6828: Summary: IndexDefinitionBuilder should provide a way to control ordering of indexRules Key: OAK-6828 URL: https://issues.apache.org/jira/browse/OAK-6828 Project: Jackrabbit Oak Issue Type: Technical task Components: lucene Reporter: Chetan Mehrotra Assignee: Chetan Mehrotra Priority: Minor Fix For: 1.8 Currently the indexRules are ordered in order of calls. For better control it should provide a way where caller can influence the ordering -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6746) Illegal reflective access by io.netty.util.internal.ReflectionUtil
[
https://issues.apache.org/jira/browse/OAK-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-6746:
Component/s: segment-tar
> Illegal reflective access by io.netty.util.internal.ReflectionUtil
> --
>
> Key: OAK-6746
> URL: https://issues.apache.org/jira/browse/OAK-6746
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Priority: Minor
>
> {noformat}
> Running org.apache.jackrabbit.oak.segment.standby.BrokenNetworkIT
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by io.netty.util.internal.ReflectionUtil
> (file:/C:/rust/Users/jre/.m2/repository/io/netty/netty-common/4.1.14.Final/netty-common-4.1.14.Final.jar)
> to constructor java.nio.DirectByteBuffer(long,int)
> WARNING: Please consider reporting this to the maintainers of
> io.netty.util.internal.ReflectionUtil
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6701) Update Oak 1.0 to Jackrabbit 2.8.6
[ https://issues.apache.org/jira/browse/OAK-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6701: Fix Version/s: (was: 1.7.9) 1.0.40 > Update Oak 1.0 to Jackrabbit 2.8.6 > -- > > Key: OAK-6701 > URL: https://issues.apache.org/jira/browse/OAK-6701 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.0.40 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6802) Manage 'secret' property internally in S3/AzureDataStore
[ https://issues.apache.org/jira/browse/OAK-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Jain resolved OAK-6802. Resolution: Fixed Fix Version/s: 1.7.10 Closing streams and re-reading the created content to ensure the object key actually assigned used S3 - http://svn.apache.org/viewvc?rev=1812109=rev Azure - http://svn.apache.org/viewvc?rev=18121010=rev > Manage 'secret' property internally in S3/AzureDataStore > > > Key: OAK-6802 > URL: https://issues.apache.org/jira/browse/OAK-6802 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: blob-cloud, blob-cloud-azure >Reporter: Amit Jain >Assignee: Amit Jain > Fix For: 1.8, 1.7.10 > > > Property 'secret' is required to be configured (which is a shared secret > among instances sharing the datastore) to enable binary-less replication. The > DataStore should manage it internally as it does for other things in the META > folder like in the container like repository ID etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6550) Make BlobTracker snapshot process smarter
[ https://issues.apache.org/jira/browse/OAK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Jain resolved OAK-6550. Resolution: Fixed Fix Version/s: 1.7.10 Done with http://svn.apache.org/viewvc?rev=1812108=rev > Make BlobTracker snapshot process smarter > - > > Key: OAK-6550 > URL: https://issues.apache.org/jira/browse/OAK-6550 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: blob-plugins >Reporter: Amit Jain >Assignee: Amit Jain > Fix For: 1.8, 1.7.10 > > > Currently, the BlobTracker snapshot() process is scheduled (every 12 hours by > default) which synchronizes the local additions & deletions since last change > with the datastore and consequently other cluster nodes. > The process should be slightly improved to run the sync on every removal i.e. > either through : > * Blob GC > * Active Deletion > And add some heuristic (most likely time based) to skip an upcoming sync > cycle if it makes sense. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6550) Make BlobTracker snapshot process smarter
[ https://issues.apache.org/jira/browse/OAK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203352#comment-16203352 ] Amit Jain commented on OAK-6550: The consistency check problem needs a little more work and is tracked with OAK-6827. > Make BlobTracker snapshot process smarter > - > > Key: OAK-6550 > URL: https://issues.apache.org/jira/browse/OAK-6550 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: blob-plugins >Reporter: Amit Jain >Assignee: Amit Jain > Fix For: 1.8 > > > Currently, the BlobTracker snapshot() process is scheduled (every 12 hours by > default) which synchronizes the local additions & deletions since last change > with the datastore and consequently other cluster nodes. > The process should be slightly improved to run the sync on every removal i.e. > either through : > * Blob GC > * Active Deletion > And add some heuristic (most likely time based) to skip an upcoming sync > cycle if it makes sense. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6827) Consistency check fails with active deletions
Amit Jain created OAK-6827: -- Summary: Consistency check fails with active deletions Key: OAK-6827 URL: https://issues.apache.org/jira/browse/OAK-6827 Project: Jackrabbit Oak Issue Type: Bug Components: blob-plugins, lucene Reporter: Amit Jain Assignee: Amit Jain Fix For: 1.8 With active deletions of lucene blobs the consistency check fails if the revision cleanup has not removed the older revisions or has not been run. The solution discussed was to track the active deletions and ignore if the missing blob ids being reported by the consistency check are present in the tracked deletions. Also, this active deletions would have to updated during DataStore GC to remove from active deletions the ids not included in the mark references phase because they have finally been collected. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6550) Make BlobTracker snapshot process smarter
[ https://issues.apache.org/jira/browse/OAK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Jain updated OAK-6550: --- Summary: Make BlobTracker snapshot process smarter (was: Make BlobTracker snaphot process smarter) > Make BlobTracker snapshot process smarter > - > > Key: OAK-6550 > URL: https://issues.apache.org/jira/browse/OAK-6550 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: blob-plugins >Reporter: Amit Jain >Assignee: Amit Jain > Fix For: 1.8 > > > Currently, the BlobTracker snapshot() process is scheduled (every 12 hours by > default) which synchronizes the local additions & deletions since last change > with the datastore and consequently other cluster nodes. > The process should be slightly improved to run the sync on every removal i.e. > either through : > * Blob GC > * Active Deletion > And add some heuristic (most likely time based) to skip an upcoming sync > cycle if it makes sense. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6113) update spring to 1.5.x release
[ https://issues.apache.org/jira/browse/OAK-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra resolved OAK-6113. -- Resolution: Fixed Fix Version/s: 1.7.10 > update spring to 1.5.x release > -- > > Key: OAK-6113 > URL: https://issues.apache.org/jira/browse/OAK-6113 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: examples >Reporter: Julian Reschke >Assignee: Chetan Mehrotra >Priority: Minor > Fix For: 1.8, 1.7.10 > > > To 1.5.2.RELEASE or newer... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6113) update spring to 1.5.x release
[ https://issues.apache.org/jira/browse/OAK-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated OAK-6113: - Summary: update spring to 1.5.x release (was: update spring-boot-maven-plugin) > update spring to 1.5.x release > -- > > Key: OAK-6113 > URL: https://issues.apache.org/jira/browse/OAK-6113 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: examples >Reporter: Julian Reschke >Priority: Minor > Fix For: 1.8 > > > To 1.5.2.RELEASE or newer... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6825) oak-examples/standalone test failure on Java 9
[
https://issues.apache.org/jira/browse/OAK-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203275#comment-16203275
]
Chetan Mehrotra commented on OAK-6825:
--
[~julian.resc...@gmx.de] I have updated Spring dependency to latest (OAK-6113)
and now build passes on Java 9 also. Can you confirm it at your end
> oak-examples/standalone test failure on Java 9
> --
>
> Key: OAK-6825
> URL: https://issues.apache.org/jira/browse/OAK-6825
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: examples
>Reporter: Julian Reschke
>Assignee: Chetan Mehrotra
>
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.985 sec <<<
> FAILURE! - in org.apache.jackrabbit.oak.standalone.RepositoryBootIT
> repositoryLogin(org.apache.jackrabbit.oak.standalone.RepositoryBootIT) Time
> elapsed: 0.008 sec <<< ERROR!
> java.lang.IllegalStateException: Failed to load ApplicationContext
> Caused by: org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name
> 'org.springframework.boot.autoconfigure.mongo.MongoAutoConfiguration':
> Injection of autowired dependencies failed; nested exception is
> org.springframework.beans.factory.BeanCreationException: Could not autowire
> field: private org.springframework.boot.autoconfigure.mongo.MongoProperties
> org.springframework.boot.autoconfigure.mongo.MongoAutoConfiguration.properties;
> nested exception is org.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'spring.data.mongodb.CONFIGURATION_PROPERTIES':
> Initialization of bean failed; nested exception is
> java.lang.NoClassDefFoundError: javax/xml/bind/ValidationException
> Caused by: org.springframework.beans.factory.BeanCreationException: Could not
> autowire field: private
> org.springframework.boot.autoconfigure.mongo.MongoProperties
> org.springframework.boot.autoconfigure.mongo.MongoAutoConfiguration.properties;
> nested exception is org.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'spring.data.mongodb.CONFIGURATION_PROPERTIES':
> Initialization of bean failed; nested exception is
> java.lang.NoClassDefFoundError: javax/xml/bind/ValidationException
> Caused by: org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'spring.data.mongodb.CONFIGURATION_PROPERTIES':
> Initialization of bean failed; nested exception is
> java.lang.NoClassDefFoundError: javax/xml/bind/ValidationException
> Caused by: java.lang.NoClassDefFoundError: javax/xml/bind/ValidationException
> Caused by: java.lang.ClassNotFoundException:
> javax.xml.bind.ValidationException
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6113) update spring to 1.5.x release
[ https://issues.apache.org/jira/browse/OAK-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203274#comment-16203274 ] Chetan Mehrotra commented on OAK-6113: -- Done with 1812086. Had to restrict failsafe plugin too 1.18.1 due to [1] and [2]. Classpath workaround somehow not worked. For now with 1.18.1 it works fine even on Java 9 [1] https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-1.4-Release-Notes#integration-tests-with-the-maven-failsafe-plugin [2] https://github.com/spring-projects/spring-boot/issues/6254#issuecomment-281404852 > update spring to 1.5.x release > -- > > Key: OAK-6113 > URL: https://issues.apache.org/jira/browse/OAK-6113 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: examples >Reporter: Julian Reschke >Assignee: Chetan Mehrotra >Priority: Minor > Fix For: 1.8, 1.7.10 > > > To 1.5.2.RELEASE or newer... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OAK-6113) update spring to 1.5.x release
[ https://issues.apache.org/jira/browse/OAK-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra reassigned OAK-6113: Assignee: Chetan Mehrotra > update spring to 1.5.x release > -- > > Key: OAK-6113 > URL: https://issues.apache.org/jira/browse/OAK-6113 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: examples >Reporter: Julian Reschke >Assignee: Chetan Mehrotra >Priority: Minor > Fix For: 1.8 > > > To 1.5.2.RELEASE or newer... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6783) Slow queries JMX bean: sort by rows, not time
[ https://issues.apache.org/jira/browse/OAK-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6783. - Bulk close for 1.7.9 > Slow queries JMX bean: sort by rows, not time > - > > Key: OAK-6783 > URL: https://issues.apache.org/jira/browse/OAK-6783 > Project: Jackrabbit Oak > Issue Type: Bug > Components: query >Reporter: Thomas Mueller >Assignee: Thomas Mueller >Priority: Minor > Fix For: 1.8, 1.7.9 > > > The QueryStats mean added in OAK-6526 sorts by time. Timing data is > unreliable, specially after startup. It's better to sort by row count. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6743) Copy RootFactory, TreeFactory to separate package (and deprecate existing)
[
https://issues.apache.org/jira/browse/OAK-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6743.
-
Bulk close for 1.7.9
> Copy RootFactory, TreeFactory to separate package (and deprecate existing)
> --
>
> Key: OAK-6743
> URL: https://issues.apache.org/jira/browse/OAK-6743
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core
>Reporter: angela
> Fix For: 1.7.9
>
>
> [~stillalex], in a next step I suggest that we copy {{RootFactory}} and
> {{TreeFactory}} to a separate subpackage, mark existing classes deprecated
> and replace all usages within oak code base.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6724) Create empty module structure and dependencies from/to other oak modules
[ https://issues.apache.org/jira/browse/OAK-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6724. - Bulk close for 1.7.9 > Create empty module structure and dependencies from/to other oak modules > > > Key: OAK-6724 > URL: https://issues.apache.org/jira/browse/OAK-6724 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core >Reporter: angela >Assignee: angela > Fix For: 1.7.9 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6742) Upgrade to jline2 2.14.5
[ https://issues.apache.org/jira/browse/OAK-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6742. - Bulk close for 1.7.9 > Upgrade to jline2 2.14.5 > > > Key: OAK-6742 > URL: https://issues.apache.org/jira/browse/OAK-6742 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: run >Reporter: Robert Munteanu >Assignee: Robert Munteanu > Fix For: 1.8, 1.7.9 > > > 2.14.4 brings a fix for newer ncurses versions. We should update to the > latest version available though. > https://github.com/jline/jline2/issues/281 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6738) MemoryDocumentStore should optionally maintain _modCount
[ https://issues.apache.org/jira/browse/OAK-6738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6738. - Bulk close for 1.7.9 > MemoryDocumentStore should optionally maintain _modCount > > > Key: OAK-6738 > URL: https://issues.apache.org/jira/browse/OAK-6738 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 1.8, 1.7.9 > > > The MemoryDocumentStore should optionally maintain the _modCount field on > documents. With this option enabled, the store is closer to the behaviour of > the other two DocumentStore implementations for MongoDB and RDB. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6237) Tomcat JDBC pool's StatementCache interceptor may cache borked PreparedStatements with DB2
[
https://issues.apache.org/jira/browse/OAK-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6237.
-
Bulk close for 1.7.9
> Tomcat JDBC pool's StatementCache interceptor may cache borked
> PreparedStatements with DB2
> --
>
> Key: OAK-6237
> URL: https://issues.apache.org/jira/browse/OAK-6237
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 1.8, 1.2.28, 1.7.9, 1.0.40, 1.4.19, 1.6.6
>
> Attachments: OAK-6237.diff
>
>
> {noformat}
> (cd oak-store-document; mvn clean install -Prdb-db2 -Dtest=RDBBlobStoreTest)
> {noformat}
> fails with:
> {noformat}
> [ERROR] testDeleteChunks[MyFixture:
> RDB-DB2](org.apache.jackrabbit.oak.plugins.document.blob.RDBBlobStoreTest)
> Time elapsed: 0.069 s <<< ERROR!
> com.ibm.db2.jcc.am.SqlSyntaxErrorException: [jcc][10145][10844][4.16.53]
> Invalid parameter 1: Parameter index is out of range. ERRORCODE=-4461,
> SQLSTATE=42815
> at
> org.apache.jackrabbit.oak.plugins.document.blob.RDBBlobStoreTest.testDeleteChunks(RDBBlobStoreTest.java:219)
> {noformat}
> Stack trace:
> {noformat}
> com.ibm.db2.jcc.am.SqlSyntaxErrorException: [jcc][10145][10844][4.16.53]
> Invalid parameter 1: Parameter index is out of range. ERRORCODE=-4461,
> SQLSTATE=42815
> at com.ibm.db2.jcc.am.fd.a(fd.java:739)
> at com.ibm.db2.jcc.am.fd.a(fd.java:60)
> at com.ibm.db2.jcc.am.fd.a(fd.java:103)
> at com.ibm.db2.jcc.am.uo.l(uo.java:5982)
> at com.ibm.db2.jcc.am.uo.j(uo.java:5937)
> at com.ibm.db2.jcc.am.uo.a(uo.java:1606)
> at com.ibm.db2.jcc.am.uo.setString(uo.java:1595)
> at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.tomcat.jdbc.pool.interceptor.StatementDecoratorInterceptor$StatementProxy.invoke(StatementDecoratorInterceptor.java:261)
> at com.sun.proxy.$Proxy12.setString(Unknown Source)
> at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.tomcat.jdbc.pool.interceptor.AbstractQueryReport$StatementProxy.invoke(AbstractQueryReport.java:235)
> at com.sun.proxy.$Proxy12.setString(Unknown Source)
> at
> org.apache.jackrabbit.oak.plugins.document.rdb.RDBPreparedStatementWrapper.setString(RDBPreparedStatementWrapper.java:552)
> at
> org.apache.jackrabbit.oak.plugins.document.rdb.RDBBlobStoreFriend.isDataEntryPresent(RDBBlobStoreFriend.java:62)
> at
> org.apache.jackrabbit.oak.plugins.document.blob.RDBBlobStoreTest.testDeleteChunks(RDBBlobStoreTest.java:219)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at
[jira] [Closed] (OAK-6633) Overwriting a versionable node with the copy-versions=false doesn't remove versionable properties
[
https://issues.apache.org/jira/browse/OAK-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6633.
-
Bulk close for 1.7.9
> Overwriting a versionable node with the copy-versions=false doesn't remove
> versionable properties
> -
>
> Key: OAK-6633
> URL: https://issues.apache.org/jira/browse/OAK-6633
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: upgrade
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
>Priority: Minor
> Fix For: 1.8, 1.7.9
>
>
> Steps to reproduce:
> 1. Migrate a versionable node, including its version history
> ({{\-\-copy-versions=true}})
> 2. Migrate it again, excluding its version history
> ({{\-\-copy-versions=false}}
> Result:
> * the node is still versionable after the 2nd migration
> * the version history is not removed
> Expected:
> * the node shouldn't be versionable after the 2nd migration
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6744) OAK Solr Core on JDK 9: Could not find artifact jdk.tools:jdk.tools:jar:1.6
[
https://issues.apache.org/jira/browse/OAK-6744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6744.
-
Bulk close for 1.7.9
> OAK Solr Core on JDK 9: Could not find artifact jdk.tools:jdk.tools:jar:1.6
> ---
>
> Key: OAK-6744
> URL: https://issues.apache.org/jira/browse/OAK-6744
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: solr
>Affects Versions: 1.7.8
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Labels: candidate_oak_1_6
> Fix For: 1.8, 1.7.9
>
> Attachments: OAK-6744.diff
>
>
> {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: Could not find
> artifact jdk.tools:jdk.tools:jar:1.6 at specified path C:\Program
> Files\Java\jdk-9/../lib/tools.jar -> [Help 1]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6781) Reindex handling with synchronous lucene property indexes
[
https://issues.apache.org/jira/browse/OAK-6781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6781.
-
Bulk close for 1.7.9
> Reindex handling with synchronous lucene property indexes
> -
>
> Key: OAK-6781
> URL: https://issues.apache.org/jira/browse/OAK-6781
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: lucene
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
> Fix For: 1.8, 1.7.9
>
> Attachments: OAK-6781-v1.patch
>
>
> Reindex logic needs to be changes to account for presence of synchronous
> lucene property indexes. Currently reindexer would remove all hidden nodes
> which would also include the {{:property-index}} node and that can lead to
> conflict with async indexer where this nodes gets modified during async
> indexer run
> To support that we should provide a way where in reindexing some nodes are
> not removed
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6799) OSGi service tests for Blob GC
[ https://issues.apache.org/jira/browse/OAK-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6799. - Bulk close for 1.7.9 > OSGi service tests for Blob GC > -- > > Key: OAK-6799 > URL: https://issues.apache.org/jira/browse/OAK-6799 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: blob >Reporter: Amit Jain >Assignee: Amit Jain > Fix For: 1.8, 1.7.9 > > > OSGi initialization tests for Blob GC. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6665) Move DocumentNodeStore into its own bundle
[ https://issues.apache.org/jira/browse/OAK-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6665. - Bulk close for 1.7.9 > Move DocumentNodeStore into its own bundle > -- > > Key: OAK-6665 > URL: https://issues.apache.org/jira/browse/OAK-6665 > Project: Jackrabbit Oak > Issue Type: Task > Components: core, documentmk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger > Labels: modularization, technical_debt > Fix For: 1.8, 1.7.9 > > Attachments: oak-store-document.png > > > Move the DocumentNodeStore implementation and the two backends (MongoDB, RDB) > into its own bundle. This will make it possible to release oak-core and the > NodeStore implementation independently. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6483) Segment-based composite node store performance degradation
[
https://issues.apache.org/jira/browse/OAK-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6483.
-
Bulk close for 1.7.9
> Segment-based composite node store performance degradation
> --
>
> Key: OAK-6483
> URL: https://issues.apache.org/jira/browse/OAK-6483
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: composite
>Affects Versions: 1.7.4
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
>Priority: Critical
> Fix For: 1.8, 1.7.9
>
>
> It seems that the OAK-4732 is not compatible with the composite node store
> using a segment node store as the main (writeable) store. The OAK-4732
> measures how much does it usually take to apply commit hooks and merge the
> new root. However, the composite node store plugs into the commit hook and
> reads other node store states. As a result, it may take quite a while and the
> measured values are big. They are then used to tune the lock inside the
> LockBasedScheduler#getHeadNodeState() method. Since the times are big, the
> method also waits a long time for the semaphore before it gives up. This
> causes performance degradation.
> The {{-Doak.scheduler.fetch.commitDelayQuantile=0}} parameter can be used to
> disable the OAK-4732.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6798) Basic Blob GC test for in-memory NodeStore and BlobStore
[ https://issues.apache.org/jira/browse/OAK-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6798. - Bulk close for 1.7.9 > Basic Blob GC test for in-memory NodeStore and BlobStore > - > > Key: OAK-6798 > URL: https://issues.apache.org/jira/browse/OAK-6798 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: blob-plugins >Reporter: Amit Jain >Assignee: Amit Jain > Fix For: 1.8, 1.7.9 > > > Create a basic tests for BlobGC which can test the basic functionality using > an in-memory Node and Blob Store. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6732) Make it simpler to run tests from oak-it-osgi
[
https://issues.apache.org/jira/browse/OAK-6732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6732.
-
Bulk close for 1.7.9
> Make it simpler to run tests from oak-it-osgi
> -
>
> Key: OAK-6732
> URL: https://issues.apache.org/jira/browse/OAK-6732
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: it
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Minor
> Fix For: 1.8, 1.7.9
>
>
> It's not immediately obvious how to make sure changes to other modules are
> picked up when running tests from {{oak-it-osgi}}. We should document the
> process and possibly simplify it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6800) Minor typo in message returned by consistency check through mbean
[ https://issues.apache.org/jira/browse/OAK-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6800. - Bulk close for 1.7.9 > Minor typo in message returned by consistency check through mbean > - > > Key: OAK-6800 > URL: https://issues.apache.org/jira/browse/OAK-6800 > Project: Jackrabbit Oak > Issue Type: Bug > Components: blob-plugins >Reporter: Amit Jain >Assignee: Amit Jain >Priority: Minor > Fix For: 1.8, 1.7.9 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6779) IndexTracker should check diff on :status node to detect index updates
[ https://issues.apache.org/jira/browse/OAK-6779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6779. - Bulk close for 1.7.9 > IndexTracker should check diff on :status node to detect index updates > -- > > Key: OAK-6779 > URL: https://issues.apache.org/jira/browse/OAK-6779 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.8, 1.7.9 > > Attachments: OAK-6779-v1.patch > > > Currently IndexTracker while checking for index state updates does a diff > till indexPath. For e.g. if index is /oak:index/fooIndex then it would create > a SubtreeEditor for path /oak:index/fooIndex and refreshes the index if any > change is found under that path. > With synchronous lucene property indexes now other changes would occur under > /oak:index/fooIndex/:property-index which causes the tracker to refresh the > index even if no change has occurred in main index. This is mitigated to some > extent with OAK-6713 and its use in IndexTracker but not complete. > For proper fix the diff should check for changes in :status node -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-5788) Perform update of single node in one remote call if possible
[ https://issues.apache.org/jira/browse/OAK-5788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-5788. - Bulk close for 1.7.9 > Perform update of single node in one remote call if possible > > > Key: OAK-5788 > URL: https://issues.apache.org/jira/browse/OAK-5788 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Chetan Mehrotra >Assignee: Marcel Reutegger > Labels: performance > Fix For: 1.8, 1.7.9 > > Attachments: OAK-5788.patch > > > If a single node is modified in a commit then currently it performs 2 remote > calls > # The actual update > # Update of commit root > as for single node update commitRoot == node being updated we can optimize > this case to see if both operations can be done in same call -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6579) Define how the counter index works in a composite setup
[ https://issues.apache.org/jira/browse/OAK-6579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6579. - Bulk close for 1.7.9 > Define how the counter index works in a composite setup > --- > > Key: OAK-6579 > URL: https://issues.apache.org/jira/browse/OAK-6579 > Project: Jackrabbit Oak > Issue Type: Task > Components: composite, indexing >Reporter: Robert Munteanu >Assignee: Tomek Rękawek > Fix For: 1.8, 1.7.9 > > Attachments: OAK-6579-2.patch, OAK-6579-3.patch, OAK-6579.patch > > > We need to see if this index can or should be adjusted to work in a composite > environment. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6730) oak-core/src/main/java/org/apache/jackrabbit/oak/spi/security/CompositeConfiguration.java does not compile with jdk 9
[
https://issues.apache.org/jira/browse/OAK-6730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6730.
-
Bulk close for 1.7.9
> oak-core/src/main/java/org/apache/jackrabbit/oak/spi/security/CompositeConfiguration.java
> does not compile with jdk 9
> -
>
> Key: OAK-6730
> URL: https://issues.apache.org/jira/browse/OAK-6730
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
>Affects Versions: 1.7.8
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Labels: candidate_oak_1_6
> Fix For: 1.8, 1.7.9
>
> Attachments: OAK-6730.diff
>
>
> {noformat}
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /C:/projects/apache/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/spi/security/CompositeConfiguration.java:[199,36]
> incompatible types: inference variable T has incompatible bounds
> upper bounds: java.lang.Iterable org.apache.jackrabbit.oak.spi.commit.CommitHook>,java.lang.Object
> lower bounds: java.util.List org.apache.jackrabbit.oak.spi.commit.CommitHook>
> [ERROR]
> /C:/projects/apache/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/spi/security/CompositeConfiguration.java:[210,36]
> incompatible types: inference variable T has incompatible bounds
> upper bounds: java.lang.Iterable org.apache.jackrabbit.oak.spi.commit.ValidatorProvider>,java.lang.Object
> lower bounds: java.util.List org.apache.jackrabbit.oak.spi.commit.ValidatorProvider>
> [ERROR]
> /C:/projects/apache/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/spi/security/CompositeConfiguration.java:[227,36]
> incompatible types: inference variable T has incompatible bounds
> upper bounds: java.lang.Iterable org.apache.jackrabbit.oak.spi.xml.ProtectedItemImporter>,java.lang.Object
> lower bounds: java.util.List org.apache.jackrabbit.oak.spi.xml.ProtectedItemImporter>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6752) Conditional update on _modCount
[ https://issues.apache.org/jira/browse/OAK-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6752. - Bulk close for 1.7.9 > Conditional update on _modCount > --- > > Key: OAK-6752 > URL: https://issues.apache.org/jira/browse/OAK-6752 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 1.8, 1.7.9 > > > Support conditional update on the _modCount field if the DocumentStore > implementation maintains it. The MongoDocumentStore and RDBDocumentStore > implementation maintain the field, while the MemoryDocumentStore (for tests > only) maintains it optionally (see OAK-6738). This issue is about adding > tests and verifying correct behaviour of the available DocumentStore > implementations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6701) Update Oak 1.0 to Jackrabbit 2.8.6
[ https://issues.apache.org/jira/browse/OAK-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6701. - Bulk close for 1.7.9 > Update Oak 1.0 to Jackrabbit 2.8.6 > -- > > Key: OAK-6701 > URL: https://issues.apache.org/jira/browse/OAK-6701 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.7.9 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6719) add ability to run benchmarks with continuous version GC enabled (RDB fixtures)
[ https://issues.apache.org/jira/browse/OAK-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6719. - Bulk close for 1.7.9 > add ability to run benchmarks with continuous version GC enabled (RDB > fixtures) > --- > > Key: OAK-6719 > URL: https://issues.apache.org/jira/browse/OAK-6719 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: benchmarks >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.8, 1.7.9 > > > Seems that this would require stealing some code from > DocumentNodeStoreService, right? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6782) RDBDocumentStore: inconsistent handling of cache invalidation on remove()
[
https://issues.apache.org/jira/browse/OAK-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6782.
-
Bulk close for 1.7.9
> RDBDocumentStore: inconsistent handling of cache invalidation on remove()
> -
>
> Key: OAK-6782
> URL: https://issues.apache.org/jira/browse/OAK-6782
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: documentmk, rdbmk
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.8, 1.2.28, 1.7.9, 1.0.40, 1.4.19, 1.6.6
>
>
> {{remove(Collection collection, Map>
> toRemove)}} invalidates the cache after talking to the DB. The other variants
> do it before.
> [~mreutegg] - this was added for OAK-2804 - do you recall whether there was a
> specific reason to do it like that?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6725) Move o.a.j.oak.plugins.tree.impl.ChildOrderDiff to o.a.j.oak.security.authorization.permission
[
https://issues.apache.org/jira/browse/OAK-6725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6725.
-
Bulk close for 1.7.9
> Move o.a.j.oak.plugins.tree.impl.ChildOrderDiff to
> o.a.j.oak.security.authorization.permission
> --
>
> Key: OAK-6725
> URL: https://issues.apache.org/jira/browse/OAK-6725
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core
>Reporter: angela
>Assignee: angela
> Fix For: 1.7.9
>
>
> {{o.a.j.oak.plugins.tree.impl.ChildOrderDiff}} is only used in a single class
> within the permission implementation. I will move it there.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6714) Support non root index in ContentMirrorStoreStrategy
[ https://issues.apache.org/jira/browse/OAK-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6714. - Bulk close for 1.7.9 > Support non root index in ContentMirrorStoreStrategy > > > Key: OAK-6714 > URL: https://issues.apache.org/jira/browse/OAK-6714 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: property-index >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Minor > Fix For: 1.8, 1.7.9 > > Attachments: OAK-6714-v1.patch > > > So far property indexes have been only supported for root indexes i.e. index > defined under /oak:index. With OAK-6535 its possible to enable sync support > for non root indexes. > From impl > [ContentMirrorStoreStrategy|https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/property/strategy/ContentMirrorStoreStrategy.java#L151] > supports specifying a pathPrefix. However there is no way to set this from > outside. > We should provide a way to set this and see if non root indexes can be > supported -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6726) Use addDocument instead of updateDocument while reindexing with Lucene
[ https://issues.apache.org/jira/browse/OAK-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6726. - Bulk close for 1.7.9 > Use addDocument instead of updateDocument while reindexing with Lucene > -- > > Key: OAK-6726 > URL: https://issues.apache.org/jira/browse/OAK-6726 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Minor > Fix For: 1.8, 1.7.9 > > > Currently the DefaultIndexWriter uses > [updateDocument|https://lucene.apache.org/core/4_7_1/core/org/apache/lucene/index/IndexWriter.html#updateDocument(org.apache.lucene.index.Term, > java.lang.Iterable)] while adding/updating document in index. This is fine > for incremental indexing where we cannot be sure if index already has that > entry. This call first does a search for existing document matching the term > and then deletes and add the new document > However for reindex case where we start from empty index we can use > [addDocument|https://lucene.apache.org/core/4_7_1/core/org/apache/lucene/index/IndexWriter.html#addDocument(java.lang.Iterable)]. > This avoids the extra work for search > In test where index had ~70M entries switch to addDocument resulted in 10 min > reduction in reindexing timings -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6755) Convert oak-core and oak-store-document to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6755. - Bulk close for 1.7.9 > Convert oak-core and oak-store-document to OSGi R6 annotations > -- > > Key: OAK-6755 > URL: https://issues.apache.org/jira/browse/OAK-6755 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core, documentmk >Reporter: Robert Munteanu >Assignee: Julian Sedding > Fix For: 1.8, 1.7.9 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6734) IndexPlan: add supportsPathRestrictions
[ https://issues.apache.org/jira/browse/OAK-6734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6734. - Bulk close for 1.7.9 > IndexPlan: add supportsPathRestrictions > --- > > Key: OAK-6734 > URL: https://issues.apache.org/jira/browse/OAK-6734 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Thomas Mueller >Assignee: Vikas Saurabh > Fix For: 1.8, 1.7.9 > > > Some indexes support path restrictions (for example Lucene indexes, if > configured to do so). For such cases, the cost of using the index is at most > the cost of traversing. > There are two ways to solve this: (1) the index itself could (somehow) ask > the counter index about the estimated number of nodes for that path. (2) the > query engine can do that itself, so that the index doesn't need to implement > this logic. > Let's do approach (2), and add a method supportsPathRestrictions to the > IndexPlan interface. If it returns false (default), the behavior is the same > as right now. If it returns true, then the cost of the index is adjusted to > the estimated number of nodes in this path. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6777) IndexReader closed exception in previous reader
[
https://issues.apache.org/jira/browse/OAK-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6777.
-
Bulk close for 1.7.9
> IndexReader closed exception in previous reader
> ---
>
> Key: OAK-6777
> URL: https://issues.apache.org/jira/browse/OAK-6777
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
>Affects Versions: 1.6.5
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
> Labels: candidate_oak_1_6
> Fix For: 1.8, 1.7.9
>
> Attachments: OAK-6777-v1.patch
>
>
> Another variant of index reader closed exception as reported in OAK-6635 is
> seen for previous readers
> {noformat}
> 2017-10-03 21:21:41,810 ERROR NA [oak-lucene-16]
> o.a.j.o.p.i.l.h.DocumentQueue - Uncaught exception
> org.apache.lucene.store.AlreadyClosedException: this IndexReader is closed
> at org.apache.lucene.index.IndexReader.ensureOpen(IndexReader.java:262)
> at
> org.apache.lucene.index.StandardDirectoryReader.doOpenIfChanged(StandardDirectoryReader.java:271)
> at
> org.apache.lucene.index.DirectoryReader.openIfChanged(DirectoryReader.java:250)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.hybrid.NRTIndex.createReader(NRTIndex.java:257)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.hybrid.NRTIndex.getPrimaryReader(NRTIndex.java:113)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.hybrid.NRTIndex.getReaders(NRTIndex.java:148)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.IndexNodeManager.getNRTReaders(IndexNodeManager.java:243)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.IndexNodeManager.refreshReaders(IndexNodeManager.java:203)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.IndexNodeManager.access$100(IndexNodeManager.java:53)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.IndexNodeManager$1.run(IndexNodeManager.java:104)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.hybrid.TimedRefreshPolicy.refreshIfRequired(TimedRefreshPolicy.java:59)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.hybrid.TimedRefreshPolicy.refreshOnReadIfRequired(TimedRefreshPolicy.java:40)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.IndexNodeManager.acquire(IndexNodeManager.java:152)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.IndexTracker.acquireIndexNode(IndexTracker.java:193)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.hybrid.DocumentQueue.processDocs(DocumentQueue.java:235)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.hybrid.DocumentQueue.addDocsToIndex(DocumentQueue.java:214)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.hybrid.DocumentQueue.access$500(DocumentQueue.java:55)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.hybrid.DocumentQueue$2$1.call(DocumentQueue.java:121)
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.hybrid.DocumentQueue$2$1.call(DocumentQueue.java:96)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6680) Test failure: DocumentNodeStoreTest.disabledBranchesWithBackgroundWrite
[
https://issues.apache.org/jira/browse/OAK-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6680.
-
Bulk close for 1.7.9
> Test failure: DocumentNodeStoreTest.disabledBranchesWithBackgroundWrite
> ---
>
> Key: OAK-6680
> URL: https://issues.apache.org/jira/browse/OAK-6680
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: documentmk
>Affects Versions: 1.7.3
>Reporter: Francesco Mari
>Assignee: Marcel Reutegger
> Labels: test-failure
> Fix For: 1.8, 1.7.9
>
>
> {{DocumentNodeStoreTest.disabledBranchesWithBackgroundWrite}} fails when I
> try a clean build on Windows, as per r1808698.
> {noformat}
> [ERROR] Failures:
> [ERROR] DocumentNodeStoreTest.disabledBranchesWithBackgroundWrite:3199
> expected:<1> but was:<0>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6666) Clean up tests depending on DocumentNodeStore
[
https://issues.apache.org/jira/browse/OAK-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-.
-
Bulk close for 1.7.9
> Clean up tests depending on DocumentNodeStore
> -
>
> Key: OAK-
> URL: https://issues.apache.org/jira/browse/OAK-
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Minor
> Fix For: 1.8, 1.7.9
>
>
> There are various tests outside the {{plugins.document}} package using a
> {{DocumentNodeStore}}. These need to be cleaned up before the implementation
> can be moved to its own bundle.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6623) Document QueryEngineSettings.FastQuerySize / QueryEngineSettingsService
[ https://issues.apache.org/jira/browse/OAK-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6623. - Bulk close for 1.7.9 > Document QueryEngineSettings.FastQuerySize / QueryEngineSettingsService > --- > > Key: OAK-6623 > URL: https://issues.apache.org/jira/browse/OAK-6623 > Project: Jackrabbit Oak > Issue Type: Documentation > Components: query >Reporter: Thomas Mueller >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.9 > > > This setting is currently not well documented. > Documentation is in the code (in the JMX bean / configuration). > Also, there is documentation at > http://jackrabbit.apache.org/oak/docs/query/query-engine.html#Result_Size -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6722) Incorrect and unused dependencies in oak-query-spi
[
https://issues.apache.org/jira/browse/OAK-6722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6722.
-
Bulk close for 1.7.9
> Incorrect and unused dependencies in oak-query-spi
> --
>
> Key: OAK-6722
> URL: https://issues.apache.org/jira/browse/OAK-6722
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
>Affects Versions: 1.7.6
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Minor
> Fix For: 1.8, 1.7.9
>
>
> The scope of the logback-classic dependency in {{oak-query-spi}} is not set
> and therefore defaults to {{compile}}. This incorrect and should be set to
> {{test}} scope.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6713) AsyncIndexInfoService - Method to detect change in indexer state
[ https://issues.apache.org/jira/browse/OAK-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6713. - Bulk close for 1.7.9 > AsyncIndexInfoService - Method to detect change in indexer state > > > Key: OAK-6713 > URL: https://issues.apache.org/jira/browse/OAK-6713 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: indexing >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.8, 1.7.9 > > > AsyncIndexInfoService should provide a method to determine if async indexer > has completed any new indexing cycle (i.e. lastIndexedTo state changed) > between 2 repository states. > This can be used by indexers to determine if they should check further for > actual change in index -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6739) Improve oak-it-osgi to support SCR spec 1.3
[ https://issues.apache.org/jira/browse/OAK-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6739. - Bulk close for 1.7.9 > Improve oak-it-osgi to support SCR spec 1.3 > --- > > Key: OAK-6739 > URL: https://issues.apache.org/jira/browse/OAK-6739 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: it >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Minor > Fix For: 1.8, 1.7.9 > > > Similar to OAK-6736, we need to support SCR 1.3 in oak-it-osgi. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6750) Lucene facets don't work with relative properties
[
https://issues.apache.org/jira/browse/OAK-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6750.
-
Bulk close for 1.7.9
> Lucene facets don't work with relative properties
> -
>
> Key: OAK-6750
> URL: https://issues.apache.org/jira/browse/OAK-6750
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Labels: candidate_oak_1_4, candidate_oak_1_6
> Fix For: 1.8, 1.7.9
>
> Attachments: OAK-6750-testCase.patch
>
>
> Facets currently work only when faceted dimension is direct property of
> selected node e.g.
> {noformat}
> select \[jcr:path], \[rep:facet(jc/text)] from \[nt:base] where ...
> {noformat}
> doesn't work but
> {noformat}
> select \[jcr:path], \[rep:facet(text)] from \[nt:base] where ...
> {noformat}
> works (assume correct index defs).
> The issue is that {{ast/SelectorImpl#currentOakProperty}} check if
> {{rep:facet(jc/text)}} is a relative path or not and incorrectly 'feels' that
> it indeed is - it then proceeds ahead to traverse down a tree with elements
> \[{{rep:facet(jc}}, {{text)}}\] which makes no sense.
> /cc [~teofili], [~tmueller]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6778) XPath union with "explain" doesn't explain
[
https://issues.apache.org/jira/browse/OAK-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6778.
-
Bulk close for 1.7.9
> XPath union with "explain" doesn't explain
> --
>
> Key: OAK-6778
> URL: https://issues.apache.org/jira/browse/OAK-6778
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
> Fix For: 1.8, 1.7.9
>
>
> Combining "explain" / "explain measure" with an XPath union doesn't work as
> expected: it executes the statement instead of explaining / measuring it.
> Example:
> {noformat}
> explain /jcr:root/content/(activities|people)//element(*, acme:Asset)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6699) Move PathFilter to oak-store-spi
[
https://issues.apache.org/jira/browse/OAK-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6699.
-
Bulk close for 1.7.9
> Move PathFilter to oak-store-spi
>
>
> Key: OAK-6699
> URL: https://issues.apache.org/jira/browse/OAK-6699
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, store-spi
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Minor
> Fix For: 1.8, 1.7.9
>
>
> The class {{org.apache.jackrabbit.oak.plugins.index.PathFilter}} in oak-core
> is used by the index implementation, the DocumentNodeStore and oak-lucene.
> In order to reduce the dependencies on oak-core, I propose to move the
> {{PathFilter}} to oak-store-spi.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6269) Support non chunk storage in OakDirectory
[ https://issues.apache.org/jira/browse/OAK-6269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6269. - Bulk close for 1.7.9 > Support non chunk storage in OakDirectory > - > > Key: OAK-6269 > URL: https://issues.apache.org/jira/browse/OAK-6269 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Vikas Saurabh > Fix For: 1.8, 1.7.9 > > Attachments: > 0001-OAK-6269-Support-non-chunk-storage-in-OakDirectory.patch, > 0002-OAK-6269-Support-non-chunk-storage-in-OakDirectory.patch, > 0003-OAK-6269-Support-non-chunk-storage-in-OakDirectory.patch, > S3DsSupport.patch, s3Files.false.txt, s3Files.true.txt > > > Logging this issue based on offline discussion with [~catholicon]. > Currently OakDirectory stores files in chunk of 1 MB each. So a 1 GB file > would be stored in 1000+ chunks of 1 MB. > This design was done to support direct usage of OakDirectory with Lucene as > Lucene makes use of random io. Chunked storage allows it to seek to random > position quickly. If the files are stored as Blobs then its only possible to > access via streaming which would be slow > As most setup now use copy-on-read and copy-on-write support and rely on > local copy of index we can have an implementation which stores the file as > single blob. > *Pros* > * Quite a bit of reduction in number of small blobs stored in BlobStore. > Which should reduce the GC time specially for S3 > * Reduced overhead of storing a single file in repository. Instead of array > of 1k blobids we would be stored a single blobid > * Potential improvement in IO cost as file can be read in one connection and > uploaded in one. > *Cons* > It would not be possible to use OakDirectory directly (or would be very slow) > and we would always need to do local copy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6731) Remove implementation dependencies in non-factory classes
[
https://issues.apache.org/jira/browse/OAK-6731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6731.
-
Bulk close for 1.7.9
> Remove implementation dependencies in non-factory classes
> -
>
> Key: OAK-6731
> URL: https://issues.apache.org/jira/browse/OAK-6731
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core
>Reporter: angela
>Assignee: angela
> Fix For: 1.7.9
>
>
> {{TreeUtil}} and {{TreeTypeProvider}} rely on implementation details, which
> prevents us from refactoring the plugins.tree package out of oak-core.
> Also moving {{TreeConstants}} one level up would reduce the dependency to
> impl package throughout the code base.
> For the former issue [~stillalex] suggested to introduce a {{TreeTypeAware}}
> interface that defines the getter and setter for {{TreeType}}. Additionally I
> would suggest to introduce a marker interface {{ReadOnly}} to be able to
> detect if a {{Tree}} or {{Root}} only supports read operations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6716) RDB*Store: update DB2 JDBC dependency to 4.19.66
[ https://issues.apache.org/jira/browse/OAK-6716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6716. - Bulk close for 1.7.9 > RDB*Store: update DB2 JDBC dependency to 4.19.66 > > > Key: OAK-6716 > URL: https://issues.apache.org/jira/browse/OAK-6716 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, > candidate_oak_1_6 > Fix For: 1.8, 1.7.9 > > > (also remove the db2-license jar which we don't need here anyway) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6736) Upgrade PojoSR to handle SCR spec 1.3
[ https://issues.apache.org/jira/browse/OAK-6736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6736. - Bulk close for 1.7.9 > Upgrade PojoSR to handle SCR spec 1.3 > - > > Key: OAK-6736 > URL: https://issues.apache.org/jira/browse/OAK-6736 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: pojosr >Reporter: Robert Munteanu >Assignee: Chetan Mehrotra > Fix For: 1.8, 1.7.9 > > Attachments: OAK-6736-v1.patch > > > When upgrading to the new OSGi R6 annotations some components have their SCR > descriptors generated with the 1.3 version. These are not handled by the > Felix SCR implementation 1.8, used in the PojoSR project. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6729) PojoSR: RepositoryFactory tests should have timeouts
[ https://issues.apache.org/jira/browse/OAK-6729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6729. - Bulk close for 1.7.9 > PojoSR: RepositoryFactory tests should have timeouts > > > Key: OAK-6729 > URL: https://issues.apache.org/jira/browse/OAK-6729 > Project: Jackrabbit Oak > Issue Type: Bug > Components: pojosr >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Minor > Fix For: 1.8, 1.7.9 > > > When there is a problem with the undelrying repository setup some PojoSR > tests wait indefinitely, without timing out. > We should add timeouts to those tests to make sure that the build at least > fails instead of just hanging. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6723) Incorrect scope of logback-classic in oak-blob-plugins
[ https://issues.apache.org/jira/browse/OAK-6723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6723. - Bulk close for 1.7.9 > Incorrect scope of logback-classic in oak-blob-plugins > -- > > Key: OAK-6723 > URL: https://issues.apache.org/jira/browse/OAK-6723 > Project: Jackrabbit Oak > Issue Type: Bug > Components: blob-plugins >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 1.8, 1.7.9 > > > The scope of the logback-classic dependency is incorrect. Currently compile, > but should be test. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6717) DefaultIndexWriter using incorrect merge scheduler
[ https://issues.apache.org/jira/browse/OAK-6717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6717. - Bulk close for 1.7.9 > DefaultIndexWriter using incorrect merge scheduler > -- > > Key: OAK-6717 > URL: https://issues.apache.org/jira/browse/OAK-6717 > Project: Jackrabbit Oak > Issue Type: Bug > Components: lucene >Affects Versions: 1.7.0 >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Minor > Fix For: 1.8, 1.7.9 > > > With > [refactoring|https://github.com/apache/jackrabbit-oak/commit/84723e3f0ace69517e96548da71276fb9a685dd9#diff-8f9ff377295cc147ed2c1ff9119503bbR146] > done for OAK-6243 the condition to select the remote flag got inverted due > to which it started using SerialMergeScheduler for local directory. Instead > it should only use serial for remote directory -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6753) Wrong binding in TokenConfigurationImpl
[
https://issues.apache.org/jira/browse/OAK-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6753.
-
Bulk close for 1.7.9
> Wrong binding in TokenConfigurationImpl
>
>
> Key: OAK-6753
> URL: https://issues.apache.org/jira/browse/OAK-6753
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
>Reporter: Antonio Sanso
>Assignee: Alex Deparvu
> Fix For: 1.7.9
>
>
> OAK-6741 made a Switch to official OSGi component and metatype annotations.
> I spotted at least one lost in translation issue.
> {code}
> -@References({
> -@Reference(
> -name = "credentialsSupport",
> -referenceInterface = CredentialsSupport.class,
> -cardinality = ReferenceCardinality.OPTIONAL_MULTIPLE,
> -policy = ReferencePolicy.DYNAMIC)
> -})
> +@Reference(name = "credentialsSupport",
> +cardinality = ReferenceCardinality.OPTIONAL,
> +policy = ReferencePolicy.DYNAMIC)
> +@SuppressWarnings("UnusedDeclaration")
> {code}
> the {{CredentialsSupport}} reference used to be {{cardinality =
> ReferenceCardinality.OPTIONAL_MULTIPLE}} but is {{cardinality =
> ReferenceCardinality.OPTIONAL}} after the "migration"
> cc [~stillalex] [~jsedding] [~anchela]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6678) Syncing big blobs fails since StandbyServer sends persisted head
[
https://issues.apache.org/jira/browse/OAK-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6678.
-
Bulk close for 1.7.9
> Syncing big blobs fails since StandbyServer sends persisted head
>
>
> Key: OAK-6678
> URL: https://issues.apache.org/jira/browse/OAK-6678
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar, tarmk-standby
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
> Labels: cold-standby, resilience
> Fix For: 1.8, 1.7.9
>
> Attachments: OAK-6678-02.patch, OAK-6678-03.patch, OAK-6678.patch
>
>
> With changes for OAK-6653 in place,
> {{ExternalPrivateStoreIT#testSyncBigBlog}} and sometimes
> {{ExternalSharedStoreIT#testSyncBigBlob}} are failing on CI:
> {noformat}
> org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT
> testSyncBigBlob(org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT)
> Time elapsed: 96.82 sec <<< FAILURE!
> java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { }
> }>
> ...
> testSyncBigBlob(org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT)
> Time elapsed: 95.254 sec <<< FAILURE!
> java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { }
> }>
> {noformat}
> Partial stacktrace:
> {noformat}
> 14:09:08.355 DEBUG [main] StandbyServer.java:242Binding was
> successful
> 14:09:08.358 DEBUG [standby-1] GetHeadRequestEncoder.java:33 Sending request
> from client Bar for current head
> 14:09:08.359 DEBUG [primary-1] ClientFilterHandler.java:53 Client
> /127.0.0.1:52988 is allowed
> 14:09:08.360 DEBUG [primary-1] RequestDecoder.java:42 Parsed 'get head'
> message
> 14:09:08.360 DEBUG [primary-1] CommunicationObserver.java:79 Message 'get
> head' received from client Bar
> 14:09:08.362 DEBUG [primary-1] GetHeadRequestHandler.java:43 Reading head for
> client Bar
> 14:09:08.363 WARN [primary-1] ExceptionHandler.java:31 Exception caught
> on the server
> java.lang.NullPointerException: null
> at
> org.apache.jackrabbit.oak.segment.standby.server.DefaultStandbyHeadReader.readHeadRecordId(DefaultStandbyHeadReader.java:32)
> ~[oak-segment-tar-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> at
> org.apache.jackrabbit.oak.segment.standby.server.GetHeadRequestHandler.channelRead0(GetHeadRequestHandler.java:45)
> ~[oak-segment-tar-1.8-SNAPSHOT.jar:1.8-SNAPSHOT]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6715) Log elapsed time even if actual count is more than estimate
[ https://issues.apache.org/jira/browse/OAK-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6715. - Bulk close for 1.7.9 > Log elapsed time even if actual count is more than estimate > --- > > Key: OAK-6715 > URL: https://issues.apache.org/jira/browse/OAK-6715 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Minor > Fix For: 1.8, 1.7.9 > > > IndexingProgressReporter currently stops logging the time is actual count > crosses the estimated count. In such a case it would still be useful to log > elapsed time -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6718) Configure RAM buffer size used by IndexWriter with oak-run indexing
[ https://issues.apache.org/jira/browse/OAK-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6718. - Bulk close for 1.7.9 > Configure RAM buffer size used by IndexWriter with oak-run indexing > --- > > Key: OAK-6718 > URL: https://issues.apache.org/jira/browse/OAK-6718 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene, run >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.8, 1.7.9 > > Attachments: OAK-6718-v1.patch > > > Lucene IndexWriter uses 16M buffer by default. For reindexing of large repo > via oak-run it should be possible to set this to higher value like 300MB. > In one of the test which indexes 65M entries setting the buffer size to 300M > reduced the reindexing time from 2 hrs to 1.1 hrs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6824) oak-run console should have some helpers to compose editors based on repository state
[ https://issues.apache.org/jira/browse/OAK-6824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Saurabh updated OAK-6824: --- Description: Currently, different oak console scripts do a merge using EmptyHook.INSTANCE. That then requires to take care of various hidden structures which could have easily been taken care of in-built editors. That said, I think it'd be useful to only have utilities to compose editors in scripts - we would most likely _not_ want default behavior (all editors coming into play) if some recovery is being required via oak-run. Also, this would be a good point to at least identify some kind of safety check-list while operating directly on the node-store (or even riskier on mongo). /cc [~chetanm] was: Currently, different oak console scripts do a merge using EmptyHook.INSTANCE. That then requires to take care of various hidden structures which could have easily been taken care of in-built editors. That said, I think it'd be useful to only have utilities to compose editors in scripts - we would most likely _not_ want default behavior (all editors coming into play) if some recovery is being required via oak-run. /cc [~chetanm] > oak-run console should have some helpers to compose editors based on > repository state > - > > Key: OAK-6824 > URL: https://issues.apache.org/jira/browse/OAK-6824 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Vikas Saurabh >Assignee: Vikas Saurabh >Priority: Minor > > Currently, different oak console scripts do a merge using EmptyHook.INSTANCE. > That then requires to take care of various hidden structures which could have > easily been taken care of in-built editors. > That said, I think it'd be useful to only have utilities to compose editors > in scripts - we would most likely _not_ want default behavior (all editors > coming into play) if some recovery is being required via oak-run. > Also, this would be a good point to at least identify some kind of safety > check-list while operating directly on the node-store (or even riskier on > mongo). > /cc [~chetanm] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6826) Refactor Jcr class to remove dependency on o.a.j.oak.plugins.index
[
https://issues.apache.org/jira/browse/OAK-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203205#comment-16203205
]
Alex Deparvu commented on OAK-6826:
---
In {{oak-jcr}} there's an OSGi component ({{RepositoryManager}}) that
references {{IndexEditorProvider}} and {{WhiteboardIndexEditorProvider}}.
> Refactor Jcr class to remove dependency on o.a.j.oak.plugins.index
> --
>
> Key: OAK-6826
> URL: https://issues.apache.org/jira/browse/OAK-6826
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: jcr
>Reporter: Alex Deparvu
>Assignee: Alex Deparvu
>Priority: Minor
>
> I'd like to take a look at the Jcr class, to have it rely more on api/spi
> classes and reduce if possible references to oak-core impl.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6826) Refactor Jcr class to remove dependency on o.a.j.oak.plugins.index
[ https://issues.apache.org/jira/browse/OAK-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Deparvu updated OAK-6826: -- Summary: Refactor Jcr class to remove dependency on o.a.j.oak.plugins.index (was: Refactor Jcr class) > Refactor Jcr class to remove dependency on o.a.j.oak.plugins.index > -- > > Key: OAK-6826 > URL: https://issues.apache.org/jira/browse/OAK-6826 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: jcr >Reporter: Alex Deparvu >Assignee: Alex Deparvu >Priority: Minor > > I'd like to take a look at the Jcr class, to have it rely more on api/spi > classes and reduce if possible references to oak-core impl. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OAK-6826) Refactor Jcr class
[
https://issues.apache.org/jira/browse/OAK-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203176#comment-16203176
]
Alex Deparvu edited comment on OAK-6826 at 10/13/17 8:41 AM:
-
first try on a WIP branch [0].
Similar to the {{InitialContent}} class I introduced a {{OakDefaultComponents}}
class in oak-core that hosts all the default values for various components we
initialise by default. this only moves the reference problem to oak-core, but
at least reduces oak-jcr dependency footprint.
Not sure what to do with
{{org.apache.jackrabbit.oak.plugins.index.IndexEditorProvider}} and
{{org.apache.jackrabbit.oak.plugins.observation.CommitRateLimiter}} yet.
Also, the only {{CommitHook}} we have left here is the {{VersionHook}} which
does not look like a commit hook at all (it's more of a composite editor), so I
think it would be worthwhile to refactor this class into a proper Editor.
[~tmueller], [~anchela] thoughts?
[edit] turned this issue into a subtask of the indexing refactoring to make it
more focused.
[0] https://github.com/apache/jackrabbit-oak/compare/trunk...stillalex:OAK-6826
was (Author: alex.parvulescu):
first try on a WIP branch [0].
Similar to the {{InitialContent}} class I introduced a {{OakDefaultComponents}}
class in oak-core that hosts all the default values for various components we
initialise by default. this only moves the reference problem to oak-core, but
at least reduces oak-jcr dependency footprint.
Not sure what to do with
{{org.apache.jackrabbit.oak.plugins.index.IndexEditorProvider}} and
{{org.apache.jackrabbit.oak.plugins.observation.CommitRateLimiter}} yet.
Also, the only {{CommitHook}} we have left here is the {{VersionHook}} which
does not look like a commit hook at all (it's more of a composite editor), so I
think it would be worthwhile to refactor this class into a proper Editor.
[~tmueller], [~anchela] thoughts?
[0] https://github.com/apache/jackrabbit-oak/compare/trunk...stillalex:OAK-6826
> Refactor Jcr class
> --
>
> Key: OAK-6826
> URL: https://issues.apache.org/jira/browse/OAK-6826
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: jcr
>Reporter: Alex Deparvu
>Assignee: Alex Deparvu
>Priority: Minor
>
> I'd like to take a look at the Jcr class, to have it rely more on api/spi
> classes and reduce if possible references to oak-core impl.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6826) Refactor Jcr class
[ https://issues.apache.org/jira/browse/OAK-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Deparvu updated OAK-6826: -- Issue Type: Technical task (was: Improvement) Parent: OAK-6408 > Refactor Jcr class > -- > > Key: OAK-6826 > URL: https://issues.apache.org/jira/browse/OAK-6826 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: jcr >Reporter: Alex Deparvu >Assignee: Alex Deparvu >Priority: Minor > > I'd like to take a look at the Jcr class, to have it rely more on api/spi > classes and reduce if possible references to oak-core impl. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6826) Refactor Jcr class
[
https://issues.apache.org/jira/browse/OAK-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203176#comment-16203176
]
Alex Deparvu commented on OAK-6826:
---
first try on a WIP branch [0].
Similar to the {{InitialContent}} class I introduced a {{OakDefaultComponents}}
class in oak-core that hosts all the default values for various components we
initialise by default. this only moves the reference problem to oak-core, but
at least reduces oak-jcr dependency footprint.
Not sure what to do with
{{org.apache.jackrabbit.oak.plugins.index.IndexEditorProvider}} and
{{org.apache.jackrabbit.oak.plugins.observation.CommitRateLimiter}} yet.
Also, the only {{CommitHook}} we have left here is the {{VersionHook}} which
does not look like a commit hook at all (it's more of a composite editor), so I
think it would be worthwhile to refactor this class into a proper Editor.
[~tmueller], [~anchela] thoughts?
[0] https://github.com/apache/jackrabbit-oak/compare/trunk...stillalex:OAK-6826
> Refactor Jcr class
> --
>
> Key: OAK-6826
> URL: https://issues.apache.org/jira/browse/OAK-6826
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
>Reporter: Alex Deparvu
>Assignee: Alex Deparvu
>Priority: Minor
>
> I'd like to take a look at the Jcr class, to have it rely more on api/spi
> classes and reduce if possible references to oak-core impl.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6826) Refactor Jcr class
Alex Deparvu created OAK-6826: - Summary: Refactor Jcr class Key: OAK-6826 URL: https://issues.apache.org/jira/browse/OAK-6826 Project: Jackrabbit Oak Issue Type: Improvement Components: jcr Reporter: Alex Deparvu Assignee: Alex Deparvu Priority: Minor I'd like to take a look at the Jcr class, to have it rely more on api/spi classes and reduce if possible references to oak-core impl. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6658) Move oak.spi.xml to oak-security-spi
[
https://issues.apache.org/jira/browse/OAK-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Deparvu resolved OAK-6658.
---
Resolution: Duplicate
already fixed with OAK-6318
> Move oak.spi.xml to oak-security-spi
>
>
> Key: OAK-6658
> URL: https://issues.apache.org/jira/browse/OAK-6658
> Project: Jackrabbit Oak
> Issue Type: Task
>Reporter: Alex Deparvu
>Assignee: angela
>
> This package is referenced by other packages so it needs to move out of
> {{oak-core}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6824) oak-run console should have some helpers to compose editors based on repository state
[ https://issues.apache.org/jira/browse/OAK-6824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Saurabh updated OAK-6824: --- Summary: oak-run console should have some helpers to compose editors based on repository state (was: oak-run console should have some helps to compose editors based on repository state) > oak-run console should have some helpers to compose editors based on > repository state > - > > Key: OAK-6824 > URL: https://issues.apache.org/jira/browse/OAK-6824 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Vikas Saurabh >Assignee: Vikas Saurabh >Priority: Minor > > Currently, different oak console scripts do a merge using EmptyHook.INSTANCE. > That then requires to take care of various hidden structures which could have > easily been taken care of in-built editors. > That said, I think it'd be useful to only have utilities to compose editors > in scripts - we would most likely _not_ want default behavior (all editors > coming into play) if some recovery is being required via oak-run. > /cc [~chetanm] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6820) Implement support for disabling indexes which are replaced with newer index
[
https://issues.apache.org/jira/browse/OAK-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203153#comment-16203153
]
Vikas Saurabh commented on OAK-6820:
Other than what we discussed the other about that IndexUpdate would now need
some sort of understanding of index def, the idea seems fine to me.
Btw, this opens up another question: while sure disabling a prop index is the
quickest way - but, maybe, we should also need to expose some jmx to clean up
such indices - maybe your recursive delete (OAK-6787) could become useful in
this case too? Yes, that' a separate issue, of course.
> Implement support for disabling indexes which are replaced with newer index
> ---
>
> Key: OAK-6820
> URL: https://issues.apache.org/jira/browse/OAK-6820
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: indexing
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
> Fix For: 1.8
>
>
> For upgrade case in many applications older index type is set to {{disabled}}
> when new index is provisioned. If the new index is async then it would take
> some time for reindex and till then any query which used to make use of old
> index would end up traversing the repository
> To avoid such a scenario we should only mark older index as "disabled" only
> if the newer index is reindex.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6820) Implement support for disabling indexes which are replaced with newer index
[
https://issues.apache.org/jira/browse/OAK-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203107#comment-16203107
]
Chetan Mehrotra commented on OAK-6820:
--
While doing this we would also need to support disabling entries in nodetype
index like removing specific nodetype from
/oak:index/nodetype/@declaringNodeType
> Implement support for disabling indexes which are replaced with newer index
> ---
>
> Key: OAK-6820
> URL: https://issues.apache.org/jira/browse/OAK-6820
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: indexing
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
> Fix For: 1.8
>
>
> For upgrade case in many applications older index type is set to {{disabled}}
> when new index is provisioned. If the new index is async then it would take
> some time for reindex and till then any query which used to make use of old
> index would end up traversing the repository
> To avoid such a scenario we should only mark older index as "disabled" only
> if the newer index is reindex.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
