[jira] [Commented] (OAK-6882) ObservationQueueFullWarnTest.testQueueFullThenFlushing failing
[
https://issues.apache.org/jira/browse/OAK-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16251028#comment-16251028
]
Julian Reschke commented on OAK-6882:
-
This is affecting my testing a lot.
Can we either fix this, or disable the test?
> ObservationQueueFullWarnTest.testQueueFullThenFlushing failing
> --
>
> Key: OAK-6882
> URL: https://issues.apache.org/jira/browse/OAK-6882
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Affects Versions: 1.7.10
>Reporter: Julian Reschke
>Assignee: Vikas Saurabh
> Attachments:
> org.apache.jackrabbit.oak.jcr.observation.ObservationQueueFullWarnTest-output.txt,
> org.apache.jackrabbit.oak.jcr.observation.ObservationQueueFullWarnTest.txt
>
>
> {noformat}
> [ERROR]
> testQueueFullThenFlushing[SegmentTar](org.apache.jackrabbit.oak.jcr.observation.ObservationQueueFullWarnTest)
> Time elapsed: 0.262 s <<< FAILURE!
> java.lang.AssertionError: Just filled queue must not convert local->external
> expected:<6> but was:<4>
> at
> org.apache.jackrabbit.oak.jcr.observation.ObservationQueueFullWarnTest.testQueueFullThenFlushing(ObservationQueueFullWarnTest.java:347)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6925) Build Jackrabbit Oak #962 failed
[ https://issues.apache.org/jira/browse/OAK-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16250416#comment-16250416 ] Hudson commented on OAK-6925: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #969|https://builds.apache.org/job/Jackrabbit%20Oak/969/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/969/console] > Build Jackrabbit Oak #962 failed > > > Key: OAK-6925 > URL: https://issues.apache.org/jira/browse/OAK-6925 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > Labels: ci, jenkins, test-failure > Fix For: 1.8 > > > No description is provided > The build Jackrabbit Oak #962 has failed. > First failed run: [Jackrabbit Oak > #962|https://builds.apache.org/job/Jackrabbit%20Oak/962/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/962/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6931) Enable the -Dcache of offline compaction
[
https://issues.apache.org/jira/browse/OAK-6931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6931:
---
Fix Version/s: 1.7.12
> Enable the -Dcache of offline compaction
>
>
> Key: OAK-6931
> URL: https://issues.apache.org/jira/browse/OAK-6931
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Affects Versions: 1.6.7
>Reporter: Michael Dürig
>Assignee: Michael Dürig
> Labels: compaction, gc, tooling
> Fix For: 1.8, 1.6.6, 1.7.12
>
> Attachments: OAK-6931.patch
>
>
> The {{-Dcache}} option currently has no effect when used in conjunction with
> the {{compact}} run mode of {{oak-run}}. However we should enable users to
> configure the segment cache size through this option if necessary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6931) Enable the -Dcache of offline compaction
[
https://issues.apache.org/jira/browse/OAK-6931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6931:
---
Attachment: OAK-6931.patch
Proposed patch [^OAK-6931.patch]. [~frm] could you have a look please?
> Enable the -Dcache of offline compaction
>
>
> Key: OAK-6931
> URL: https://issues.apache.org/jira/browse/OAK-6931
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Affects Versions: 1.6.7
>Reporter: Michael Dürig
>Assignee: Michael Dürig
> Labels: compaction, gc, tooling
> Fix For: 1.8, 1.6.6
>
> Attachments: OAK-6931.patch
>
>
> The {{-Dcache}} option currently has no effect when used in conjunction with
> the {{compact}} run mode of {{oak-run}}. However we should enable users to
> configure the segment cache size through this option if necessary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6931) Enable the -Dcache of offline compaction
[
https://issues.apache.org/jira/browse/OAK-6931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6931:
---
Fix Version/s: 1.8
> Enable the -Dcache of offline compaction
>
>
> Key: OAK-6931
> URL: https://issues.apache.org/jira/browse/OAK-6931
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Affects Versions: 1.6.7
>Reporter: Michael Dürig
>Assignee: Michael Dürig
> Labels: compaction, gc, tooling
> Fix For: 1.8, 1.6.6
>
>
> The {{-Dcache}} option currently has no effect when used in conjunction with
> the {{compact}} run mode of {{oak-run}}. However we should enable users to
> configure the segment cache size through this option if necessary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6937) use Tika version consistent with other modules
Julian Reschke created OAK-6937: --- Summary: use Tika version consistent with other modules Key: OAK-6937 URL: https://issues.apache.org/jira/browse/OAK-6937 Project: Jackrabbit Oak Issue Type: Task Components: oak-http Reporter: Julian Reschke Priority: Minor Fix For: 1.8 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6936) use current Tika version 1.16
Julian Reschke created OAK-6936: --- Summary: use current Tika version 1.16 Key: OAK-6936 URL: https://issues.apache.org/jira/browse/OAK-6936 Project: Jackrabbit Oak Issue Type: Task Components: parent Reporter: Julian Reschke Priority: Minor Fix For: 1.8 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6925) Build Jackrabbit Oak #962 failed
[ https://issues.apache.org/jira/browse/OAK-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16250058#comment-16250058 ] Hudson commented on OAK-6925: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #968|https://builds.apache.org/job/Jackrabbit%20Oak/968/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/968/console] > Build Jackrabbit Oak #962 failed > > > Key: OAK-6925 > URL: https://issues.apache.org/jira/browse/OAK-6925 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > Labels: ci, jenkins, test-failure > Fix For: 1.8 > > > No description is provided > The build Jackrabbit Oak #962 has failed. > First failed run: [Jackrabbit Oak > #962|https://builds.apache.org/job/Jackrabbit%20Oak/962/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/962/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6935) Active deletion logs warn messages when it tries to delete blobs already purged by DSGC
Vikas Saurabh created OAK-6935: -- Summary: Active deletion logs warn messages when it tries to delete blobs already purged by DSGC Key: OAK-6935 URL: https://issues.apache.org/jira/browse/OAK-6935 Project: Jackrabbit Oak Issue Type: Bug Components: lucene Reporter: Vikas Saurabh Assignee: Vikas Saurabh Priority: Minor In cases when BlobGC deleted the blobs which active delete logic later came around to purge., active deletion logs a warn message. An example timeline would be: * t1 -> index blob gets deleted (active delete logic notes it down) * t2 -> compaction removes ref to this blob from node store * t3 (t1 + 24 hours) -> blob gc runs and collects the blob * t4 -> active gc tries to purge an already deleted blob (note, active delete runs between t1 and t3 would not delete the blobs as it hasn't be 24 hours since blob deletion). While this would happen for a small set of blobs (that are unfortunate to get compacted and cleaned up by DSGC before active deletion comes around) - but, the warn log is annoying. It would be useful to detect this case and not log warn on failure to delete for these. /cc [~amjain] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6915) Minimize the amount of uncached segment reads
[
https://issues.apache.org/jira/browse/OAK-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari resolved OAK-6915.
-
Resolution: Fixed
Fixed at r1815118. Thanks everyone for your feedback and your help!
> Minimize the amount of uncached segment reads
> -
>
> Key: OAK-6915
> URL: https://issues.apache.org/jira/browse/OAK-6915
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
> Fix For: 1.8, 1.7.12
>
> Attachments: OAK-6915-01.patch, OAK-6915-02.patch, OAK-6915-03.patch,
> OAK-6915-04.patch, OAK-6915-05.patch, OAK-6915-diagnostics-02.patch,
> OAK-6915-diagnostics.patch, OAK-6915.patch, Screen Shot 2017-11-09 at
> 14.14.28.png, Screen Shot 2017-11-09 at 14.16.59.png
>
>
> The current implementation of {{SegmentCache}} should make better use of the
> underlying Guava cache by relying on the cached segments instead of
> unconditionally performing an uncached segment read via the
> {{Callable}} passed to {{SegmentCache#getSegment}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-5361) switch to stable release of org.apache.directory.api.api-all
[ https://issues.apache.org/jira/browse/OAK-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249777#comment-16249777 ] Manfred Baedke commented on OAK-5361: - Commited to trunk: r1815115 > switch to stable release of org.apache.directory.api.api-all > > > Key: OAK-5361 > URL: https://issues.apache.org/jira/browse/OAK-5361 > Project: Jackrabbit Oak > Issue Type: Task > Components: auth-ldap >Reporter: Julian Reschke >Assignee: Manfred Baedke > Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, > candidate_oak_1_6, patch-available > Fix For: 1.8 > > Attachments: OAK-5361.diff > > > We currently use a release candidate, but could switch to 1.0.0 (see > https://mvnrepository.com/artifact/org.apache.directory.api/api-all) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-5361) switch to stable release of org.apache.directory.api.api-all
[ https://issues.apache.org/jira/browse/OAK-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke resolved OAK-5361. - Resolution: Done > switch to stable release of org.apache.directory.api.api-all > > > Key: OAK-5361 > URL: https://issues.apache.org/jira/browse/OAK-5361 > Project: Jackrabbit Oak > Issue Type: Task > Components: auth-ldap >Reporter: Julian Reschke >Assignee: Manfred Baedke > Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, > candidate_oak_1_6, patch-available > Fix For: 1.8 > > Attachments: OAK-5361.diff > > > We currently use a release candidate, but could switch to 1.0.0 (see > https://mvnrepository.com/artifact/org.apache.directory.api/api-all) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6932) Add test coverage of spi.xml package
[ https://issues.apache.org/jira/browse/OAK-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela resolved OAK-6932. - Resolution: Fixed Fix Version/s: 1.7.12 1.8 > Add test coverage of spi.xml package > > > Key: OAK-6932 > URL: https://issues.apache.org/jira/browse/OAK-6932 > Project: Jackrabbit Oak > Issue Type: Task > Components: security-spi >Reporter: angela >Assignee: angela > Fix For: 1.8, 1.7.12 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6934) Add test coverage of spi.tree package
angela created OAK-6934: --- Summary: Add test coverage of spi.tree package Key: OAK-6934 URL: https://issues.apache.org/jira/browse/OAK-6934 Project: Jackrabbit Oak Issue Type: Task Components: security-spi Reporter: angela Assignee: angela [~stillalex] fyi -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6933) Fix nullable annotations in PasswordUtil
[
https://issues.apache.org/jira/browse/OAK-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved OAK-6933.
-
Resolution: Fixed
Fix Version/s: 1.7.12
1.8
Committed revision 1815107.
> Fix nullable annotations in PasswordUtil
>
>
> Key: OAK-6933
> URL: https://issues.apache.org/jira/browse/OAK-6933
> Project: Jackrabbit Oak
> Issue Type: Improvement
>Reporter: angela
>Assignee: angela
>Priority: Minor
> Fix For: 1.8, 1.7.12
>
>
> While writing tests I noticed a few cases where annotations with
> {{PasswordUtil}} were missing or could be defined to be {{Nonnull}}.
> [~stillalex], fyi
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6933) Fix nullable annotations in PasswordUtil
angela created OAK-6933:
---
Summary: Fix nullable annotations in PasswordUtil
Key: OAK-6933
URL: https://issues.apache.org/jira/browse/OAK-6933
Project: Jackrabbit Oak
Issue Type: Improvement
Reporter: angela
Assignee: angela
Priority: Minor
While writing tests I noticed a few cases where annotations with
{{PasswordUtil}} were missing or could be defined to be {{Nonnull}}.
[~stillalex], fyi
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6932) Add test coverage of spi.xml package
angela created OAK-6932: --- Summary: Add test coverage of spi.xml package Key: OAK-6932 URL: https://issues.apache.org/jira/browse/OAK-6932 Project: Jackrabbit Oak Issue Type: Task Components: security-spi Reporter: angela Assignee: angela -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6829) ExternalPrivateStoreIT/ExternalSharedStoreIT.testSyncBigBlob failures
[
https://issues.apache.org/jira/browse/OAK-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6829.
-
Bulk close 1.7.11
> 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
>Assignee: Francesco Mari
> Fix For: 1.8, 1.7.11
>
> 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.ExternalPrivateStoreIT-output.txt,
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT-output.txt,
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT-output.txt,
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT-output.txt,
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT-output.txt,
> org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT-output.txt,
> org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT-output.txt,
> org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT-output.txt,
> org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT-output.txt,
> org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT-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] [Closed] (OAK-6877) NodeBuilder#isReplaced behaves incorrectly for SegmentNodeStore
[
https://issues.apache.org/jira/browse/OAK-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6877.
-
Bulk close 1.7.11
> NodeBuilder#isReplaced behaves incorrectly for SegmentNodeStore
> ---
>
> Key: OAK-6877
> URL: https://issues.apache.org/jira/browse/OAK-6877
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Chetan Mehrotra
>Assignee: Michael Dürig
>Priority: Minor
> Fix For: 1.8, 1.7.11
>
> Attachments: OAK-6877-v1.patch
>
>
> As seen in OAK-6876 NodeBuilder reports incorrectly for isReplaced call.
> Following test fails for Segment fixture
> {noformat}
> @Test
> public void isReplacedBehaviour() throws Exception{
> NodeBuilder nb = store.getRoot().builder();
> nb.child("a").setProperty("foo", "bar");
> store.merge(nb, EmptyHook.INSTANCE, CommitInfo.EMPTY);
> nb = store.getRoot().builder();
> nb.child("a").child("b");
> assertFalse(nb.getChildNode("a").isReplaced("foo"));
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6871) Composite roles are not compatible with Windows
[ https://issues.apache.org/jira/browse/OAK-6871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6871. - Bulk close 1.7.11 > Composite roles are not compatible with Windows > --- > > Key: OAK-6871 > URL: https://issues.apache.org/jira/browse/OAK-6871 > Project: Jackrabbit Oak > Issue Type: Bug > Components: composite >Affects Versions: 1.7.10 >Reporter: Tomek Rękawek > Fix For: 1.8, 1.7.11 > > > Composite Node Store uses following format for the roles: > * composite:global > * composite:mount:libs > When using Segment Node Store Factory, it tries to create following > directories for: > * segmentstore-composite:global > * segmentstore-composite:mount:libs > However, Windows doesn't support file names with colons. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-1327) Cleanup NodeStore and MK implementations
[ https://issues.apache.org/jira/browse/OAK-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-1327. - Bulk close 1.7.11 > Cleanup NodeStore and MK implementations > > > Key: OAK-1327 > URL: https://issues.apache.org/jira/browse/OAK-1327 > Project: Jackrabbit Oak > Issue Type: Wish > Components: core, documentmk >Reporter: angela > Labels: modularization, technical_debt > Fix For: 1.8, 1.7.11 > > Attachments: OAK-1327.patch > > > as discussed during the oak-call today, i would like to cleanup the code base > before we officially release OAK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-2621) Too many reads for child nodes
[
https://issues.apache.org/jira/browse/OAK-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-2621.
-
Bulk close 1.7.11
> Too many reads for child nodes
> --
>
> Key: OAK-2621
> URL: https://issues.apache.org/jira/browse/OAK-2621
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
>Affects Versions: 1.0
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
> Labels: performance
> Fix For: 1.8, 1.7.11
>
>
> The DocumentNodeStore issues a lot of reads when sibling nodes are deleted,
> which are also index with a property index.
> The following calls will become a hotspot:
> {noformat}
> at
> org.apache.jackrabbit.oak.plugins.document.mongo.MongoDocumentStore.query(MongoDocumentStore.java:406)
> at
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.readChildDocs(DocumentNodeStore.java:846)
> at
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.readChildren(DocumentNodeStore.java:788)
> at
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.getChildren(DocumentNodeStore.java:753)
> at
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeState.getChildNodeCount(DocumentNodeState.java:194)
> at
> org.apache.jackrabbit.oak.plugins.memory.ModifiedNodeState.getChildNodeCount(ModifiedNodeState.java:198)
> at
> org.apache.jackrabbit.oak.plugins.memory.MutableNodeState.getChildNodeCount(MutableNodeState.java:265)
> at
> org.apache.jackrabbit.oak.plugins.memory.MemoryNodeBuilder.getChildNodeCount(MemoryNodeBuilder.java:293)
> at
> org.apache.jackrabbit.oak.plugins.index.property.strategy.ContentMirrorStoreStrategy.prune(ContentMirrorStoreStrategy.java:456)
> {noformat}
> I think the code triggering this issue is in
> {{ModifiedNodeState.getChildNodeCount()}}. It keeps track of already deleted
> children and requests {{max += deleted}}. The actual {{max}} is always 1 as
> requested from {{ContentMirrorStoreStrategy.prune()}}, but as more nodes get
> deleted, the higher {{max}} gets passed to
> {{DocumentNodeState.getChildNodeCount()}}. The DocumentNodeStore then checks
> if it has the children in the cache, only to find out the cache entry has too
> few entries and it needs to fetch one more.
> It would be best to have a minimum number of child nodes to fetch from
> MongoDB in this case. E.g. when NodeState.getChildNodeEntries() is called,
> the DocumentNodeState fetches 100 children.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6866) Force compaction timeout logs wrong number of seconds
[
https://issues.apache.org/jira/browse/OAK-6866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6866.
-
Bulk close 1.7.11
> Force compaction timeout logs wrong number of seconds
> --
>
> Key: OAK-6866
> URL: https://issues.apache.org/jira/browse/OAK-6866
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
>Priority: Minor
> Fix For: 1.8, 1.7.11
>
>
> When force compaction fails it logs a message like
> {noformat}
> TarMK GC #11: compaction failed to force compact remaining commits after
> 1.000 min (60016 ms). Compaction was cancelled: Timeout after 1508640269
> seconds.
> {noformat}
> The number of seconds is completely off (it actually the number of seconds
> since January 1st 1970).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6740) Test failure: StandbyTestIT.testSyncLoop()
[
https://issues.apache.org/jira/browse/OAK-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6740.
-
Bulk close 1.7.11
> Test failure: StandbyTestIT.testSyncLoop()
> --
>
> Key: OAK-6740
> URL: https://issues.apache.org/jira/browse/OAK-6740
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, segment-tar
>Affects Versions: 1.7.8
>Reporter: Hudson
>Assignee: Francesco Mari
> Fix For: 1.8, 1.7.11
>
>
> No description is provided
> The build Jackrabbit Oak #807 has failed.
> First failed run: [Jackrabbit Oak
> #807|https://builds.apache.org/job/Jackrabbit%20Oak/807/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/807/console]
> {noformat}
> Failed tests:
> StandbyTestIT.testSyncLoop:126 expected:<{ checkpoints = { ... }, root = {
> ... } }> but was:<{ checkpoints : { }, root = { ... } }>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6868) Simplify setup of access tracking of the file store caches
[
https://issues.apache.org/jira/browse/OAK-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6868.
-
Bulk close 1.7.11
> Simplify setup of access tracking of the file store caches
> ---
>
> Key: OAK-6868
> URL: https://issues.apache.org/jira/browse/OAK-6868
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
>Priority: Minor
> Fix For: 1.8, 1.7.11
>
>
> Access tracking for the caches during compaction can be setup in the
> {{FileStore}} constructor once and for all instead of every time compaction
> is run.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6875) Lucene index: the query read limit is ignored
[ https://issues.apache.org/jira/browse/OAK-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6875. - Bulk close 1.7.11 > Lucene index: the query read limit is ignored > - > > Key: OAK-6875 > URL: https://issues.apache.org/jira/browse/OAK-6875 > Project: Jackrabbit Oak > Issue Type: Bug > Components: lucene >Reporter: Thomas Mueller >Assignee: Thomas Mueller > Fix For: 1.7.11 > > > Currently, the query read limit is ignored if a query uses a Lucene index. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6775) Suggest directory should utilize CopyOnRead if available
[ https://issues.apache.org/jira/browse/OAK-6775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6775. - Bulk close 1.7.11 > Suggest directory should utilize CopyOnRead if available > > > Key: OAK-6775 > URL: https://issues.apache.org/jira/browse/OAK-6775 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Vikas Saurabh >Assignee: Vikas Saurabh >Priority: Minor > Fix For: 1.8, 1.7.11 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6901) Unknown channel option 'TCP_NODELAY' for channel warning in cold standby
[
https://issues.apache.org/jira/browse/OAK-6901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6901.
-
Bulk close 1.7.11
> Unknown channel option 'TCP_NODELAY' for channel warning in cold standby
>
>
> Key: OAK-6901
> URL: https://issues.apache.org/jira/browse/OAK-6901
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar, tarmk-standby
>Affects Versions: 1.7.6
>Reporter: Andrei Dulceanu
>Assignee: Francesco Mari
>Priority: Minor
> Labels: cold-standby
> Fix For: 1.7.11
>
>
> After the netty upgrade in OAK-6564, there's a recurring warning appearing in
> the server thread:
> {noformat}
> 18:54:44.691 [main] WARN io.netty.bootstrap.ServerBootstrap - Unknown
> channel option 'TCP_NODELAY' for channel '[id: 0xa64bc5c4]'
> {noformat}
> We need to see what's causing it (i.e. was that option removed in the latest
> version? if yes, is there a substitute/change needed?).
> /cc [~frm]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6907) RDB*Store: require ojdbc 12.2.0.1 because of known issues in earlier versions
[ https://issues.apache.org/jira/browse/OAK-6907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6907. - Bulk close 1.7.11 > RDB*Store: require ojdbc 12.2.0.1 because of known issues in earlier versions > - > > Key: OAK-6907 > URL: https://issues.apache.org/jira/browse/OAK-6907 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.8, 1.7.11, 1.6.7 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6861) Warn messages when building oak-query-spi
[
https://issues.apache.org/jira/browse/OAK-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6861.
-
Bulk close 1.7.11
> Warn messages when building oak-query-spi
> -
>
> Key: OAK-6861
> URL: https://issues.apache.org/jira/browse/OAK-6861
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Minor
> Fix For: 1.8, 1.7.11
>
>
> There are warn messages when building oak-query-spi or depending modules:
> {noformat}
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.jackrabbit:oak-query-spi:bundle:1.8-SNAPSHOT
> [WARNING] 'build.plugins.plugin.version' for
> org.apache.felix:maven-scr-plugin is missing. @
> org.apache.jackrabbit:oak-query-spi:[unknown-version],
> /Users/mreutegg/devel/apache/oak_clean/trunk/oak-query-spi/pom.xml, line 66,
> column 17
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> {noformat}
> The plugin is not needed anymore. See also OAK-6449.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6857) Lucene unique index should check path validity for uniqueness constraint
[
https://issues.apache.org/jira/browse/OAK-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6857.
-
Bulk close 1.7.11
> Lucene unique index should check path validity for uniqueness constraint
>
>
> Key: OAK-6857
> URL: https://issues.apache.org/jira/browse/OAK-6857
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: lucene
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
> Fix For: 1.8, 1.7.11
>
>
> The {{UniquenessConstraintValidator}} currently checks for any new index
> entry if any matching entry is found in primary (property) and secondary
> (lucene) index.
> This can lead to false positive where the entry in index is obsolete and due
> to async index lagging behind is yet not pruned. For e.g. if
> # Time T1 - path /a/@uuid=1 existed , present in lucene index
> # Time T2 - path /a removed (async index yet not catched up)
> # Time T3 - path /b/@uuid=1 being created.
> In this case save should pass. However as async index has yet not catched up
> it reports a constraint validation exception. As a fix
> {{UniquenessConstraintValidator}} should check if reported paths are valid
> wrt current revision
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6626) Replace standby blob chunk size configuration with feature flag
[
https://issues.apache.org/jira/browse/OAK-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6626.
-
Bulk close 1.7.11
> Replace standby blob chunk size configuration with feature flag
> ---
>
> Key: OAK-6626
> URL: https://issues.apache.org/jira/browse/OAK-6626
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar, tarmk-standby
>Reporter: Michael Dürig
>Assignee: Andrei Dulceanu
> Labels: cold-standby, configuration
> Fix For: 1.8, 1.7.11
>
> Attachments: OAK-6626.patch
>
>
> We should remove the {{StandbyStoreService#BLOB_CHUNK_SIZE}} OSGi
> configuration and replace it with a feature flag. Rational: we expect
> customer to rarely change this thus not justifying the additional
> configuration complexity and testing overhead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6864) IndexUpdate should disable superseded indexes only during an async cycle run
[
https://issues.apache.org/jira/browse/OAK-6864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6864.
-
Bulk close 1.7.11
> IndexUpdate should disable superseded indexes only during an async cycle run
>
>
> Key: OAK-6864
> URL: https://issues.apache.org/jira/browse/OAK-6864
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: indexing
>Affects Versions: 1.7.10
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
>Priority: Minor
> Fix For: 1.8, 1.7.11
>
>
> Once an superseding index is indexed (has {{:disableIndexesOnNextCycle}}
> flag) then IndexUpdate disables the superseded index the next time
> superseding index is indexed. So, if we have and async index running in nrt
> mode too - then nrt updates also disable indexes.
> We should have a more controlled disabling action (apart from concurrent
> nrt/sync updates would likely conflict with each to fail the commit) - do it
> in async cycle.
> Note: This is only relevant when superseding index is an async index -
> superseding sync indexes would continue to work as earlier.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-3878) Avoid caching of NodeDocument while iterating in BlobReferenceIterator
[
https://issues.apache.org/jira/browse/OAK-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-3878.
-
Bulk close 1.7.11
> Avoid caching of NodeDocument while iterating in BlobReferenceIterator
> --
>
> Key: OAK-3878
> URL: https://issues.apache.org/jira/browse/OAK-3878
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: 1.8, 1.7.11
>
>
> {{BlobReferenceIterator}} in DocumentMK makes use of {{DocumentStore}} API to
> query the NodeDocument. This would cause all those NodeDocuments to be added
> to cache in DocumentStore. Due to this when blob gc is running cache usage
> would not be that effective due to all the associated churn.
> As these NodeDocument are only required for BlobGC logic and its not expected
> that this document would read again soon it would be better to skip caching
> of these documents within DocumentStore
> Similar requirement exist in VersionGC logic but there we use direct store
> based API which does not add such documents to the cache
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6748) Test failure: ExternalPrivateStoreIT.testSyncBigBlob()
[
https://issues.apache.org/jira/browse/OAK-6748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6748.
-
Bulk close 1.7.11
> Test failure: ExternalPrivateStoreIT.testSyncBigBlob()
> --
>
> Key: OAK-6748
> URL: https://issues.apache.org/jira/browse/OAK-6748
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, segment-tar
>Reporter: Hudson
>Assignee: Francesco Mari
> Fix For: 1.8, 1.7.11
>
>
> No description is provided
> The build Jackrabbit Oak #815 has failed.
> First failed run: [Jackrabbit Oak
> #815|https://builds.apache.org/job/Jackrabbit%20Oak/815/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/815/console]
> {noformat}
> Failed tests:
> ExternalPrivateStoreIT>DataStoreTestBase.testSyncBigBlob:237 expected:<{
> root = { ... } }> but was:<{ root : { } }>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6813) DocumentStore conditional remove: reduce set of supported conditions to what the Version GC needs
[ https://issues.apache.org/jira/browse/OAK-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6813. - Bulk close 1.7.11 > DocumentStore conditional remove: reduce set of supported conditions to what > the Version GC needs > - > > Key: OAK-6813 > URL: https://issues.apache.org/jira/browse/OAK-6813 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: documentmk >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.8, 1.7.11 > > Attachments: OAK-6813-simplified.diff, OAK-6813.diff > > > ...and verify in tests that implementations consistently reject other > variants. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6889) Followup on OAK-6755: fix OSGi component descriptors
[ https://issues.apache.org/jira/browse/OAK-6889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6889. - Bulk close 1.7.11 > Followup on OAK-6755: fix OSGi component descriptors > > > Key: OAK-6889 > URL: https://issues.apache.org/jira/browse/OAK-6889 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core, security >Affects Versions: 1.7.9 >Reporter: Julian Sedding >Assignee: Julian Sedding > Fix For: 1.7.11 > > > The fix for OAK-6755 (see also OAK-6741) caused some OSGi metadata to be lost > or otherwise incorrect. > Issues were found using > [osgi-ds-metatype-diff|https://github.com/jsedding/osgi-ds-metatype-diff]. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6888) Flushing the FileStore might return before data is persisted
[
https://issues.apache.org/jira/browse/OAK-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6888.
-
Bulk close 1.7.11
> Flushing the FileStore might return before data is persisted
>
>
> Key: OAK-6888
> URL: https://issues.apache.org/jira/browse/OAK-6888
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
> Fix For: 1.8, 1.7.11
>
> Attachments: failure.txt
>
>
> The implementation of {{FileStore#flush}} might return before all the
> expected data is persisted on disk.
> The root cause of this behaviour is the implementation of
> {{TarRevisions#flush}}, which is too lenient when acquiring the lock for the
> journal file. If a background flush operation is in progress and a user calls
> {{FileStore#flush}}, that method will immediately return because the lock of
> the journal file is already owned by the background flush operation. The
> caller doesn't have the guarantee that everything committed before
> {{FileStore#flush}} is persisted to disk when the method returns.
> A fix for this problem might be to create an additional implementation of
> flush. The current implementation, needed for the background flush thread,
> will not be exposed to the users of {{FileStore}}. The new implementation of
> {{TarRevisions#flush}} should have stricter semantics and always guarantee
> that the persisted head contains everything visible to the user of
> {{FileStore}} before the flush operation was started.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6893) Add BasicWriteTest benchmark
[
https://issues.apache.org/jira/browse/OAK-6893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6893.
-
Bulk close 1.7.11
> Add BasicWriteTest benchmark
>
>
> Key: OAK-6893
> URL: https://issues.apache.org/jira/browse/OAK-6893
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: benchmarks
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Fix For: 1.7.11
>
>
> As discussed at [0], this simple benchmark is all about adding a node of type
> {{nt:folder}} at each iteration (run) with an {{nt:file}} node which in turn
> contains an {{nt:resource}} node. The last node has a binary property of 5MB
> (random content generated every time).
> [0]
> https://lists.apache.org/thread.html/ae6eeb41db1e1a92c8cee0dd8edf4fcbf51d14769cfd71d91dc39f84@%3Coak-dev.jackrabbit.apache.org%3E
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-2382) Move NodeStore implementations to separate modules
[ https://issues.apache.org/jira/browse/OAK-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-2382. - Bulk close 1.7.11 > Move NodeStore implementations to separate modules > -- > > Key: OAK-2382 > URL: https://issues.apache.org/jira/browse/OAK-2382 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: core, documentmk >Reporter: angela > Labels: modularization, technical_debt > Fix For: 1.8, 1.7.11 > > > as discussed in the oak-call yesterday, i think we should take another look > at the modularization of the oak-core module. > some time ago i proposed to move the NodeStore implementations into separate > modules. > to begin with i just tried 2 separate modules: > - oak-ns-document: > everything below oak.plugins.document > - oak-ns-segment: > everything below oak.plugins.segment > segment specific > parts of oak.plugins.backup > i found the following issues: > - org.apache.jackrabbit.oak.plugins.cache is not part of the exported > packages - oak.plugins.backup contains both public API and implementations > without separation - the following test-classes have a hard dependency on one > or more ns implementations: > KernelNodeStoreCacheTest > > ClusterPermissionsTest > NodeStoreFixture to fix those we could need to be > able to run the tests with the individual nodestore modules and move those > tests that are just intended to work with a particular impl. > such a move would not only prevent us from introducing unintended package > dependencies but would also reduce the number of dependencies present with > oak-core. > as discussed yesterday we may want to pick this up again this year. > see also http://markmail.org/message/6cpbyuthub4jxase for the whole > discussion. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6887) Change default value for autoCompact
[
https://issues.apache.org/jira/browse/OAK-6887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6887.
-
Bulk close 1.7.11
> Change default value for autoCompact
>
>
> Key: OAK-6887
> URL: https://issues.apache.org/jira/browse/OAK-6887
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Minor
> Fix For: 1.8, 1.7.11
>
>
> The persistent cache has an option {{autoCompact}} which is related to
> {{compact}}. The former compacts the cache in a background thread, while the
> latter controls whether it should be done on close. OAK-2815 set the default
> for {{compact}} to disabled. Similarly, the default for {{autoCompact}}
> should also be disabled, unless a user wants to use the feature.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6895) Suggest directory lookup (query) isn't closed
[
https://issues.apache.org/jira/browse/OAK-6895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6895.
-
Bulk close 1.7.11
> Suggest directory lookup (query) isn't closed
> -
>
> Key: OAK-6895
> URL: https://issues.apache.org/jira/browse/OAK-6895
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Fix For: 1.8, 1.7.11
>
>
> After OAK-6775, it was observed that we are leaking file handles pointing to
> suggestion directory files.
> This is because {{DefaultIndexReader}} doesn't close suggest directory on
> close.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-2046) Cleaning-up double test artifacts between oak-core and oak-jcr
[ https://issues.apache.org/jira/browse/OAK-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-2046. - Bulk close 1.7.11 > Cleaning-up double test artifacts between oak-core and oak-jcr > -- > > Key: OAK-2046 > URL: https://issues.apache.org/jira/browse/OAK-2046 > Project: Jackrabbit Oak > Issue Type: Task > Components: core, jcr >Reporter: Davide Giannella >Assignee: Davide Giannella >Priority: Minor > Fix For: 1.7.11 > > > On a hurry it happened to copy over a couple of "helpers" from oak-core to > oak-jcr. > Clean up those for avoiding code duplication by using maven dependencies and > classifier. > Full discussion in http://markmail.org/thread/k7qplq4xtuxsvphi -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6876) IndexDisabler should not use NodeBuilder#isReplaced
[
https://issues.apache.org/jira/browse/OAK-6876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6876.
-
Bulk close 1.7.11
> IndexDisabler should not use NodeBuilder#isReplaced
> ---
>
> Key: OAK-6876
> URL: https://issues.apache.org/jira/browse/OAK-6876
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: indexing
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: 1.8, 1.7.11
>
>
> {{IndexDisabler}} currently uses NodeBuilder#isReplaced method to check if
> "disableIndexesOnNextCycle" is set in current flow or not. This is used to
> ensure that disabling is not done in same cycle as the one where reindexing
> was done.
> {noformat}
> //Skip disabling for the cycle where reindexing just got completed
> if (idxBuilder.isReplaced(DISABLE_INDEXES_ON_NEXT_CYCLE)){
> return emptyList();
> }
> {noformat}
> This method though has issues as it would return true
> * If property is only modified. If property is added then it returns false
> * Even if the property is not added new it may return true if base state is
> different object. This happens to be case with SegmentNodeStore and not with
> others
> As a fix we should check explicitly with base state instead of using this api
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6896) Log SegmentStore size at startup
[ https://issues.apache.org/jira/browse/OAK-6896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6896. - Bulk close 1.7.11 > Log SegmentStore size at startup > > > Key: OAK-6896 > URL: https://issues.apache.org/jira/browse/OAK-6896 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Chetan Mehrotra >Assignee: Francesco Mari >Priority: Minor > Labels: production > Fix For: 1.8, 1.7.11 > > > It would be useful if we can log the segmentstore size at time of startup. > FileStore already computes the size to initialize the FileStoreStats so we > just need to log it > This size often help when customer report issues and provide log files -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-5424) Add documentation about revision garbage collection
[ https://issues.apache.org/jira/browse/OAK-5424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-5424. - Bulk close 1.7.11 > Add documentation about revision garbage collection > --- > > Key: OAK-5424 > URL: https://issues.apache.org/jira/browse/OAK-5424 > Project: Jackrabbit Oak > Issue Type: Documentation > Components: documentmk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 1.8, 1.7.11 > > > Add documentation about revision garbage collection to > http://jackrabbit.apache.org/oak/docs/nodestore/documentmk.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6909) FileStore.compact does not persist compacted head to journal
[
https://issues.apache.org/jira/browse/OAK-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6909.
-
Bulk close 1.7.11
> FileStore.compact does not persist compacted head to journal
>
>
> Key: OAK-6909
> URL: https://issues.apache.org/jira/browse/OAK-6909
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Michael Dürig
>Assignee: Michael Dürig
> Labels: compaction, gc
> Fix For: 1.8, 1.7.11
>
>
> When {{FileStore.compact()}} returns the {{journal.log}} does not necessarily
> contain the head created by the compactor. This can lead to problems
> downstream like e.g. in OAK-6894 where the compactor tool wrote the wrong
> (i.e. uncompacted) head to the {{journal.log}}.
> Proposed fix is to call on of the {{FileStore.flush()}} methods after
> compaction and add a test case that verifies the {{journal.log}} contains the
> correct head state.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6859) Schedule Revision GC in DocumentNodeStoreService
[ https://issues.apache.org/jira/browse/OAK-6859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6859. - Bulk close 1.7.11 > Schedule Revision GC in DocumentNodeStoreService > > > Key: OAK-6859 > URL: https://issues.apache.org/jira/browse/OAK-6859 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger > Fix For: 1.8, 1.7.11 > > > Introduce scheduling of the Revision GC task in DocumentNodeStoreService. > There are already other tasks scheduled, like Journal GC and recovery when > another cluster node crashes. > I'd like to enable Continuous Revision GC on MongoDB by default and schedule > Revision GC on RDB once a day at 2 AM. This avoids the need to trigger the GC > externally. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6885) Add missing id field setting in CloudSolrServer
[
https://issues.apache.org/jira/browse/OAK-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6885.
-
Bulk close 1.7.11
> Add missing id field setting in CloudSolrServer
> ---
>
> Key: OAK-6885
> URL: https://issues.apache.org/jira/browse/OAK-6885
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: solr
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 1.7.11
>
>
> {{CloudSolrServer}} doesn't have the _id field_ set with the proper value
> (default _path_exact_ field), this could make SolrCloud routing not work
> efficiently as it should.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6883) The compaction estimator should take the compaction type (tail vs. full) into consideration
[ https://issues.apache.org/jira/browse/OAK-6883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6883. - Bulk close 1.7.11 > The compaction estimator should take the compaction type (tail vs. full) into > consideration > --- > > Key: OAK-6883 > URL: https://issues.apache.org/jira/browse/OAK-6883 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Michael Dürig >Assignee: Francesco Mari >Priority: Critical > Labels: compaction, gc > Fix For: 1.8, 1.7.11 > > > Currently the compaction estimator unconditionally looks at the growth of the > repository since the last compaction run. This turn out to be not optimal > when interleaving tail and full compaction. It would be better to have the > estimator look at the growth of the repository since last full compaction > when running full compaction. > cc [~frm] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6807) Query Recorder
[ https://issues.apache.org/jira/browse/OAK-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6807. - Bulk close 1.7.11 > Query Recorder > -- > > Key: OAK-6807 > URL: https://issues.apache.org/jira/browse/OAK-6807 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Thomas Mueller >Assignee: Thomas Mueller > Fix For: 1.7.11 > > > In order to manage indexes (e.g. find out which indexes are no longer needed, > which properties don't need to be indexed any longer), we have an easy way to > log all executed queries / query plans. > Each entry only needs to be logged once (logging multiple times is OK, but > ensure it's not logged to often). Different log levels can be used (e.g. log > level "TRACE" logs more data, "DEBUG" less). For "DEBUG" level, overhead of > logging should be minimal, so this can be kept enabled for a long time. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-5521) CommunicationObserver and its MBeans need proper synchronization
[
https://issues.apache.org/jira/browse/OAK-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-5521.
-
Bulk close 1.7.11
> CommunicationObserver and its MBeans need proper synchronization
>
>
> Key: OAK-5521
> URL: https://issues.apache.org/jira/browse/OAK-5521
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
> Fix For: 1.8, 1.7.11
>
>
> The {{CommunicationObserver}} used in Cold Standby might be called
> concurrently by multiple threads. The implementation of
> {{CommunicationObserver}} doesn't currently use any form of synchronization
> to protect its state.
> Moreover, the MBeans published by the {{CommunicationObserver}} might be
> concurrently read via JMX and updated via the {{CommunicationObserver}}. As
> such, further synchronization is also needed in the MBeans to protect
> concurrent access to shared data.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6902) Cost estimation for path tranformable queries is incorrect
[
https://issues.apache.org/jira/browse/OAK-6902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6902.
-
Bulk close 1.7.11
> Cost estimation for path tranformable queries is incorrect
> --
>
> Key: OAK-6902
> URL: https://issues.apache.org/jira/browse/OAK-6902
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Fix For: 1.8, 1.7.11
>
>
> OAK-6735 introduced cost calculation based on number of documents indexed per
> term. But, it miscalculates cost as 0 for relative properties which are
> queried on an {{nt:base}} based index while tranforming paths
> e.g. index:
> {noformat}
> + index
> + indexRules/nt:base/properties/foo
> - name = foo
> - propertyIndex = true
> {noformat}
> and query
> {noformat}
> SELECT * FROM [nt:base] WHERE [a/foo] = 'bar'
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6890) Background threads might not be automatically restarted
[
https://issues.apache.org/jira/browse/OAK-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6890.
-
Bulk close 1.7.11
> Background threads might not be automatically restarted
> ---
>
> Key: OAK-6890
> URL: https://issues.apache.org/jira/browse/OAK-6890
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
>Priority: Critical
> Labels: resilience
> Fix For: 1.8, 1.7.11
>
>
> The background threads used in {{FileStore}} are implemented by wrapping
> {{Runnable}} instances in {{SafeRunnable}}, and by handing the
> {{SafeRunnable}} instances over to a {{ScheduledExecutorService}}.
> The documentation of {{ScheduledExecutorService#scheduleAtFixedRate}} states
> that "if any execution of the task encounters an exception, subsequent
> executions are suppressed". But a {{SafeRunnable}} always re-throws any
> {{Throwable}} that it catches, effectively preventing itself from executing
> again in the future.
> There is more than one solution to this problem. One of these is to never
> re-throw any exception. Even if it doesn't always make sense, e.g. in case of
> an {{OutOfMemoryError}}, never re-throwing an exception would better fulfil
> the assumption that background threads should always be up and running even
> in case of error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6874) Segment-Tar-Cold fixture doesn't correctly set up standby blob store
[
https://issues.apache.org/jira/browse/OAK-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6874.
-
Bulk close 1.7.11
> Segment-Tar-Cold fixture doesn't correctly set up standby blob store
>
>
> Key: OAK-6874
> URL: https://issues.apache.org/jira/browse/OAK-6874
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: benchmarks, segment-tar, tarmk-standby
>Affects Versions: 1.7.10
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Minor
> Labels: cold-standby
> Fix For: 1.7.11
>
> Attachments: OAK-6874.patch
>
>
> When {{--shareDataStore}} option is used for {{Segment-Tar-Cold}}, the
> standby instance ends up without a blob store configured.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6894) org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT.offRCUpgradesSegments failing
[
https://issues.apache.org/jira/browse/OAK-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6894.
-
Bulk close 1.7.11
> org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT.offRCUpgradesSegments
> failing
> -
>
> Key: OAK-6894
> URL: https://issues.apache.org/jira/browse/OAK-6894
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Blocker
> Labels: compaction, gc
> Fix For: 1.8, 1.7.11
>
> Attachments:
> TEST-org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT.xml,
> org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT-output.txt,
> org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT.txt
>
>
> {noformat}
> [ERROR]
> offRCUpgradesSegments(org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT)
> Time elapsed: 7.446 s <<< FAILURE!
> java.lang.AssertionError: Segment version mismatch. Expected V_13, found V_12
> expected: but was:
> at
> org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT.checkSegmentVersion(UpgradeIT.java:141)
> at
> org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT.offRCUpgradesSegments(UpgradeIT.java:107)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6908) Change RDB default scheduling on RDB
[ https://issues.apache.org/jira/browse/OAK-6908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6908. - Bulk close 1.7.11 > Change RDB default scheduling on RDB > > > Key: OAK-6908 > URL: https://issues.apache.org/jira/browse/OAK-6908 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 1.8, 1.7.11 > > > The Revision GC schedule on RDB should be changed to disabled. This means the > behaviour on RDB would be the same as in previous releases. The default > schedule on RDB should be re-considered once Continuous RGC is ready on RDB. > At which point it would probably be the same schedule as on MongoDB. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6903) RDB*Store: update Tomcat JDBC pool dependency to 7.0.82
[ https://issues.apache.org/jira/browse/OAK-6903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6903. - Bulk close 1.7.11 > RDB*Store: update Tomcat JDBC pool dependency to 7.0.82 > --- > > Key: OAK-6903 > URL: https://issues.apache.org/jira/browse/OAK-6903 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.8, 1.2.28, 1.0.40, 1.4.19, 1.7.11, 1.6.7 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6796) DataStoreTestBase.testSyncBigBlob failures
[
https://issues.apache.org/jira/browse/OAK-6796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed OAK-6796.
-
Bulk close 1.7.11
> DataStoreTestBase.testSyncBigBlob failures
> --
>
> Key: OAK-6796
> URL: https://issues.apache.org/jira/browse/OAK-6796
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Reporter: Julian Reschke
>Assignee: Francesco Mari
> Fix For: 1.8, 1.7.11
>
> Attachments:
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT-output.txt,
> org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT-output.txt
>
>
> {noformat}
> ExternalPrivateStoreIT>DataStoreTestBase.testSyncBigBlob:237 expected:<{
> root = { ... } }> but was:<{ root : { } }>
> ExternalSharedStoreIT>DataStoreTestBase.testSyncBigBlob:237 expected:<{
> root = { ... } }> but was:<{ root : { } }>
> {noformat}
> fail reliably on my Windows notebook.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6869) oak-http and oak-remote use potentially vulnerable versions of com.fasterxml.jackson
[ https://issues.apache.org/jira/browse/OAK-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6869. - Bulk close 1.7.11 > oak-http and oak-remote use potentially vulnerable versions of > com.fasterxml.jackson > > > Key: OAK-6869 > URL: https://issues.apache.org/jira/browse/OAK-6869 > Project: Jackrabbit Oak > Issue Type: Bug > Components: remoting >Affects Versions: 1.0.39, 1.2.27, 1.4.18, 1.6.5, 1.7.10 >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.8, 1.7.11 > > > See https://github.com/FasterXML/jackson-databind/issues/1599 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6735) Lucene Index: improved cost estimation by using document count per field
[ https://issues.apache.org/jira/browse/OAK-6735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6735. - Bulk close 1.7.11 > Lucene Index: improved cost estimation by using document count per field > > > Key: OAK-6735 > URL: https://issues.apache.org/jira/browse/OAK-6735 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene, query >Affects Versions: 1.7.4 >Reporter: Thomas Mueller >Assignee: Vikas Saurabh > Labels: doc-impacting > Fix For: 1.8, 1.7.11 > > Attachments: IndexReadPattern.txt, LuceneIndexReadPattern.java, > OAK-6735.patch > > > The cost estimation of the Lucene index is somewhat inaccurate because (by > default) it just used the number of documents in the index (as of Oak 1.7.4 > by default, due to OAK-6333). > Instead, it should use the number of documents for the given fields (the > minimum, if there are multiple fields with restrictions). > Plus divided by the number of restrictions (as we do now already). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OAK-6906) RDB*Store: update Tomcat JDBC pool dependency to 8.5.23 (for branches compatible with Java 7)
[ https://issues.apache.org/jira/browse/OAK-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella closed OAK-6906. - Bulk close 1.7.11 > RDB*Store: update Tomcat JDBC pool dependency to 8.5.23 (for branches > compatible with Java 7) > - > > Key: OAK-6906 > URL: https://issues.apache.org/jira/browse/OAK-6906 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.8, 1.4.19, 1.7.11, 1.6.7 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6931) Enable the -Dcache of offline compaction
Michael Dürig created OAK-6931:
--
Summary: Enable the -Dcache of offline compaction
Key: OAK-6931
URL: https://issues.apache.org/jira/browse/OAK-6931
Project: Jackrabbit Oak
Issue Type: Improvement
Components: segment-tar
Affects Versions: 1.6.7
Reporter: Michael Dürig
Assignee: Michael Dürig
Fix For: 1.6.6
The {{-Dcache}} option currently has no effect when used in conjunction with
the {{compact}} run mode of {{oak-run}}. However we should enable users to
configure the segment cache size through this option if necessary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6925) Build Jackrabbit Oak #962 failed
[ https://issues.apache.org/jira/browse/OAK-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249481#comment-16249481 ] Hudson commented on OAK-6925: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #967|https://builds.apache.org/job/Jackrabbit%20Oak/967/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/967/console] > Build Jackrabbit Oak #962 failed > > > Key: OAK-6925 > URL: https://issues.apache.org/jira/browse/OAK-6925 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > Labels: ci, jenkins, test-failure > Fix For: 1.8 > > > No description is provided > The build Jackrabbit Oak #962 has failed. > First failed run: [Jackrabbit Oak > #962|https://builds.apache.org/job/Jackrabbit%20Oak/962/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/962/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6930) TreeUtil.getString(Tree,String,String defaultValue) is not static
[ https://issues.apache.org/jira/browse/OAK-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela resolved OAK-6930. - Resolution: Fixed Fix Version/s: 1.7.12 1.8 Committed revision 1815082. > TreeUtil.getString(Tree,String,String defaultValue) is not static > - > > Key: OAK-6930 > URL: https://issues.apache.org/jira/browse/OAK-6930 > Project: Jackrabbit Oak > Issue Type: Bug > Components: security-spi >Reporter: angela >Assignee: angela >Priority: Minor > Fix For: 1.8, 1.7.12 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6925) Build Jackrabbit Oak #962 failed
[ https://issues.apache.org/jira/browse/OAK-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249375#comment-16249375 ] Hudson commented on OAK-6925: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #966|https://builds.apache.org/job/Jackrabbit%20Oak/966/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/966/console] > Build Jackrabbit Oak #962 failed > > > Key: OAK-6925 > URL: https://issues.apache.org/jira/browse/OAK-6925 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > Labels: ci, jenkins, test-failure > Fix For: 1.8 > > > No description is provided > The build Jackrabbit Oak #962 has failed. > First failed run: [Jackrabbit Oak > #962|https://builds.apache.org/job/Jackrabbit%20Oak/962/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/962/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6930) TreeUtil.getString(Tree,String,String defaultValue) is not static
angela created OAK-6930: --- Summary: TreeUtil.getString(Tree,String,String defaultValue) is not static Key: OAK-6930 URL: https://issues.apache.org/jira/browse/OAK-6930 Project: Jackrabbit Oak Issue Type: Bug Components: security-spi Reporter: angela Assignee: angela Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6929) Enforce minimal test-coverage with oak-core
[ https://issues.apache.org/jira/browse/OAK-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela resolved OAK-6929. - Resolution: Fixed Fix Version/s: 1.7.12 1.8 Committed revision 1815074. > Enforce minimal test-coverage with oak-core > --- > > Key: OAK-6929 > URL: https://issues.apache.org/jira/browse/OAK-6929 > Project: Jackrabbit Oak > Issue Type: Task > Components: core >Reporter: angela >Assignee: angela >Priority: Trivial > Fix For: 1.8, 1.7.12 > > > similar to other modules i would like to enforce keeping the minimal > test-coverage we are having with oak-core. it currently is 77% (with java 1.8) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6929) Enforce minimal test-coverage with oak-core
[ https://issues.apache.org/jira/browse/OAK-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-6929: Summary: Enforce minimal test-coverage with oak-core (was: Add test for minimal test-coverage with oak-core) > Enforce minimal test-coverage with oak-core > --- > > Key: OAK-6929 > URL: https://issues.apache.org/jira/browse/OAK-6929 > Project: Jackrabbit Oak > Issue Type: Task > Components: core >Reporter: angela >Assignee: angela >Priority: Trivial > > similar to other modules i would like to enforce keeping the minimal > test-coverage we are having with oak-core. it currently is 77% (with java 1.8) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6929) Add test for minimal test-coverage with oak-core
angela created OAK-6929: --- Summary: Add test for minimal test-coverage with oak-core Key: OAK-6929 URL: https://issues.apache.org/jira/browse/OAK-6929 Project: Jackrabbit Oak Issue Type: Task Components: core Reporter: angela Assignee: angela Priority: Trivial similar to other modules i would like to enforce keeping the minimal test-coverage we are having with oak-core. it currently is 77% (with java 1.8) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6088) org.apache.jackrabbit.oak.management.ManagementOperation should use TimeDurationFormatter
[ https://issues.apache.org/jira/browse/OAK-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig resolved OAK-6088. Resolution: Fixed Fix Version/s: 1.7.12 Fixed at http://svn.apache.org/viewvc?rev=1815065&view=rev > org.apache.jackrabbit.oak.management.ManagementOperation should use > TimeDurationFormatter > - > > Key: OAK-6088 > URL: https://issues.apache.org/jira/browse/OAK-6088 > Project: Jackrabbit Oak > Issue Type: Task > Components: core >Reporter: Julian Reschke >Assignee: Michael Dürig >Priority: Minor > Labels: technical_debt > Fix For: 1.8, 1.7.12 > > > See OAK-6020. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6928) RootFactory: deprecated method createSystemRoot lost during to m12n effort
[
https://issues.apache.org/jira/browse/OAK-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249306#comment-16249306
]
Alex Deparvu commented on OAK-6928:
---
good catch Angela!
> RootFactory: deprecated method createSystemRoot lost during to m12n effort
> --
>
> Key: OAK-6928
> URL: https://issues.apache.org/jira/browse/OAK-6928
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
>Reporter: angela
>Assignee: angela
>Priority: Trivial
> Fix For: 1.8, 1.7.12
>
>
> when we introduced the copy of {{RootFactory}} we didn't copy over the
> deprecated flavor of {{createSystemRoot}} that takes
> {{QueryEngineSettings}}. Since we ended up removing the original class
> altogether for the m12n effort, we should have the deprecated method on the
> copy.
> [~stillalex] fyi
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OAK-6928) RootFactory: deprecated method createSystemRoot lost during to m12n effort
[
https://issues.apache.org/jira/browse/OAK-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved OAK-6928.
-
Resolution: Fixed
Fix Version/s: 1.7.12
1.8
Committed revision 1815064.
> RootFactory: deprecated method createSystemRoot lost during to m12n effort
> --
>
> Key: OAK-6928
> URL: https://issues.apache.org/jira/browse/OAK-6928
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
>Reporter: angela
>Assignee: angela
>Priority: Trivial
> Fix For: 1.8, 1.7.12
>
>
> when we introduced the copy of {{RootFactory}} we didn't copy over the
> deprecated flavor of {{createSystemRoot}} that takes
> {{QueryEngineSettings}}. Since we ended up removing the original class
> altogether for the m12n effort, we should have the deprecated method on the
> copy.
> [~stillalex] fyi
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6928) RootFactory: deprecated method createSystemRoot lost during to m12n effort
angela created OAK-6928:
---
Summary: RootFactory: deprecated method createSystemRoot lost
during to m12n effort
Key: OAK-6928
URL: https://issues.apache.org/jira/browse/OAK-6928
Project: Jackrabbit Oak
Issue Type: Bug
Components: core
Reporter: angela
Assignee: angela
Priority: Trivial
when we introduced the copy of {{RootFactory}} we didn't copy over the
deprecated flavor of {{createSystemRoot}} that takes {{QueryEngineSettings}}.
Since we ended up removing the original class altogether for the m12n effort,
we should have the deprecated method on the copy.
[~stillalex] fyi
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6387) Building an index (new index + reindex): temporarily store blob references
[ https://issues.apache.org/jira/browse/OAK-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249269#comment-16249269 ] Thomas Mueller commented on OAK-6387: - Now that we have indexing via oak-run, I think this issue is less important to fix. > Building an index (new index + reindex): temporarily store blob references > -- > > Key: OAK-6387 > URL: https://issues.apache.org/jira/browse/OAK-6387 > Project: Jackrabbit Oak > Issue Type: Bug > Components: lucene, query >Reporter: Thomas Mueller > Fix For: 1.9 > > > If reindexing a Lucene index takes multiple days, and if datastore garbage > collection (DSGC) is run during that time, then DSGC may remove binaries of > that index because they are not referenced. > It would be good if all binaries that are needed, and that are older than > (for example) one hour, are referenced during reindexing (for example in a > temporary location). So that DSGC will not remove them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6387) Building an index (new index + reindex): temporarily store blob references
[ https://issues.apache.org/jira/browse/OAK-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-6387: Fix Version/s: (was: 1.8) 1.9 > Building an index (new index + reindex): temporarily store blob references > -- > > Key: OAK-6387 > URL: https://issues.apache.org/jira/browse/OAK-6387 > Project: Jackrabbit Oak > Issue Type: Bug > Components: lucene, query >Reporter: Thomas Mueller > Fix For: 1.9 > > > If reindexing a Lucene index takes multiple days, and if datastore garbage > collection (DSGC) is run during that time, then DSGC may remove binaries of > that index because they are not referenced. > It would be good if all binaries that are needed, and that are older than > (for example) one hour, are referenced during reindexing (for example in a > temporary location). So that DSGC will not remove them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OAK-6342) Cost overrides for Lucene index not always working
[
https://issues.apache.org/jira/browse/OAK-6342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller reassigned OAK-6342:
---
Assignee: Thomas Mueller
> Cost overrides for Lucene index not always working
> --
>
> Key: OAK-6342
> URL: https://issues.apache.org/jira/browse/OAK-6342
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene, query
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
> Fix For: 1.8
>
>
> The cost overrides for the Lucene (compatVersion 2) index don't seem to work
> always. All features (costPerEntry, costPerExecution, entryCount which is
> undocumented) seem to be ignored for the query:
> {noformat}
> /jcr:root/replication//*[jcr:like(@sling:resourceType, "replication//%agent")]
> index rule:
> http://localhost:4502/oak:index/lucene/indexRules/nt:base/properties/resourceType.tidy.-1.json
> {
> "jcr:primaryType": "nt:unstructured",
> "propertyIndex": "true",
> "weight": "0",
> "name": "sling:resourceType"
> }
> cost for lucene-property[/oak:index/lucene] is 501.0
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6148) Warning if there are many Lucene documents
[ https://issues.apache.org/jira/browse/OAK-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-6148: Fix Version/s: (was: 1.8) 1.9 > Warning if there are many Lucene documents > -- > > Key: OAK-6148 > URL: https://issues.apache.org/jira/browse/OAK-6148 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene, query >Reporter: Thomas Mueller > Labels: candidate_oak_1_6 > Fix For: 1.9 > > > Lucene indexes are limited to Integer.MAX_VALUE (LUCENE-4104), so Lucene > indexes can have at most around 2 billion nodes indexed. > We should avoid running into this limit. For example, we could log a warning > if the number of documents is a multiple of 200 million, so a user has plenty > of time to change the index configuration. > Also, it would be good to be able to read the current number of documents per > index (using JMX for example), so that one can find out how far he is from > the limit. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-4934) Query shapes for JCR Query
[
https://issues.apache.org/jira/browse/OAK-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249267#comment-16249267
]
Thomas Mueller commented on OAK-4934:
-
[~chetanm] I have implemented this in the "query recorder", OAK-6807. Anything
else needed?
> Query shapes for JCR Query
> --
>
> Key: OAK-4934
> URL: https://issues.apache.org/jira/browse/OAK-4934
> Project: Jackrabbit Oak
> Issue Type: Wish
> Components: query
>Reporter: Chetan Mehrotra
> Fix For: 1.8
>
>
> For certain requirements it would be good to have a notion/support to deduce
> query shape [1]
> {quote}
> A combination of query predicate, sort, and projection specifications.
> For the query predicate, only the structure of the predicate, including the
> field names, are significant; the values in the query predicate are
> insignificant. As such, a query predicate \{ type: 'food' \} is equivalent to
> the query predicate \{ type: 'utensil' \} for a query shape.
> {quote}
> So transforming that to Oak the shape should represent a JCR-SQL2 query
> string (xpath query gets transformed to SQL2) which is a *canonical*
> representation of actual query ignoring the property restriction values.
> Example we have 2 queries
> * SELECT * FROM [app:Asset] AS a WHERE a.[jcr:content/metadata/status] =
> 'published'
> * SELECT * FROM [app:Asset] AS a WHERE a.[jcr:content/metadata/status] =
> 'disabled'
> The query shape would be
> SELECT * FROM [app:Asset] AS a WHERE a.[jcr:content/metadata/status] = 'A'.
> The plan for query having given shape would remain same irrespective of value
> of property restrictions. Path restriction can cause some difference though
> The shape can then be used for
> * Stats Collection - Currently stats collection gets overflown if same query
> with different value gets invoked
> * Allow configuring hints - See support in Mongo [2] for an example. One
> specify via config that for a query of such and such shape this index should
> be used
> * Less noisy diagnostics - If a query gets invoked with bad plan the QE can
> log the warning once instead of logging it for each query invocation
> involving different values.
> [1] https://docs.mongodb.com/manual/reference/glossary/#term-query-shape
> [2] https://docs.mongodb.com/manual/reference/command/planCacheSetFilter/
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5858) Lucene index may return the wrong result if path is excluded
[
https://issues.apache.org/jira/browse/OAK-5858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated OAK-5858:
Fix Version/s: (was: 1.8)
1.9
> Lucene index may return the wrong result if path is excluded
>
>
> Key: OAK-5858
> URL: https://issues.apache.org/jira/browse/OAK-5858
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
>Reporter: Thomas Mueller
> Fix For: 1.9
>
>
> If a query uses a Lucene index that has "excludedPaths", the query result may
> be wrong (not contain all matching nodes). This is case even if there is a
> property index available for the queried property. Example:
> {noformat}
> Indexes:
> /oak:index/resourceType/type = "property"
> /oak:index/lucene/type = "lucene"
> /oak:index/lucene/excludedPaths = ["/etc"]
> /oak:index/lucene/indexRules/nt:base/properties/resourceType
> Query:
> /jcr:root/etc//*[jcr:like(@resourceType, "x%y")]
> Index cost:
> cost for /oak:index/resourceType is 1602.0
> cost for /oak:index/lucene is 1001.0
> Result:
> (empty)
> Expected result:
> /etc/a
> /etc/b
> {noformat}
> Here, the lucene index is picked, even thought the query explicitly queries
> for /etc, and the lucene index has this path excluded.
> I think the lucene index should not be picked in case the index does not
> match the query path.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-5159) Killing the process may stop async index update to to 30 minutes, for DocumentStore (MongoDB, RDB)
[ https://issues.apache.org/jira/browse/OAK-5159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249263#comment-16249263 ] Thomas Mueller commented on OAK-5159: - [~chetanm] I think this only affects "async" indexes that are not "nrt", right? So basically only the counter index. In this case, I guess we can resolve it as won't fix, or at least move it to 1.9. > Killing the process may stop async index update to to 30 minutes, for > DocumentStore (MongoDB, RDB) > -- > > Key: OAK-5159 > URL: https://issues.apache.org/jira/browse/OAK-5159 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Thomas Mueller > Labels: resilience > Fix For: 1.8 > > > Same as OAK-2108, when using a DocumentStore based repository (MongoDB, > RDBMK). This is also a problem in the single-cluster-node case, not just when > using multiple cluster node. > When killing a node that is running the sync index update, then this async > index update will not run for up to 15 minutes, because the lease time is set > to 15 minutes. > We could probably use Oak / Sling Discovery to improve the situation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5950) XPath: stack overflow for large combination of "or" and "and"
[
https://issues.apache.org/jira/browse/OAK-5950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated OAK-5950:
Fix Version/s: (was: 1.8)
1.9
> XPath: stack overflow for large combination of "or" and "and"
> -
>
> Key: OAK-5950
> URL: https://issues.apache.org/jira/browse/OAK-5950
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
>Reporter: Thomas Mueller
>Priority: Critical
> Fix For: 1.9
>
>
> The following query returns in a stack overflow:
> {noformat}
> xpath2sql /jcr:root/home//element(*,rep:Authorizable)[(@a1=1 or @a2=1 or
> @a3=1 or @a4=1 or @a5=1 or @a6=1 or @a7=1 or @a8=1)
> and (@b1=1 or @b2=1 or @b3=1 or @b4=1 or @b5=1 or @b6=1 or @b7=1 or @b8=1)
> and (@c1=1 or @c2=1 or @c3=1 or @c4=1 or @c5=1 or @c6=1 or @c7=1 or @c8=1)
> and (@d1=1 or @d2=1 or @d3=1 or @d4=1 or @d5=1 or @d6=1 or @d7=1 or @d8=1)]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5214) Create FAQ for External Authentication
[ https://issues.apache.org/jira/browse/OAK-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-5214: Fix Version/s: (was: 1.8) > Create FAQ for External Authentication > -- > > Key: OAK-5214 > URL: https://issues.apache.org/jira/browse/OAK-5214 > Project: Jackrabbit Oak > Issue Type: Documentation > Components: auth-external, doc >Reporter: Alex COLLIGNON >Assignee: angela >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-2437) 'shallow' access to a node and it's properties
[ https://issues.apache.org/jira/browse/OAK-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-2437: Fix Version/s: (was: 1.8) > 'shallow' access to a node and it's properties > -- > > Key: OAK-2437 > URL: https://issues.apache.org/jira/browse/OAK-2437 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Armand Planche >Assignee: angela > > in many cases it would be helpful to be able to restrict an access control > entry as 'shallow', so affecting only the corresponding node and it's > properties but not the subnodes (and their properties). > With the empty string glob restriction it's possible to restrict to a node > only, but the properties are not included in this case... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5685) CLONE - Tool to detect permission store inconsistencies
[ https://issues.apache.org/jira/browse/OAK-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-5685: Fix Version/s: (was: 1.3.9) (was: 1.4) > CLONE - Tool to detect permission store inconsistencies > --- > > Key: OAK-5685 > URL: https://issues.apache.org/jira/browse/OAK-5685 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: core >Reporter: Michael Marth >Assignee: angela >Priority: Minor > Labels: production, resilience, tools > > I think we should prepare for cases where the permission store (managed as a > tree mirrored to the content tree) goes out of sync with the content tree for > whatever reason. > Ideally, that would be an online tool (maybe exposed via JMX) that goes back > the MVCC revisions to find the offending commit (so that have a chance to > reduce the number of such occurences) and fixes the inconsistency on head. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5880) Test in oak-pojosr module should rely on service events instead of sleeps
[
https://issues.apache.org/jira/browse/OAK-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-5880:
Fix Version/s: (was: 1.8)
> Test in oak-pojosr module should rely on service events instead of sleeps
> -
>
> Key: OAK-5880
> URL: https://issues.apache.org/jira/browse/OAK-5880
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: pojosr
>Affects Versions: 1.6.1
>Reporter: Julian Sedding
>Assignee: angela
>Priority: Minor
>
> Some tests in {{oak-pojosr}} rely on service events happening "soon enough"
> for assertions to hold. OAK-5750 introduced a mechanism to wait for service
> events before continuing execution
> (AbstractRepositoryFactoryTest#awaitServiceEvent), which should be leveraged
> in such cases.
> All tests in the module should be reviewed and adjusted if necessary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5520) Improve index and query documentation
[ https://issues.apache.org/jira/browse/OAK-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-5520: Fix Version/s: (was: 1.8) 1.9 > Improve index and query documentation > - > > Key: OAK-5520 > URL: https://issues.apache.org/jira/browse/OAK-5520 > Project: Jackrabbit Oak > Issue Type: Documentation > Components: lucene, query >Reporter: Thomas Mueller >Assignee: Thomas Mueller > Fix For: 1.9 > > > The Oak index and query documentation needs to be improved: > * step-by-step descriptions of how to fix problems (for example from slow > queries to fast queries) > * checklists > * index corruption vs merely _perceive_ corruption > * checkpoints > * text extraction > * link to tools, such as the Oak Lucene Index Definition Generator at > http://oakutils.appspot.com/generate/index > * indexing and reindex: when it is needed and how to do it, how long does it > take, how to stop > * document currently undocumented features (for example Lucene index, > notNullCheckEnabled) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6217) Document tricky statements
[
https://issues.apache.org/jira/browse/OAK-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated OAK-6217:
Fix Version/s: (was: 1.8)
1.9
> Document tricky statements
> --
>
> Key: OAK-6217
> URL: https://issues.apache.org/jira/browse/OAK-6217
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
> Fix For: 1.9
>
>
> There are some cases, specially if fulltext conditions and aggregation are
> used, where a query sometimes returns no results even thought with the right
> index it does return the results. This is a bit hard to understand, because
> it doesn't match the rule "indexes should only affect performance, not
> results". One such example is if a query uses one or the other index, but not
> both. Or if a query uses fulltext conditions on different nodes (parent and
> child). Examples:
> {noformat}
> /jcr:root/home//element(*, rep:User)
> [jcr:contains(.,'Kerr*')
> and jcr:like(@rep:impersonators, '%ccibu%')]/profile
> /jcr:root/home//element(*, rep:User)
> [jcr:contains(profile,'Kerr*')
> and jcr:like(@rep:impersonators, '%ccibu%')]/profile
> {noformat}
> Related is the usage of relative properties in indexes, excluded / included
> paths.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5917) Document enhancements in indexing in 1.6
[ https://issues.apache.org/jira/browse/OAK-5917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-5917: Fix Version/s: (was: 1.8) 1.9 > Document enhancements in indexing in 1.6 > > > Key: OAK-5917 > URL: https://issues.apache.org/jira/browse/OAK-5917 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: doc >Reporter: Chetan Mehrotra >Assignee: Thomas Mueller > Fix For: 1.9 > > > This task is meant to collect and refer work done in 1.6 release which needs > to be documented in Oak docs. > Issues in lucene and query area > [jql|https://issues.apache.org/jira/issues/?jql=project%20%3D%20OAK%20AND%20fixVersion%20%3D%201.6.0%20and%20component%20in%20(lucene%2C%20query)%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC] > Topics to cover > * OAK-4412 - Lucene Hybrid Index (/) > * OAK-4939 - Isolation of corrupted index (/) > * OAK-4974 - Enable configuring QueryEngineSettings via OSGi config > * OAK-3574 - Function based indexes > * OAK-4400 - Correlate index with the index definition used to build it (/) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6381) Improved index analysis tools
[ https://issues.apache.org/jira/browse/OAK-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-6381: Sprint: L15 > Improved index analysis tools > - > > Key: OAK-6381 > URL: https://issues.apache.org/jira/browse/OAK-6381 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Thomas Mueller >Assignee: Thomas Mueller > Fix For: 1.8 > > > It would be good to have more tools to analyze indexes: > * For Lucene indexes, get a histogram of samples (terms). We have > "getFieldInfo", which shows which fields are how common, but we don't have > terms. For example the /oak:index/lucene index contains 1 million fulltext > fields and node names for 1 million nodes, but I wonder why, and what typical > nodes names are, and maybe fulltext for most nodes is actually empty. Maybe a > new method "getTermHistogram(int sampleCount)" or similar > * For property indexes, number of updated nodes per second or so. Right now > we can just analyze the counts per key, but some indexes / keys are very > volatile (see many short lived entries) > * For Lucene indexes, writes per second or so (in MB). > * How indexes are used (approximate read nodes / MB per hours) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6915) Minimize the amount of uncached segment reads
[
https://issues.apache.org/jira/browse/OAK-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249258#comment-16249258
]
Francesco Mari commented on OAK-6915:
-
I could have a look at the patch just now. The patch looks good to me, and the
comment is clear and explanatory.
> Minimize the amount of uncached segment reads
> -
>
> Key: OAK-6915
> URL: https://issues.apache.org/jira/browse/OAK-6915
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
>Reporter: Francesco Mari
>Assignee: Francesco Mari
> Fix For: 1.8, 1.7.12
>
> Attachments: OAK-6915-01.patch, OAK-6915-02.patch, OAK-6915-03.patch,
> OAK-6915-04.patch, OAK-6915-05.patch, OAK-6915-diagnostics-02.patch,
> OAK-6915-diagnostics.patch, OAK-6915.patch, Screen Shot 2017-11-09 at
> 14.14.28.png, Screen Shot 2017-11-09 at 14.16.59.png
>
>
> The current implementation of {{SegmentCache}} should make better use of the
> underlying Guava cache by relying on the cached segments instead of
> unconditionally performing an uncached segment read via the
> {{Callable}} passed to {{SegmentCache#getSegment}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6381) Improved index analysis tools
[ https://issues.apache.org/jira/browse/OAK-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249257#comment-16249257 ] Thomas Mueller commented on OAK-6381: - It would be good to add a "getFieldTerms" with a term prefix. > Improved index analysis tools > - > > Key: OAK-6381 > URL: https://issues.apache.org/jira/browse/OAK-6381 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Thomas Mueller >Assignee: Thomas Mueller > Fix For: 1.8 > > > It would be good to have more tools to analyze indexes: > * For Lucene indexes, get a histogram of samples (terms). We have > "getFieldInfo", which shows which fields are how common, but we don't have > terms. For example the /oak:index/lucene index contains 1 million fulltext > fields and node names for 1 million nodes, but I wonder why, and what typical > nodes names are, and maybe fulltext for most nodes is actually empty. Maybe a > new method "getTermHistogram(int sampleCount)" or similar > * For property indexes, number of updated nodes per second or so. Right now > we can just analyze the counts per key, but some indexes / keys are very > volatile (see many short lived entries) > * For Lucene indexes, writes per second or so (in MB). > * How indexes are used (approximate read nodes / MB per hours) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6309) Not always convert XPath "primaryType in a, b" to union
[
https://issues.apache.org/jira/browse/OAK-6309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated OAK-6309:
Fix Version/s: (was: 1.8)
1.9
> Not always convert XPath "primaryType in a, b" to union
> ---
>
> Key: OAK-6309
> URL: https://issues.apache.org/jira/browse/OAK-6309
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Critical
> Fix For: 1.9
>
>
> Currently, queries with multiple primary types are always converted to a
> "union", but this is not alway the best solution. The main problem is that
> results are not sorted by score as expected. Example:
> {noformat}
> /jcr:root/content//element(*, nt:hierarchyNode)[jcr:contains(., 'abc)
> and (@jcr:primaryType = 'acme:Page' or @jcr:primaryType = 'acme:Asset')]
> {noformat}
> This is currently converted to a union, even if the same index is used for
> buth subqueries (assuming there is an index on nt:hierarchyNode).
> A workaround is to use:
> {noformat}
> /jcr:root/content//element(*, nt:hierarchyNode)[jcr:contains(., 'abc)
> and (./@jcr:primaryType = 'acme:Page' or ./@jcr:primaryType = 'acme:Asset')]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6303) Cache in CachingBlobStore might grow beyond configured limit
[
https://issues.apache.org/jira/browse/OAK-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated OAK-6303:
Fix Version/s: (was: 1.8)
1.9
> Cache in CachingBlobStore might grow beyond configured limit
>
>
> Key: OAK-6303
> URL: https://issues.apache.org/jira/browse/OAK-6303
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: blob, core
>Reporter: Julian Reschke
>Assignee: Thomas Mueller
> Fix For: 1.9
>
> Attachments: OAK-6303-test.diff, OAK-6303.diff
>
>
> It appears that depending on actual cache entry sizes, the {{CacheLIRS}}
> might grow beyond the configured limit.
> For {{RDBBlobStore}}, the limit is currently configured to 16MB, yet storing
> random 2M entries appears to fill the cache with 64MB of data (according to
> it's own stats).
> The attached test case reproduces this.
> (it seems this is caused by the fact that each of the 16 segments of the
> cache can hold 2 entries, no matter how big they are...)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6261) Log queries that sort by un-indexed properties
[ https://issues.apache.org/jira/browse/OAK-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-6261: Fix Version/s: (was: 1.8) 1.9 > Log queries that sort by un-indexed properties > -- > > Key: OAK-6261 > URL: https://issues.apache.org/jira/browse/OAK-6261 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Thomas Mueller >Assignee: Thomas Mueller >Priority: Minor > Fix For: 1.9 > > > Queries that can read many nodes, and sort by properties that are not > indexed, can be very slow. This includes for example fulltext queries. > As a start, it might make sense to log an "info" level message (but avoid > logging the same message each time a query is run). Per configuration, this > could be turned to "warning". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6076) Ensure tracking of slow queries includes the full execution time including getting result nodes
[ https://issues.apache.org/jira/browse/OAK-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-6076: Fix Version/s: 1.7.6 > Ensure tracking of slow queries includes the full execution time including > getting result nodes > --- > > Key: OAK-6076 > URL: https://issues.apache.org/jira/browse/OAK-6076 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Tom Blackford >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.6 > > > At present the query durations shown in the Oak Query Statistics do not > include the full execution time to provide the results of the query (IIUC the > include only the initial Query Execution time and not the time to get the > resulting nodes). Often the latter time is far higher and as such, many slow > and troublesome queries are not really shown in the QueryStats Slow Queries. > cc [~chetanm] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6076) Ensure tracking of slow queries includes the full execution time including getting result nodes
[ https://issues.apache.org/jira/browse/OAK-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved OAK-6076. - Resolution: Duplicate > Ensure tracking of slow queries includes the full execution time including > getting result nodes > --- > > Key: OAK-6076 > URL: https://issues.apache.org/jira/browse/OAK-6076 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Reporter: Tom Blackford >Assignee: Thomas Mueller > Fix For: 1.8 > > > At present the query durations shown in the Oak Query Statistics do not > include the full execution time to provide the results of the query (IIUC the > include only the initial Query Execution time and not the time to get the > resulting nodes). Often the latter time is far higher and as such, many slow > and troublesome queries are not really shown in the QueryStats Slow Queries. > cc [~chetanm] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5782) Test failure: persistentCache.BroadcastTest.broadcastTCP
[ https://issues.apache.org/jira/browse/OAK-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-5782: Fix Version/s: (was: 1.8) 1.9 > Test failure: persistentCache.BroadcastTest.broadcastTCP > - > > Key: OAK-5782 > URL: https://issues.apache.org/jira/browse/OAK-5782 > Project: Jackrabbit Oak > Issue Type: Bug > Components: cache, continuous integration, core >Affects Versions: 1.6.0 >Reporter: Hudson >Assignee: Thomas Mueller > Labels: test-failure, ubuntu > Fix For: 1.9 > > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1447 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting > #1447|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1447/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1447/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-5782) Test failure: persistentCache.BroadcastTest.broadcastTCP
[ https://issues.apache.org/jira/browse/OAK-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249254#comment-16249254 ] Thomas Mueller commented on OAK-5782: - Maybe just disable the test and deprecate the feature. > Test failure: persistentCache.BroadcastTest.broadcastTCP > - > > Key: OAK-5782 > URL: https://issues.apache.org/jira/browse/OAK-5782 > Project: Jackrabbit Oak > Issue Type: Bug > Components: cache, continuous integration, core >Affects Versions: 1.6.0 >Reporter: Hudson >Assignee: Thomas Mueller > Labels: test-failure, ubuntu > Fix For: 1.9 > > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1447 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting > #1447|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1447/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1447/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5706) Function based indexes with "like" conditions
[
https://issues.apache.org/jira/browse/OAK-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated OAK-5706:
Fix Version/s: (was: 1.8)
1.9
> Function based indexes with "like" conditions
> -
>
> Key: OAK-5706
> URL: https://issues.apache.org/jira/browse/OAK-5706
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: indexing
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
> Fix For: 1.9
>
>
> Currently, a function-based index is not used when using "like" conditions,
> as follows:
> {noformat}
> /jcr:root//*[jcr:like(fn:lower-case(fn:name()), 'abc%')]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
