[jira] [Updated] (OAK-7218) Build Jackrabbit Oak #1210 failed
[
https://issues.apache.org/jira/browse/OAK-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-7218:
--
Description:
No description is provided
The build Jackrabbit Oak #1210 has failed.
First failed run: [Jackrabbit Oak
#1210|https://builds.apache.org/job/Jackrabbit%20Oak/1210/] [console
log|https://builds.apache.org/job/Jackrabbit%20Oak/1210/console]
{noformat}
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running org.apache.jackrabbit.oak.segment.standby.BrokenNetworkIT
[INFO] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 102.22
s - in org.apache.jackrabbit.oak.segment.standby.BrokenNetworkIT
[INFO] Running org.apache.jackrabbit.oak.segment.standby.StandbyTestIT
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 87.75 s
- in org.apache.jackrabbit.oak.segment.standby.StandbyTestIT
[INFO] Running org.apache.jackrabbit.oak.segment.standby.FailoverIPRangeIT
[INFO] Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 62.121
s - in org.apache.jackrabbit.oak.segment.standby.FailoverIPRangeIT
[INFO] Running org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT
[ERROR] Tests run: 12, Failures: 0, Errors: 1, Skipped: 1, Time elapsed:
122.881 s <<< FAILURE! - in
org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT
[ERROR]
testSyncBigBlob(org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT)
Time elapsed: 37.303 s <<< ERROR!
java.io.IOException: org.apache.jackrabbit.core.data.DataStoreException: Could
not add record
Caused by: org.apache.jackrabbit.core.data.DataStoreException: Could not add
record
Caused by: java.io.IOException: No space left on device
{noformat}
was:
No description is provided
The build Jackrabbit Oak #1210 has failed.
First failed run: [Jackrabbit Oak
#1210|https://builds.apache.org/job/Jackrabbit%20Oak/1210/] [console
log|https://builds.apache.org/job/Jackrabbit%20Oak/1210/console]
> Build Jackrabbit Oak #1210 failed
> -
>
> Key: OAK-7218
> URL: https://issues.apache.org/jira/browse/OAK-7218
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1210 has failed.
> First failed run: [Jackrabbit Oak
> #1210|https://builds.apache.org/job/Jackrabbit%20Oak/1210/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1210/console]
> {noformat}
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.jackrabbit.oak.segment.standby.BrokenNetworkIT
> [INFO] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> 102.22 s - in org.apache.jackrabbit.oak.segment.standby.BrokenNetworkIT
> [INFO] Running org.apache.jackrabbit.oak.segment.standby.StandbyTestIT
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 87.75
> s - in org.apache.jackrabbit.oak.segment.standby.StandbyTestIT
> [INFO] Running org.apache.jackrabbit.oak.segment.standby.FailoverIPRangeIT
> [INFO] Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> 62.121 s - in org.apache.jackrabbit.oak.segment.standby.FailoverIPRangeIT
> [INFO] Running
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT
> [ERROR] Tests run: 12, Failures: 0, Errors: 1, Skipped: 1, Time elapsed:
> 122.881 s <<< FAILURE! - in
> org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT
> [ERROR]
> testSyncBigBlob(org.apache.jackrabbit.oak.segment.standby.ExternalPrivateStoreIT)
> Time elapsed: 37.303 s <<< ERROR!
> java.io.IOException: org.apache.jackrabbit.core.data.DataStoreException:
> Could not add record
> Caused by: org.apache.jackrabbit.core.data.DataStoreException: Could not add
> record
> Caused by: java.io.IOException: No space left on device
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (OAK-7218) Build Jackrabbit Oak #1210 failed
[ https://issues.apache.org/jira/browse/OAK-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger closed OAK-7218. - > Build Jackrabbit Oak #1210 failed > - > > Key: OAK-7218 > URL: https://issues.apache.org/jira/browse/OAK-7218 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1210 has failed. > First failed run: [Jackrabbit Oak > #1210|https://builds.apache.org/job/Jackrabbit%20Oak/1210/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1210/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7218) Build Jackrabbit Oak #1210 failed
[ https://issues.apache.org/jira/browse/OAK-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-7218. --- Resolution: Duplicate > Build Jackrabbit Oak #1210 failed > - > > Key: OAK-7218 > URL: https://issues.apache.org/jira/browse/OAK-7218 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1210 has failed. > First failed run: [Jackrabbit Oak > #1210|https://builds.apache.org/job/Jackrabbit%20Oak/1210/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1210/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OAK-4401) Excerpt Highlighting for a property is not correct
[ https://issues.apache.org/jira/browse/OAK-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330663#comment-16330663 ] Vikas Saurabh edited comment on OAK-4401 at 1/30/18 12:27 AM: -- Updated earlier impl in trunk at [r1821516|https://svn.apache.org/r1821516]. Backported to 1.8 branch in [r1821521|https://svn.apache.org/r1821521]. Backported to 1.6 branch in [r1822592|https://svn.apache.org/r1822592]. Backported to 1.4 branch in [r1822593|https://svn.apache.org/r1822593]. Backported to 1.2 branch in [r1822594|https://svn.apache.org/r1822594]. So, trunk ([r1821325|https://svn.apache.org/r1821325], [r1821516|https://svn.apache.org/r1821516]), 1.8 ([r1821521|https://svn.apache.org/r1821521], 1.6 ([r1822592|https://svn.apache.org/r1822592]), 1.4 ([r1822593|https://svn.apache.org/r1822593]), 1.2 ([r1822594|https://svn.apache.org/r1822594])) was (Author: catholicon): Updated earlier impl in trunk at [r1821516|https://svn.apache.org/r1821516]. Backported to 1.8 branch in [r1821521|https://svn.apache.org/r1821521]. Backported to 1.6 branch in [r1822592|https://svn.apache.org/r1822592]. Backported to 1.4 branch in [r1822593|https://svn.apache.org/r1822593]. So, trunk ([r1821325|https://svn.apache.org/r1821325], [r1821516|https://svn.apache.org/r1821516]), 1.8 ([r1821521|https://svn.apache.org/r1821521], 1.6 ([r1822592|https://svn.apache.org/r1822592]), 1.4 ([r1822593|https://svn.apache.org/r1822593])) > Excerpt Highlighting for a property is not correct > --- > > Key: OAK-4401 > URL: https://issues.apache.org/jira/browse/OAK-4401 > Project: Jackrabbit Oak > Issue Type: Bug > Components: query >Affects Versions: 1.5.2 >Reporter: Ankit Agarwal >Assignee: Vikas Saurabh >Priority: Major > Fix For: 1.9.0, 1.10, 1.8.1 > > Attachments: > 0001-OAK-4401-Excerpt-Highlighting-for-a-property-is-not-.patch > > > if we have following text at property > /jcr:content/text > === > A state agency’s Conflict of Interest Code must reflect the current structure > of the organization and properly identify officials andemployees > = > and if rep:excerpt(/jcr:content/text) is been calling after search then > == > officials will be in output , which is incorrect. > == -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OAK-4401) Excerpt Highlighting for a property is not correct
[ https://issues.apache.org/jira/browse/OAK-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330663#comment-16330663 ] Vikas Saurabh edited comment on OAK-4401 at 1/30/18 12:12 AM: -- Updated earlier impl in trunk at [r1821516|https://svn.apache.org/r1821516]. Backported to 1.8 branch in [r1821521|https://svn.apache.org/r1821521]. Backported to 1.6 branch in [r1822592|https://svn.apache.org/r1822592]. Backported to 1.4 branch in [r1822593|https://svn.apache.org/r1822593]. So, trunk ([r1821325|https://svn.apache.org/r1821325], [r1821516|https://svn.apache.org/r1821516]), 1.8 ([r1821521|https://svn.apache.org/r1821521], 1.6 ([r1822592|https://svn.apache.org/r1822592]), 1.4 ([r1822593|https://svn.apache.org/r1822593])) was (Author: catholicon): Updated earlier impl in trunk at [r1821516|https://svn.apache.org/r1821516]. Backported to 1.8 branch in [r1821521|https://svn.apache.org/r1821521]. Backported to 1.6 branch in [r1822592|https://svn.apache.org/r1822592]. So, trunk ([r1821325|https://svn.apache.org/r1821325], [r1821516|https://svn.apache.org/r1821516]), 1.8 ([r1821521|https://svn.apache.org/r1821521], 1.6 ([r1822592|https://svn.apache.org/r1822592])) > Excerpt Highlighting for a property is not correct > --- > > Key: OAK-4401 > URL: https://issues.apache.org/jira/browse/OAK-4401 > Project: Jackrabbit Oak > Issue Type: Bug > Components: query >Affects Versions: 1.5.2 >Reporter: Ankit Agarwal >Assignee: Vikas Saurabh >Priority: Major > Fix For: 1.9.0, 1.10, 1.8.1 > > Attachments: > 0001-OAK-4401-Excerpt-Highlighting-for-a-property-is-not-.patch > > > if we have following text at property > /jcr:content/text > === > A state agency’s Conflict of Interest Code must reflect the current structure > of the organization and properly identify officials andemployees > = > and if rep:excerpt(/jcr:content/text) is been calling after search then > == > officials will be in output , which is incorrect. > == -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OAK-4401) Excerpt Highlighting for a property is not correct
[ https://issues.apache.org/jira/browse/OAK-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330663#comment-16330663 ] Vikas Saurabh edited comment on OAK-4401 at 1/30/18 12:03 AM: -- Updated earlier impl in trunk at [r1821516|https://svn.apache.org/r1821516]. Backported to 1.8 branch in [r1821521|https://svn.apache.org/r1821521]. Backported to 1.6 branch in [r1822592|https://svn.apache.org/r1822592]. So, trunk ([r1821325|https://svn.apache.org/r1821325], [r1821516|https://svn.apache.org/r1821516]), 1.8 ([r1821521|https://svn.apache.org/r1821521], 1.6 ([r1822592|https://svn.apache.org/r1822592])) was (Author: catholicon): Updated earlier impl in trunk at [r1821516|https://svn.apache.org/r1821516]. Backported to 1.8 branch in [r1821521|https://svn.apache.org/r1821521]. So, trunk ([r1821325|https://svn.apache.org/r1821325], [r1821516|https://svn.apache.org/r1821516]), 1.8 ([r1821521|https://svn.apache.org/r1821521]) > Excerpt Highlighting for a property is not correct > --- > > Key: OAK-4401 > URL: https://issues.apache.org/jira/browse/OAK-4401 > Project: Jackrabbit Oak > Issue Type: Bug > Components: query >Affects Versions: 1.5.2 >Reporter: Ankit Agarwal >Assignee: Vikas Saurabh >Priority: Major > Fix For: 1.9.0, 1.10, 1.8.1 > > Attachments: > 0001-OAK-4401-Excerpt-Highlighting-for-a-property-is-not-.patch > > > if we have following text at property > /jcr:content/text > === > A state agency’s Conflict of Interest Code must reflect the current structure > of the organization and properly identify officials andemployees > = > and if rep:excerpt(/jcr:content/text) is been calling after search then > == > officials will be in output , which is incorrect. > == -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7218) Build Jackrabbit Oak #1210 failed
Hudson created OAK-7218: --- Summary: Build Jackrabbit Oak #1210 failed Key: OAK-7218 URL: https://issues.apache.org/jira/browse/OAK-7218 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit Oak #1210 has failed. First failed run: [Jackrabbit Oak #1210|https://builds.apache.org/job/Jackrabbit%20Oak/1210/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1210/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7217) check public Oak APIs for references to Guava
[ https://issues.apache.org/jira/browse/OAK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7217: Summary: check public Oak APIs for references to Guava (was: check public OAK APis for references to Guava) > check public Oak APIs for references to Guava > - > > Key: OAK-7217 > URL: https://issues.apache.org/jira/browse/OAK-7217 > Project: Jackrabbit Oak > Issue Type: Technical task >Reporter: Julian Reschke >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7217) check public OAK APis for references to Guava
Julian Reschke created OAK-7217: --- Summary: check public OAK APis for references to Guava Key: OAK-7217 URL: https://issues.apache.org/jira/browse/OAK-7217 Project: Jackrabbit Oak Issue Type: Technical task Reporter: Julian Reschke -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7185) Upgrade jclouds dependency to 2.0.3
[ https://issues.apache.org/jira/browse/OAK-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343586#comment-16343586 ] Julian Reschke commented on OAK-7185: - trunk: [r1822527|http://svn.apache.org/r1822527] > Upgrade jclouds dependency to 2.0.3 > --- > > Key: OAK-7185 > URL: https://issues.apache.org/jira/browse/OAK-7185 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: blob, blob-plugins >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_8 > Fix For: 1.9.0, 1.10 > > Attachments: OAK-7185.diff > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7185) Upgrade jclouds dependency to 2.0.3
[ https://issues.apache.org/jira/browse/OAK-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7185: Labels: candidate_oak_1_8 (was: ) > Upgrade jclouds dependency to 2.0.3 > --- > > Key: OAK-7185 > URL: https://issues.apache.org/jira/browse/OAK-7185 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: blob, blob-plugins >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_8 > Fix For: 1.9.0, 1.10 > > Attachments: OAK-7185.diff > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7185) Upgrade jclouds dependency to 2.0.3
[ https://issues.apache.org/jira/browse/OAK-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-7185. - Resolution: Fixed Assignee: Julian Reschke Fix Version/s: 1.10 1.9.0 > Upgrade jclouds dependency to 2.0.3 > --- > > Key: OAK-7185 > URL: https://issues.apache.org/jira/browse/OAK-7185 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: blob, blob-plugins >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_8 > Fix For: 1.9.0, 1.10 > > Attachments: OAK-7185.diff > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7194) Threads are going in blocked state - OAK segment
[
https://issues.apache.org/jira/browse/OAK-7194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343516#comment-16343516
]
Michael Dürig commented on OAK-7194:
Where you able to identify a deadlock between threads? If so, please share the
stack traces of all involved parties (i.e. threads and monitors). Otherwise,
these stack traces usually show up in a contended system. Have a look at
[https://helpx.adobe.com/experience-manager/kb/how-to-monitor-the-tarmk.html]
for some general advice on how monitor your instance for abnormal load.
> Threads are going in blocked state - OAK segment
>
>
> Key: OAK-7194
> URL: https://issues.apache.org/jira/browse/OAK-7194
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Affects Versions: 1.6.2
>Reporter: Kshitiz Garg
>Priority: Critical
>
> We are using AEM and it internally is using OAK 1.6.2. Our application is
> going to a choked state many a times. Our thread dump analysis is always
> pointing to this stack trace with many blocked threads. Is it a known issue?
> Or is there a setting to avoid it? We are using tar files based repository
> underneath and are using default settings:
>
> {noformat}
> - nativeId:0x1208 - state:BLOCKED
> stackTrace:
> java.lang.Thread.State: BLOCKED (on object monitor)
> at org.apache.jackrabbit.oak.segment.SegmentId.getSegment(SegmentId.java:121)
> - waiting to lock <0x000414d8c250> (a
> org.apache.jackrabbit.oak.segment.SegmentId)
> at org.apache.jackrabbit.oak.segment.Record.getSegment(Record.java:70)
> at org.apache.jackrabbit.oak.segment.MapRecord.getEntry(MapRecord.java:160)
> at org.apache.jackrabbit.oak.segment.MapRecord.getEntry(MapRecord.java:192)
> at org.apache.jackrabbit.oak.segment.MapRecord.getEntry(MapRecord.java:192)
> at org.apache.jackrabbit.oak.segment.MapRecord.getEntry(MapRecord.java:192)
> at
> org.apache.jackrabbit.oak.segment.SegmentNodeState.getChildNode(SegmentNodeState.java:412)
> at
> org.apache.jackrabbit.oak.plugins.tree.impl.ImmutableTree.createChild(ImmutableTree.java:125)
> at
> org.apache.jackrabbit.oak.plugins.tree.impl.ImmutableTree.getChild(ImmutableTree.java:176)
> at
> org.apache.jackrabbit.oak.plugins.tree.impl.ImmutableTree.getChild(ImmutableTree.java:81)
> at
> org.apache.jackrabbit.oak.security.authorization.permission.PermissionUtil.getPrincipalRoot(PermissionUtil.java:83)
> at
> org.apache.jackrabbit.oak.security.authorization.permission.PermissionStoreImpl.getPrincipalRoot(PermissionStoreImpl.java:132)
> at
> org.apache.jackrabbit.oak.security.authorization.permission.PermissionStoreImpl.getNumEntries(PermissionStoreImpl.java:103)
> at
> org.apache.jackrabbit.oak.security.authorization.permission.PermissionEntryCache.getNumEntries(PermissionEntryCache.java:102)
> at
> org.apache.jackrabbit.oak.security.authorization.permission.PermissionEntryProviderImpl.init(PermissionEntryProviderImpl.java:79)
> at
> org.apache.jackrabbit.oak.security.authorization.permission.PermissionEntryProviderImpl.(PermissionEntryProviderImpl.java:72)
> at
> org.apache.jackrabbit.oak.security.authorization.permission.CompiledPermissionImpl.(CompiledPermissionImpl.java:112)
> at
> org.apache.jackrabbit.oak.security.authorization.permission.CompiledPermissionImpl.create(CompiledPermissionImpl.java:126)
> at
> org.apache.jackrabbit.oak.security.authorization.permission.PermissionProviderImpl.getCompiledPermissions(PermissionProviderImpl.java:162)
> at
> org.apache.jackrabbit.oak.security.authorization.permission.PermissionProviderImpl.getTreePermission(PermissionProviderImpl.java:151)
> at
> org.apache.jackrabbit.oak.security.authorization.composite.CompositeTreePermission.create(CompositeTreePermission.java:67)
> at
> org.apache.jackrabbit.oak.security.authorization.composite.CompositePermissionProvider.getTreePermission(CompositePermissionProvider.java:147)
> at
> org.apache.jackrabbit.oak.core.SecureNodeBuilder.getTreePermission(SecureNodeBuilder.java:357)
> at
> org.apache.jackrabbit.oak.core.SecureNodeBuilder.getTreePermission(SecureNodeBuilder.java:360)
> at
> org.apache.jackrabbit.oak.core.SecureNodeBuilder.getTreePermission(SecureNodeBuilder.java:360)
> at
> org.apache.jackrabbit.oak.core.SecureNodeBuilder.access$100(SecureNodeBuilder.java:49)
> at
> org.apache.jackrabbit.oak.core.SecureNodeBuilder$ReadablePropertyPredicate.apply(SecureNodeBuilder.java:377)
> at
> org.apache.jackrabbit.oak.core.SecureNodeBuilder.getProperty(SecureNodeBuilder.java:184)
> at
> org.apache.jackrabbit.oak.plugins.tree.impl.AbstractTree.getProperty(AbstractTree.java:249)
> at
> org.apache.jackrabbit.oak.core.MutableTree.getProperty(MutableTree.java:128)
> at
> org.apache.jackrabbit.oak.util.TreeUtil.getStringInternal(TreeUtil.java:108)
> at
[jira] [Created] (OAK-7216) Remove support for binaries in persistent cache
Marcel Reutegger created OAK-7216: - Summary: Remove support for binaries in persistent cache Key: OAK-7216 URL: https://issues.apache.org/jira/browse/OAK-7216 Project: Jackrabbit Oak Issue Type: Task Components: documentmk Reporter: Marcel Reutegger Fix For: 1.10 The persistent cache currently stores binaries up to one MB by default. However most of the BlobStore implementations already provide some form of caching. E.g. for S3 a cache on the local filesystem is maintained and when using a Jackrabbit FileDataStore the persistent cache is actually unnecessary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7203) Make MountInfoProvider service in AuthorizationConfigurationImpl optional
[
https://issues.apache.org/jira/browse/OAK-7203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343506#comment-16343506
]
Alex Deparvu commented on OAK-7203:
---
I agree with making it optional, but I'm not convinced we need to make it
dynamic. Is the _MountInfoProvider_ service expected to be changed on a live
system (causing the reference to go and come again)?
> Make MountInfoProvider service in AuthorizationConfigurationImpl optional
> -
>
> Key: OAK-7203
> URL: https://issues.apache.org/jira/browse/OAK-7203
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
>Affects Versions: 1.8.1
>Reporter: Oliver Lietz
>Priority: Major
> Attachments: OAK-7203.patch
>
>
> While testing Sling with Oak 1.8 I've observed that
> AuthorizationConfigurationImpl gets not activated due to missing
> MountInfoProvider service:
> {noformat}
> @Reference
> private MountInfoProvider mountInfoProvider =
> Mounts.defaultMountInfoProvider();
> {noformat}
> {noformat}
> org.apache.jackrabbit.oak.security.authorization.AuthorizationConfigurationImpl
> Bundleorg.apache.jackrabbit.oak-core (63)
> Implementation Class
> org.apache.jackrabbit.oak.security.authorization.AuthorizationConfigurationImpl
> Default State enabled
> Activationdelayed
> Configuration Policy optional
> Service Type singleton
> Services
> org.apache.jackrabbit.oak.spi.security.authorization.AuthorizationConfiguration
> org.apache.jackrabbit.oak.spi.security.SecurityConfiguration
> PID
> org.apache.jackrabbit.oak.security.authorization.AuthorizationConfigurationImpl
> Reference mountInfoProvider Unsatisfied
> Service Name: org.apache.jackrabbit.oak.spi.mount.MountInfoProvider
> Cardinality: 1..1
> Policy: static
> Policy Option: reluctant
> No Services bound
> Propertiescomponent.id = 35
> component.name =
> org.apache.jackrabbit.oak.security.authorization.AuthorizationConfigurationImpl
> configurationRanking = 100
> importBehavior = abort
> oak.security.name =
> org.apache.jackrabbit.oak.security.authorization.AuthorizationConfigurationImpl
> readPaths = [/jcr:system/rep:namespaces, /jcr:system/jcr:nodeTypes,
> /jcr:system/rep:privileges]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7214) Build Jackrabbit Oak #1209 failed
[
https://issues.apache.org/jira/browse/OAK-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-7214:
--
Description:
No description is provided
The build Jackrabbit Oak #1209 has failed.
First failed run: [Jackrabbit Oak
#1209|https://builds.apache.org/job/Jackrabbit%20Oak/1209/] [console
log|https://builds.apache.org/job/Jackrabbit%20Oak/1209/console]
{noformat}
Build timed out (after 90 minutes). Marking the build as failed.
{noformat}
was:
No description is provided
The build Jackrabbit Oak #1209 has failed.
First failed run: [Jackrabbit Oak
#1209|https://builds.apache.org/job/Jackrabbit%20Oak/1209/] [console
log|https://builds.apache.org/job/Jackrabbit%20Oak/1209/console]
> Build Jackrabbit Oak #1209 failed
> -
>
> Key: OAK-7214
> URL: https://issues.apache.org/jira/browse/OAK-7214
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1209 has failed.
> First failed run: [Jackrabbit Oak
> #1209|https://builds.apache.org/job/Jackrabbit%20Oak/1209/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1209/console]
> {noformat}
> Build timed out (after 90 minutes). Marking the build as failed.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OAK-7214) Build Jackrabbit Oak #1209 failed
[ https://issues.apache.org/jira/browse/OAK-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-7214. --- Resolution: Duplicate > Build Jackrabbit Oak #1209 failed > - > > Key: OAK-7214 > URL: https://issues.apache.org/jira/browse/OAK-7214 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1209 has failed. > First failed run: [Jackrabbit Oak > #1209|https://builds.apache.org/job/Jackrabbit%20Oak/1209/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1209/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OAK-7214) Build Jackrabbit Oak #1209 failed
[
https://issues.apache.org/jira/browse/OAK-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger closed OAK-7214.
-
> Build Jackrabbit Oak #1209 failed
> -
>
> Key: OAK-7214
> URL: https://issues.apache.org/jira/browse/OAK-7214
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1209 has failed.
> First failed run: [Jackrabbit Oak
> #1209|https://builds.apache.org/job/Jackrabbit%20Oak/1209/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1209/console]
> {noformat}
> Build timed out (after 90 minutes). Marking the build as failed.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-6058) Avoid accessing remote binaries when migration involves S3
[
https://issues.apache.org/jira/browse/OAK-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343320#comment-16343320
]
Francesco Mari commented on OAK-6058:
-
[~tomek.rekawek], if I understood {{OakUpgrade}} correctly, and
{{NodeStateCopier}} in particular, the code already does what this issue
proposes. During a sidegrade between oak-segment and oak-segment-tar, two
instances of {{SegmentBlob}} are compared, respectively
{{o.a.j.o.plugins.segment.SegmentBlob}} and {{o.a.j.o.segment.SegmentBlob}}.
Being their classes different, they are passed to
{{o.a.j.o.plugins.memory.AbstractBlob#equal}}, which compares their length and
content identities. In both cases the content identities are the BLOB IDs that
are serialized on disk. As long as the binaries are the same, their content
identites are the same too, and their content doesn't need to be inspected.
Am I missing something from oak-upgrade that might influence the computation of
the content identities of the BLOBs?
> Avoid accessing remote binaries when migration involves S3
> --
>
> Key: OAK-6058
> URL: https://issues.apache.org/jira/browse/OAK-6058
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: upgrade
>Reporter: Tomek Rękawek
>Assignee: Francesco Mari
>Priority: Major
> Fix For: 1.10
>
>
> When migrating (sidegrade) a repository referencing the S3DataStore, we
> should avoid accessing the binaries themselves and use their identifiers
> instead.
> In particular:
> * it should be possible to copy a a nodestore referencing S3DataStore without
> accessing/configuring S3 at all (copy binaries by the references),
> * if the S3DataStore is configured for the migration and the destination
> already exists, the blob identifiers should be used in the equals() method,
> not the whole binary input stream.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OAK-7215) Add configurable repository size cap to SegmentOverflowExceptionIT
Michael Dürig created OAK-7215:
--
Summary: Add configurable repository size cap to
SegmentOverflowExceptionIT
Key: OAK-7215
URL: https://issues.apache.org/jira/browse/OAK-7215
Project: Jackrabbit Oak
Issue Type: Improvement
Components: segment-tar
Reporter: Michael Dürig
Assignee: Michael Dürig
Fix For: 1.9.0
{{SegmentOverflowExceptionIT}} potentially consumes a lot of disk space.
Running it for 10 minutes on a AWS m4.4xlarge instance with 900 / 3000 IOPS
resulted in 80GB being taken up.
Currently the test can be time boxed but not size boxed. I suggest to add
another option to cap the repository size in addition to the existing
{{-Dtimeout}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OAK-7214) Build Jackrabbit Oak #1209 failed
Hudson created OAK-7214: --- Summary: Build Jackrabbit Oak #1209 failed Key: OAK-7214 URL: https://issues.apache.org/jira/browse/OAK-7214 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit Oak #1209 has failed. First failed run: [Jackrabbit Oak #1209|https://builds.apache.org/job/Jackrabbit%20Oak/1209/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1209/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-5506) reject item names with unpaired surrogates early
[
https://issues.apache.org/jira/browse/OAK-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343227#comment-16343227
]
Michael Dürig commented on OAK-5506:
bq. is it worth the effort?
I don't know. But finding out is part of this effort.
> reject item names with unpaired surrogates early
>
>
> Key: OAK-5506
> URL: https://issues.apache.org/jira/browse/OAK-5506
> Project: Jackrabbit Oak
> Issue Type: Wish
> Components: core, jcr, segment-tar
>Affects Versions: 1.5.18
>Reporter: Julian Reschke
>Assignee: Francesco Mari
>Priority: Minor
> Fix For: 1.10
>
> Attachments: OAK-5506-01.patch, OAK-5506-02.patch, OAK-5506-4.diff,
> OAK-5506-bench.diff, OAK-5506-name-conversion.diff, OAK-5506-segment.diff,
> OAK-5506.diff, ValidNamesTest.java
>
>
> Apparently, the following node name is accepted:
>{{"foo\ud800"}}
> but a subsequent {{getPath()}} call fails:
> {noformat}
> javax.jcr.InvalidItemStateException: This item [/test_node/foo?] does not
> exist anymore
> at
> org.apache.jackrabbit.oak.jcr.delegate.ItemDelegate.checkAlive(ItemDelegate.java:86)
> at
> org.apache.jackrabbit.oak.jcr.session.operation.ItemOperation.checkPreconditions(ItemOperation.java:34)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.prePerform(SessionDelegate.java:615)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:205)
> at
> org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:112)
> at
> org.apache.jackrabbit.oak.jcr.session.ItemImpl.getPath(ItemImpl.java:140)
> at
> org.apache.jackrabbit.oak.jcr.session.NodeImpl.getPath(NodeImpl.java:106)
> at
> org.apache.jackrabbit.oak.jcr.ValidNamesTest.nameTest(ValidNamesTest.java:271)
> at
> org.apache.jackrabbit.oak.jcr.ValidNamesTest.testUnpairedSurrogate(ValidNamesTest.java:259)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source){noformat}
> (test case follows)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7188) guava: ListenableFuture.transform() changes to transformAsync in version 20
[
https://issues.apache.org/jira/browse/OAK-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343226#comment-16343226
]
Michael Dürig commented on OAK-7188:
AFAIU the Guava version used for testing is pretty much constant per Oak
version. So I would suggest to use whatever is the current name they come up
for what used to be {{ListenableFuture.transform()}}.
> guava: ListenableFuture.transform() changes to transformAsync in version 20
> ---
>
> Key: OAK-7188
> URL: https://issues.apache.org/jira/browse/OAK-7188
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: segment-tar
>Reporter: Julian Reschke
>Priority: Major
> Attachments: OAK-7188.diff
>
>
> See
> https://google.github.io/guava/releases/19.0/api/docs/com/google/common/util/concurrent/Futures.html#transform(com.google.common.util.concurrent.ListenableFuture,%20com.google.common.util.concurrent.AsyncFunction)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7213) Avoid call for child node when bundle contains all children
[
https://issues.apache.org/jira/browse/OAK-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343225#comment-16343225
]
Marcel Reutegger commented on OAK-7213:
---
Proposed fix in [^OAK-7213.patch]. [~chetanm], can you please review?
> Avoid call for child node when bundle contains all children
> ---
>
> Key: OAK-7213
> URL: https://issues.apache.org/jira/browse/OAK-7213
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Minor
> Labels: bundling
> Fix For: 1.10
>
> Attachments: OAK-7213.patch
>
>
> When nodes are bundled in a document, the DocumentNodeStore keeps track of
> whether all children are included in a document. The presence of the hidden
> {{:doc-has-child-non-bundled}} property indicates there are non bundled child
> nodes. For the case when a document contains all children in the bundle, the
> DocumentNodeStore still does a find call on the DocumentStore when asked for
> an unknown child node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7213) Avoid call for child node when bundle contains all children
[
https://issues.apache.org/jira/browse/OAK-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-7213:
--
Attachment: OAK-7213.patch
> Avoid call for child node when bundle contains all children
> ---
>
> Key: OAK-7213
> URL: https://issues.apache.org/jira/browse/OAK-7213
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Minor
> Labels: bundling
> Fix For: 1.10
>
> Attachments: OAK-7213.patch
>
>
> When nodes are bundled in a document, the DocumentNodeStore keeps track of
> whether all children are included in a document. The presence of the hidden
> {{:doc-has-child-non-bundled}} property indicates there are non bundled child
> nodes. For the case when a document contains all children in the bundle, the
> DocumentNodeStore still does a find call on the DocumentStore when asked for
> an unknown child node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OAK-7195) Node.getMixinNodeTypes() may check for child node named jcr:mixinTypes
[
https://issues.apache.org/jira/browse/OAK-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved OAK-7195.
---
Resolution: Fixed
Fix Version/s: 1.9.0
Applied the most recent patch: http://svn.apache.org/r1822497
> Node.getMixinNodeTypes() may check for child node named jcr:mixinTypes
> --
>
> Key: OAK-7195
> URL: https://issues.apache.org/jira/browse/OAK-7195
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
>Affects Versions: 1.2, 1.4, 1.6.0, 1.8.0
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Minor
> Labels: performance
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7195-2.patch, OAK-7195.patch
>
>
> In some cases a call to {{Node.getMixinNodeTypes()}} may result in a check
> whether there is a child node named {{jcr:mixinTypes}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7213) Avoid call for child node when bundle contains all children
[
https://issues.apache.org/jira/browse/OAK-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343202#comment-16343202
]
Marcel Reutegger commented on OAK-7213:
---
Added an ignored test: http://svn.apache.org/r1822496
> Avoid call for child node when bundle contains all children
> ---
>
> Key: OAK-7213
> URL: https://issues.apache.org/jira/browse/OAK-7213
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Minor
> Labels: bundling
> Fix For: 1.10
>
>
> When nodes are bundled in a document, the DocumentNodeStore keeps track of
> whether all children are included in a document. The presence of the hidden
> {{:doc-has-child-non-bundled}} property indicates there are non bundled child
> nodes. For the case when a document contains all children in the bundle, the
> DocumentNodeStore still does a find call on the DocumentStore when asked for
> an unknown child node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-6373) oak-run check should also check checkpoints
[
https://issues.apache.org/jira/browse/OAK-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343183#comment-16343183
]
Andrei Dulceanu commented on OAK-6373:
--
I adapted the old tests to take into account the new {{--head-}} and
{{-checkpoints}} options and also added new tests for dealing with invalid
revisions. [~mduerig], [~frm], could you take a look at the latest commits in
my branch [0]?
{quote}Maybe the ConsistencyChecker.checkConsistency() should be broken down as
it is getting quite long?
{quote}
I started refactoring that method, but didn't come up with a good outcome
without cluttering the new methods with lots of parameters. I would leave this
as it is for the time being. We can take this up again in a new issue focused
on simplifying/cleaning the code. WDYT?
[0] [https://github.com/dulceanu/jackrabbit-oak/commits/issues/OAK-6373]
> oak-run check should also check checkpoints
>
>
> Key: OAK-6373
> URL: https://issues.apache.org/jira/browse/OAK-6373
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run, segment-tar
>Reporter: Michael Dürig
>Assignee: Andrei Dulceanu
>Priority: Major
> Labels: candidate_oak_1_8, tooling
> Fix For: 1.9.0, 1.10
>
>
> {{oak-run check}} does currently *not* traverse and check the items in the
> checkpoint. I think we should change this and add an option to traverse all,
> some or none of the checkpoints. When doing this we need to keep in mind the
> interaction of this new feature with the {{filter}} option: the paths passed
> through this option need then be prefixed with {{/root}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-5272) Expose BlobStore API to provide information whether blob id is content hashed
[
https://issues.apache.org/jira/browse/OAK-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343163#comment-16343163
]
Amit Jain commented on OAK-5272:
[~mduerig], [~tmueller]
Would an addition of a method below to the BlobStore be good for the purpose?
This keeps the amount of required changes to low. I have avoided pushing the
blob equal method to the BlobStore because currently the BlobStore(s) are not
aware of the Blob object.
{code:java}
/**
*
* Will return true if blob ids are generated from content hash
*
* @return true if blobs are content addressable
*/
boolean hasContentAdressableBlobIds();
{code}
> Expose BlobStore API to provide information whether blob id is content hashed
> -
>
> Key: OAK-5272
> URL: https://issues.apache.org/jira/browse/OAK-5272
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob
>Reporter: Amit Jain
>Priority: Major
>
> As per discussion in OAK-5253 it's better to have some information from the
> BlobStore(s) whether the blob id can be solely relied upon for comparison.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7188) guava: ListenableFuture.transform() changes to transformAsync in version 20
[ https://issues.apache.org/jira/browse/OAK-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343119#comment-16343119 ] Julian Reschke commented on OAK-7188: - Not entirely sure that helps. If we keep the code as is, and configure a matching guava version for the tests, we'll have a problem if we want to test with a newer guava version. Vice versa: same problem, no? > guava: ListenableFuture.transform() changes to transformAsync in version 20 > --- > > Key: OAK-7188 > URL: https://issues.apache.org/jira/browse/OAK-7188 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: segment-tar >Reporter: Julian Reschke >Priority: Major > Attachments: OAK-7188.diff > > > See > https://google.github.io/guava/releases/19.0/api/docs/com/google/common/util/concurrent/Futures.html#transform(com.google.common.util.concurrent.ListenableFuture,%20com.google.common.util.concurrent.AsyncFunction) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-5506) reject item names with unpaired surrogates early
[
https://issues.apache.org/jira/browse/OAK-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343117#comment-16343117
]
Julian Reschke commented on OAK-5506:
-
[~mduerig] - in earlier comments you said that the current behavior is ok
because it "garbage in, garbage out" - why do you care how garbage is handled
then?
FWIW, we certainly can do more work than having an emergency system variable,
the question is: is it worth the effort?
> reject item names with unpaired surrogates early
>
>
> Key: OAK-5506
> URL: https://issues.apache.org/jira/browse/OAK-5506
> Project: Jackrabbit Oak
> Issue Type: Wish
> Components: core, jcr, segment-tar
>Affects Versions: 1.5.18
>Reporter: Julian Reschke
>Assignee: Francesco Mari
>Priority: Minor
> Fix For: 1.10
>
> Attachments: OAK-5506-01.patch, OAK-5506-02.patch, OAK-5506-4.diff,
> OAK-5506-bench.diff, OAK-5506-name-conversion.diff, OAK-5506-segment.diff,
> OAK-5506.diff, ValidNamesTest.java
>
>
> Apparently, the following node name is accepted:
>{{"foo\ud800"}}
> but a subsequent {{getPath()}} call fails:
> {noformat}
> javax.jcr.InvalidItemStateException: This item [/test_node/foo?] does not
> exist anymore
> at
> org.apache.jackrabbit.oak.jcr.delegate.ItemDelegate.checkAlive(ItemDelegate.java:86)
> at
> org.apache.jackrabbit.oak.jcr.session.operation.ItemOperation.checkPreconditions(ItemOperation.java:34)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.prePerform(SessionDelegate.java:615)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:205)
> at
> org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:112)
> at
> org.apache.jackrabbit.oak.jcr.session.ItemImpl.getPath(ItemImpl.java:140)
> at
> org.apache.jackrabbit.oak.jcr.session.NodeImpl.getPath(NodeImpl.java:106)
> at
> org.apache.jackrabbit.oak.jcr.ValidNamesTest.nameTest(ValidNamesTest.java:271)
> at
> org.apache.jackrabbit.oak.jcr.ValidNamesTest.testUnpairedSurrogate(ValidNamesTest.java:259)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source){noformat}
> (test case follows)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OAK-7205) Test failure: ActiveDeletedBlobSyncTrackerTest.syncActiveDeletionWithBlobTracker
[
https://issues.apache.org/jira/browse/OAK-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Jain reassigned OAK-7205:
--
Assignee: Amit Jain
> Test failure:
> ActiveDeletedBlobSyncTrackerTest.syncActiveDeletionWithBlobTracker
>
>
> Key: OAK-7205
> URL: https://issues.apache.org/jira/browse/OAK-7205
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, lucene
>Reporter: Hudson
>Assignee: Amit Jain
>Priority: Major
> Fix For: 1.10
>
>
> No description is provided
> The build Jackrabbit Oak #1203 has failed.
> First failed run: [Jackrabbit Oak
> #1203|https://builds.apache.org/job/Jackrabbit%20Oak/1203/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1203/console]
> {noformat}
> [ERROR]
> syncActiveDeletionWithBlobTracker(org.apache.jackrabbit.oak.plugins.index.lucene.directory.ActiveDeletedBlobSyncTrackerTest)
> Time elapsed: 0.364 s <<< FAILURE!
> java.lang.AssertionError: First GC should delete some chunks
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.directory.ActiveDeletedBlobSyncTrackerTest.syncActiveDeletionWithBlobTracker(ActiveDeletedBlobSyncTrackerTest.java:138)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7185) Upgrade jclouds dependency to 2.0.3
[ https://issues.apache.org/jira/browse/OAK-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343116#comment-16343116 ] Amit Jain commented on OAK-7185: [~reschke] +1 to update the version. The general connector uses aws dependencies and the unused S3 connector based on chunked storage uses the basic jclouds api. > Upgrade jclouds dependency to 2.0.3 > --- > > Key: OAK-7185 > URL: https://issues.apache.org/jira/browse/OAK-7185 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: blob, blob-plugins >Reporter: Julian Reschke >Priority: Minor > Attachments: OAK-7185.diff > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-5506) reject item names with unpaired surrogates early
[
https://issues.apache.org/jira/browse/OAK-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343106#comment-16343106
]
Michael Dürig commented on OAK-5506:
TBH I'm not in favour of this change unless we have better ways for dealing
with upgrades than an emergency button. See my
[comment|https://issues.apache.org/jira/browse/OAK-7208?focusedCommentId=16343101=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16343101]
on OAK-7280, which applies here respectively.
> reject item names with unpaired surrogates early
>
>
> Key: OAK-5506
> URL: https://issues.apache.org/jira/browse/OAK-5506
> Project: Jackrabbit Oak
> Issue Type: Wish
> Components: core, jcr, segment-tar
>Affects Versions: 1.5.18
>Reporter: Julian Reschke
>Assignee: Francesco Mari
>Priority: Minor
> Fix For: 1.10
>
> Attachments: OAK-5506-01.patch, OAK-5506-02.patch, OAK-5506-4.diff,
> OAK-5506-bench.diff, OAK-5506-name-conversion.diff, OAK-5506-segment.diff,
> OAK-5506.diff, ValidNamesTest.java
>
>
> Apparently, the following node name is accepted:
>{{"foo\ud800"}}
> but a subsequent {{getPath()}} call fails:
> {noformat}
> javax.jcr.InvalidItemStateException: This item [/test_node/foo?] does not
> exist anymore
> at
> org.apache.jackrabbit.oak.jcr.delegate.ItemDelegate.checkAlive(ItemDelegate.java:86)
> at
> org.apache.jackrabbit.oak.jcr.session.operation.ItemOperation.checkPreconditions(ItemOperation.java:34)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.prePerform(SessionDelegate.java:615)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:205)
> at
> org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:112)
> at
> org.apache.jackrabbit.oak.jcr.session.ItemImpl.getPath(ItemImpl.java:140)
> at
> org.apache.jackrabbit.oak.jcr.session.NodeImpl.getPath(NodeImpl.java:106)
> at
> org.apache.jackrabbit.oak.jcr.ValidNamesTest.nameTest(ValidNamesTest.java:271)
> at
> org.apache.jackrabbit.oak.jcr.ValidNamesTest.testUnpairedSurrogate(ValidNamesTest.java:259)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source){noformat}
> (test case follows)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7213) Avoid call for child node when bundle contains all children
[
https://issues.apache.org/jira/browse/OAK-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-7213:
-
Labels: bundling (was: )
> Avoid call for child node when bundle contains all children
> ---
>
> Key: OAK-7213
> URL: https://issues.apache.org/jira/browse/OAK-7213
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Minor
> Labels: bundling
> Fix For: 1.10
>
>
> When nodes are bundled in a document, the DocumentNodeStore keeps track of
> whether all children are included in a document. The presence of the hidden
> {{:doc-has-child-non-bundled}} property indicates there are non bundled child
> nodes. For the case when a document contains all children in the bundle, the
> DocumentNodeStore still does a find call on the DocumentStore when asked for
> an unknown child node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7208) Various disallowed control characters are accepted in item names
[ https://issues.apache.org/jira/browse/OAK-7208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343101#comment-16343101 ] Michael Dürig commented on OAK-7208: bq. do you believe we really need more than that? Yes. I think we need to proactively anticipate the case where users have repositories containing characters that are disallowed under the new rules: * How do we handle migration and upgrade? * How do we detect affected repositories? * Implement proper test scenarios covering migration/upgrade > Various disallowed control characters are accepted in item names > > > Key: OAK-7208 > URL: https://issues.apache.org/jira/browse/OAK-7208 > Project: Jackrabbit Oak > Issue Type: Bug > Components: jcr >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_8 > Fix For: 1.9.0, 1.10 > > Attachments: OAK-7208.diff > > > Our node name check currently allow control characters other than CR, LF and > TAB. This is a bug according to JCR, names being restricted to XML characters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7213) Avoid call for child node when bundle contains all children
Marcel Reutegger created OAK-7213:
-
Summary: Avoid call for child node when bundle contains all
children
Key: OAK-7213
URL: https://issues.apache.org/jira/browse/OAK-7213
Project: Jackrabbit Oak
Issue Type: Improvement
Components: documentmk
Reporter: Marcel Reutegger
Assignee: Marcel Reutegger
Fix For: 1.10
When nodes are bundled in a document, the DocumentNodeStore keeps track of
whether all children are included in a document. The presence of the hidden
{{:doc-has-child-non-bundled}} property indicates there are non bundled child
nodes. For the case when a document contains all children in the bundle, the
DocumentNodeStore still does a find call on the DocumentStore when asked for an
unknown child node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (OAK-7210) Build Jackrabbit Oak #1207 failed
[
https://issues.apache.org/jira/browse/OAK-7210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger closed OAK-7210.
-
> Build Jackrabbit Oak #1207 failed
> -
>
> Key: OAK-7210
> URL: https://issues.apache.org/jira/browse/OAK-7210
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1207 has failed.
> First failed run: [Jackrabbit Oak
> #1207|https://builds.apache.org/job/Jackrabbit%20Oak/1207/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1207/console]
> {noformat}
> Build timed out (after 90 minutes). Marking the build as failed.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OAK-7210) Build Jackrabbit Oak #1207 failed
[
https://issues.apache.org/jira/browse/OAK-7210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved OAK-7210.
---
Resolution: Duplicate
> Build Jackrabbit Oak #1207 failed
> -
>
> Key: OAK-7210
> URL: https://issues.apache.org/jira/browse/OAK-7210
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1207 has failed.
> First failed run: [Jackrabbit Oak
> #1207|https://builds.apache.org/job/Jackrabbit%20Oak/1207/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1207/console]
> {noformat}
> Build timed out (after 90 minutes). Marking the build as failed.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7210) Build Jackrabbit Oak #1207 failed
[
https://issues.apache.org/jira/browse/OAK-7210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-7210:
--
Description:
No description is provided
The build Jackrabbit Oak #1207 has failed.
First failed run: [Jackrabbit Oak
#1207|https://builds.apache.org/job/Jackrabbit%20Oak/1207/] [console
log|https://builds.apache.org/job/Jackrabbit%20Oak/1207/console]
{noformat}
Build timed out (after 90 minutes). Marking the build as failed.
{noformat}
was:
No description is provided
The build Jackrabbit Oak #1207 has failed.
First failed run: [Jackrabbit Oak
#1207|https://builds.apache.org/job/Jackrabbit%20Oak/1207/] [console
log|https://builds.apache.org/job/Jackrabbit%20Oak/1207/console]
> Build Jackrabbit Oak #1207 failed
> -
>
> Key: OAK-7210
> URL: https://issues.apache.org/jira/browse/OAK-7210
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1207 has failed.
> First failed run: [Jackrabbit Oak
> #1207|https://builds.apache.org/job/Jackrabbit%20Oak/1207/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1207/console]
> {noformat}
> Build timed out (after 90 minutes). Marking the build as failed.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7205) Test failure: ActiveDeletedBlobSyncTrackerTest.syncActiveDeletionWithBlobTracker
[
https://issues.apache.org/jira/browse/OAK-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-7205:
--
Fix Version/s: 1.10
> Test failure:
> ActiveDeletedBlobSyncTrackerTest.syncActiveDeletionWithBlobTracker
>
>
> Key: OAK-7205
> URL: https://issues.apache.org/jira/browse/OAK-7205
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, lucene
>Reporter: Hudson
>Priority: Major
> Fix For: 1.10
>
>
> No description is provided
> The build Jackrabbit Oak #1203 has failed.
> First failed run: [Jackrabbit Oak
> #1203|https://builds.apache.org/job/Jackrabbit%20Oak/1203/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1203/console]
> {noformat}
> [ERROR]
> syncActiveDeletionWithBlobTracker(org.apache.jackrabbit.oak.plugins.index.lucene.directory.ActiveDeletedBlobSyncTrackerTest)
> Time elapsed: 0.364 s <<< FAILURE!
> java.lang.AssertionError: First GC should delete some chunks
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.directory.ActiveDeletedBlobSyncTrackerTest.syncActiveDeletionWithBlobTracker(ActiveDeletedBlobSyncTrackerTest.java:138)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7205) Test failure: ActiveDeletedBlobSyncTrackerTest.syncActiveDeletionWithBlobTracker
[
https://issues.apache.org/jira/browse/OAK-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-7205:
--
Summary: Test failure:
ActiveDeletedBlobSyncTrackerTest.syncActiveDeletionWithBlobTracker (was: Build
Jackrabbit Oak #1203 failed)
> Test failure:
> ActiveDeletedBlobSyncTrackerTest.syncActiveDeletionWithBlobTracker
>
>
> Key: OAK-7205
> URL: https://issues.apache.org/jira/browse/OAK-7205
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, lucene
>Reporter: Hudson
>Priority: Major
> Fix For: 1.10
>
>
> No description is provided
> The build Jackrabbit Oak #1203 has failed.
> First failed run: [Jackrabbit Oak
> #1203|https://builds.apache.org/job/Jackrabbit%20Oak/1203/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1203/console]
> {noformat}
> [ERROR]
> syncActiveDeletionWithBlobTracker(org.apache.jackrabbit.oak.plugins.index.lucene.directory.ActiveDeletedBlobSyncTrackerTest)
> Time elapsed: 0.364 s <<< FAILURE!
> java.lang.AssertionError: First GC should delete some chunks
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.directory.ActiveDeletedBlobSyncTrackerTest.syncActiveDeletionWithBlobTracker(ActiveDeletedBlobSyncTrackerTest.java:138)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-5506) reject item names with unpaired surrogates early
[
https://issues.apache.org/jira/browse/OAK-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343072#comment-16343072
]
Julian Reschke commented on OAK-5506:
-
For segment-tar, it would mean that it would stop loosing information, but
instead throw exceptions.
Otherwise, the answer is "no", that is, we may want to have a system variable
to turn this off in emergencies.
> reject item names with unpaired surrogates early
>
>
> Key: OAK-5506
> URL: https://issues.apache.org/jira/browse/OAK-5506
> Project: Jackrabbit Oak
> Issue Type: Wish
> Components: core, jcr, segment-tar
>Affects Versions: 1.5.18
>Reporter: Julian Reschke
>Assignee: Francesco Mari
>Priority: Minor
> Fix For: 1.10
>
> Attachments: OAK-5506-01.patch, OAK-5506-02.patch, OAK-5506-4.diff,
> OAK-5506-bench.diff, OAK-5506-name-conversion.diff, OAK-5506-segment.diff,
> OAK-5506.diff, ValidNamesTest.java
>
>
> Apparently, the following node name is accepted:
>{{"foo\ud800"}}
> but a subsequent {{getPath()}} call fails:
> {noformat}
> javax.jcr.InvalidItemStateException: This item [/test_node/foo?] does not
> exist anymore
> at
> org.apache.jackrabbit.oak.jcr.delegate.ItemDelegate.checkAlive(ItemDelegate.java:86)
> at
> org.apache.jackrabbit.oak.jcr.session.operation.ItemOperation.checkPreconditions(ItemOperation.java:34)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.prePerform(SessionDelegate.java:615)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:205)
> at
> org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:112)
> at
> org.apache.jackrabbit.oak.jcr.session.ItemImpl.getPath(ItemImpl.java:140)
> at
> org.apache.jackrabbit.oak.jcr.session.NodeImpl.getPath(NodeImpl.java:106)
> at
> org.apache.jackrabbit.oak.jcr.ValidNamesTest.nameTest(ValidNamesTest.java:271)
> at
> org.apache.jackrabbit.oak.jcr.ValidNamesTest.testUnpairedSurrogate(ValidNamesTest.java:259)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source){noformat}
> (test case follows)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7205) Test failure: ActiveDeletedBlobSyncTrackerTest.syncActiveDeletionWithBlobTracker
[
https://issues.apache.org/jira/browse/OAK-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-7205:
--
Component/s: lucene
> Test failure:
> ActiveDeletedBlobSyncTrackerTest.syncActiveDeletionWithBlobTracker
>
>
> Key: OAK-7205
> URL: https://issues.apache.org/jira/browse/OAK-7205
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, lucene
>Reporter: Hudson
>Priority: Major
> Fix For: 1.10
>
>
> No description is provided
> The build Jackrabbit Oak #1203 has failed.
> First failed run: [Jackrabbit Oak
> #1203|https://builds.apache.org/job/Jackrabbit%20Oak/1203/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1203/console]
> {noformat}
> [ERROR]
> syncActiveDeletionWithBlobTracker(org.apache.jackrabbit.oak.plugins.index.lucene.directory.ActiveDeletedBlobSyncTrackerTest)
> Time elapsed: 0.364 s <<< FAILURE!
> java.lang.AssertionError: First GC should delete some chunks
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.directory.ActiveDeletedBlobSyncTrackerTest.syncActiveDeletionWithBlobTracker(ActiveDeletedBlobSyncTrackerTest.java:138)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-6058) Avoid accessing remote binaries when migration involves S3
[ https://issues.apache.org/jira/browse/OAK-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-6058: Fix Version/s: 1.10 > Avoid accessing remote binaries when migration involves S3 > -- > > Key: OAK-6058 > URL: https://issues.apache.org/jira/browse/OAK-6058 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: upgrade >Reporter: Tomek Rękawek >Assignee: Francesco Mari >Priority: Major > Fix For: 1.10 > > > When migrating (sidegrade) a repository referencing the S3DataStore, we > should avoid accessing the binaries themselves and use their identifiers > instead. > In particular: > * it should be possible to copy a a nodestore referencing S3DataStore without > accessing/configuring S3 at all (copy binaries by the references), > * if the S3DataStore is configured for the migration and the destination > already exists, the blob identifiers should be used in the equals() method, > not the whole binary input stream. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7205) Build Jackrabbit Oak #1203 failed
[
https://issues.apache.org/jira/browse/OAK-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-7205:
--
Description:
No description is provided
The build Jackrabbit Oak #1203 has failed.
First failed run: [Jackrabbit Oak
#1203|https://builds.apache.org/job/Jackrabbit%20Oak/1203/] [console
log|https://builds.apache.org/job/Jackrabbit%20Oak/1203/console]
{noformat}
[ERROR]
syncActiveDeletionWithBlobTracker(org.apache.jackrabbit.oak.plugins.index.lucene.directory.ActiveDeletedBlobSyncTrackerTest)
Time elapsed: 0.364 s <<< FAILURE!
java.lang.AssertionError: First GC should delete some chunks
at
org.apache.jackrabbit.oak.plugins.index.lucene.directory.ActiveDeletedBlobSyncTrackerTest.syncActiveDeletionWithBlobTracker(ActiveDeletedBlobSyncTrackerTest.java:138)
{noformat}
was:
No description is provided
The build Jackrabbit Oak #1203 has failed.
First failed run: [Jackrabbit Oak
#1203|https://builds.apache.org/job/Jackrabbit%20Oak/1203/] [console
log|https://builds.apache.org/job/Jackrabbit%20Oak/1203/console]
> Build Jackrabbit Oak #1203 failed
> -
>
> Key: OAK-7205
> URL: https://issues.apache.org/jira/browse/OAK-7205
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #1203 has failed.
> First failed run: [Jackrabbit Oak
> #1203|https://builds.apache.org/job/Jackrabbit%20Oak/1203/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1203/console]
> {noformat}
> [ERROR]
> syncActiveDeletionWithBlobTracker(org.apache.jackrabbit.oak.plugins.index.lucene.directory.ActiveDeletedBlobSyncTrackerTest)
> Time elapsed: 0.364 s <<< FAILURE!
> java.lang.AssertionError: First GC should delete some chunks
> at
> org.apache.jackrabbit.oak.plugins.index.lucene.directory.ActiveDeletedBlobSyncTrackerTest.syncActiveDeletionWithBlobTracker(ActiveDeletedBlobSyncTrackerTest.java:138)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7208) Various disallowed control characters are accepted in item names
[ https://issues.apache.org/jira/browse/OAK-7208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343063#comment-16343063 ] Julian Reschke commented on OAK-7208: - There's always the system variable knob we can turn - do you believe we really need more than that? > Various disallowed control characters are accepted in item names > > > Key: OAK-7208 > URL: https://issues.apache.org/jira/browse/OAK-7208 > Project: Jackrabbit Oak > Issue Type: Bug > Components: jcr >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_8 > Fix For: 1.9.0, 1.10 > > Attachments: OAK-7208.diff > > > Our node name check currently allow control characters other than CR, LF and > TAB. This is a bug according to JCR, names being restricted to XML characters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-5506) reject item names with unpaired surrogates early
[
https://issues.apache.org/jira/browse/OAK-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343061#comment-16343061
]
Michael Dürig commented on OAK-5506:
[~reschke], do we understand the backward compatibility concerns the latest
patch introduces? Do we have a migration path for existing repositories that
might contain such characters now disallowed? Do we have test coverage for such
migration cases?
> reject item names with unpaired surrogates early
>
>
> Key: OAK-5506
> URL: https://issues.apache.org/jira/browse/OAK-5506
> Project: Jackrabbit Oak
> Issue Type: Wish
> Components: core, jcr, segment-tar
>Affects Versions: 1.5.18
>Reporter: Julian Reschke
>Assignee: Francesco Mari
>Priority: Minor
> Fix For: 1.10
>
> Attachments: OAK-5506-01.patch, OAK-5506-02.patch, OAK-5506-4.diff,
> OAK-5506-bench.diff, OAK-5506-name-conversion.diff, OAK-5506-segment.diff,
> OAK-5506.diff, ValidNamesTest.java
>
>
> Apparently, the following node name is accepted:
>{{"foo\ud800"}}
> but a subsequent {{getPath()}} call fails:
> {noformat}
> javax.jcr.InvalidItemStateException: This item [/test_node/foo?] does not
> exist anymore
> at
> org.apache.jackrabbit.oak.jcr.delegate.ItemDelegate.checkAlive(ItemDelegate.java:86)
> at
> org.apache.jackrabbit.oak.jcr.session.operation.ItemOperation.checkPreconditions(ItemOperation.java:34)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.prePerform(SessionDelegate.java:615)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:205)
> at
> org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:112)
> at
> org.apache.jackrabbit.oak.jcr.session.ItemImpl.getPath(ItemImpl.java:140)
> at
> org.apache.jackrabbit.oak.jcr.session.NodeImpl.getPath(NodeImpl.java:106)
> at
> org.apache.jackrabbit.oak.jcr.ValidNamesTest.nameTest(ValidNamesTest.java:271)
> at
> org.apache.jackrabbit.oak.jcr.ValidNamesTest.testUnpairedSurrogate(ValidNamesTest.java:259)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source){noformat}
> (test case follows)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7208) Various disallowed control characters are accepted in item names
[ https://issues.apache.org/jira/browse/OAK-7208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343047#comment-16343047 ] Michael Dürig commented on OAK-7208: [~reschke], do we understand the backward compatibility concerns this change introduces? Do we have a migration path for existing repositories that might contain such characters now disallowed? Do we have test coverage for such migration cases? > Various disallowed control characters are accepted in item names > > > Key: OAK-7208 > URL: https://issues.apache.org/jira/browse/OAK-7208 > Project: Jackrabbit Oak > Issue Type: Bug > Components: jcr >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_8 > Fix For: 1.9.0, 1.10 > > Attachments: OAK-7208.diff > > > Our node name check currently allow control characters other than CR, LF and > TAB. This is a bug according to JCR, names being restricted to XML characters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7188) guava: ListenableFuture.transform() changes to transformAsync in version 20
[ https://issues.apache.org/jira/browse/OAK-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343041#comment-16343041 ] Michael Dürig commented on OAK-7188: [~reschke], that occurrence is in a test so there should be a problem to be tied to the specific Guava version used by the test runner. > guava: ListenableFuture.transform() changes to transformAsync in version 20 > --- > > Key: OAK-7188 > URL: https://issues.apache.org/jira/browse/OAK-7188 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: segment-tar >Reporter: Julian Reschke >Priority: Major > Attachments: OAK-7188.diff > > > See > https://google.github.io/guava/releases/19.0/api/docs/com/google/common/util/concurrent/Futures.html#transform(com.google.common.util.concurrent.ListenableFuture,%20com.google.common.util.concurrent.AsyncFunction) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
