[jira] [Updated] (OAK-7376) Build failed: SVNException: svn: E200030: FULL
[ https://issues.apache.org/jira/browse/OAK-7376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Deparvu updated OAK-7376: -- Summary: Build failed: SVNException: svn: E200030: FULL (was: Build Jackrabbit Oak #1337 failed) > Build failed: SVNException: svn: E200030: FULL > -- > > Key: OAK-7376 > URL: https://issues.apache.org/jira/browse/OAK-7376 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1337 has failed. > First failed run: [Jackrabbit Oak > #1337|https://builds.apache.org/job/Jackrabbit%20Oak/1337/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1337/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7376) Build Jackrabbit Oak #1337 failed
[ https://issues.apache.org/jira/browse/OAK-7376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409995#comment-16409995 ] Hudson commented on OAK-7376: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #1338|https://builds.apache.org/job/Jackrabbit%20Oak/1338/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1338/console] > Build Jackrabbit Oak #1337 failed > - > > Key: OAK-7376 > URL: https://issues.apache.org/jira/browse/OAK-7376 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1337 has failed. > First failed run: [Jackrabbit Oak > #1337|https://builds.apache.org/job/Jackrabbit%20Oak/1337/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1337/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-6087) Avoid reads from MongoDB primary
[ https://issues.apache.org/jira/browse/OAK-6087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409745#comment-16409745 ] Marcel Reutegger commented on OAK-6087: --- Work in progress available on github: https://github.com/mreutegg/jackrabbit-oak/tree/OAK-6087 > Avoid reads from MongoDB primary > > > Key: OAK-6087 > URL: https://issues.apache.org/jira/browse/OAK-6087 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Major > Labels: scalability > > With OAK-2106 Oak now attempts to read from a MongoDB secondary when it > detects the requested data is available on the secondary. > When multiple Oak cluster nodes are deployed on a MongoDB replica set, many > reads are still directed to the primary. One of the reasons why this is seen > in practice, are observers and JCR event listeners that are triggered rather > soon after a change happens and therefore read recently modified documents. > This makes it difficult for Oak to direct calls to a nearby secondary, > because changes may not yet be available there. > A rather simple solution for the observers may be to delay processing of > changes until they are available on the near secondary. > A more sophisticated solution discussed offline could hide the replica set > entirely and always read from the nearest secondary. Writes would obviously > still go to the primary, but only return when the write is available also on > the nearest secondary. This guarantees that any subsequent read is able to > see the preceding write. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7376) Build Jackrabbit Oak #1337 failed
Hudson created OAK-7376: --- Summary: Build Jackrabbit Oak #1337 failed Key: OAK-7376 URL: https://issues.apache.org/jira/browse/OAK-7376 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit Oak #1337 has failed. First failed run: [Jackrabbit Oak #1337|https://builds.apache.org/job/Jackrabbit%20Oak/1337/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1337/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OAK-2155) TokenAuthenticationTest#tokenCreationWithPreAuth test failing repeatedly
[
https://issues.apache.org/jira/browse/OAK-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409703#comment-16409703
]
Alex Deparvu edited comment on OAK-2155 at 3/22/18 3:21 PM:
I'll reenable this test to see if it's still failing or not
(http://svn.apache.org/viewvc?rev=1827509=rev)
was (Author: alex.parvulescu):
I'll reenable this test to see if it's still failing or not
> TokenAuthenticationTest#tokenCreationWithPreAuth test failing repeatedly
>
>
> Key: OAK-2155
> URL: https://issues.apache.org/jira/browse/OAK-2155
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, pojosr
>Reporter: Amit Jain
>Assignee: Alex Deparvu
>Priority: Major
> Labels: CI, test
>
> The test
> {{org.apache.jackrabbit.oak.run.osgi.TokenAuthenticationTest#tokenCreationWithPreAuth}}
> in oak-pojosr component failing repeatedly on the local system.
> Also, failing repeatedly on http://ci.apache.org/builders/oak-trunk-win7.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-2155) TokenAuthenticationTest#tokenCreationWithPreAuth test failing repeatedly
[
https://issues.apache.org/jira/browse/OAK-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409703#comment-16409703
]
Alex Deparvu commented on OAK-2155:
---
I'll reenable this test to see if it's still failing or not
> TokenAuthenticationTest#tokenCreationWithPreAuth test failing repeatedly
>
>
> Key: OAK-2155
> URL: https://issues.apache.org/jira/browse/OAK-2155
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, pojosr
>Reporter: Amit Jain
>Assignee: Alex Deparvu
>Priority: Major
> Labels: CI, test
>
> The test
> {{org.apache.jackrabbit.oak.run.osgi.TokenAuthenticationTest#tokenCreationWithPreAuth}}
> in oak-pojosr component failing repeatedly on the local system.
> Also, failing repeatedly on http://ci.apache.org/builders/oak-trunk-win7.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OAK-2155) TokenAuthenticationTest#tokenCreationWithPreAuth test failing repeatedly
[
https://issues.apache.org/jira/browse/OAK-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Deparvu reassigned OAK-2155:
-
Assignee: Alex Deparvu (was: Chetan Mehrotra)
> TokenAuthenticationTest#tokenCreationWithPreAuth test failing repeatedly
>
>
> Key: OAK-2155
> URL: https://issues.apache.org/jira/browse/OAK-2155
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, pojosr
>Reporter: Amit Jain
>Assignee: Alex Deparvu
>Priority: Major
> Labels: CI, test
>
> The test
> {{org.apache.jackrabbit.oak.run.osgi.TokenAuthenticationTest#tokenCreationWithPreAuth}}
> in oak-pojosr component failing repeatedly on the local system.
> Also, failing repeatedly on http://ci.apache.org/builders/oak-trunk-win7.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7373) Build failure: OutOfMemoryError
[ https://issues.apache.org/jira/browse/OAK-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409676#comment-16409676 ] Hudson commented on OAK-7373: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #1336|https://builds.apache.org/job/Jackrabbit%20Oak/1336/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1336/console] > Build failure: OutOfMemoryError > --- > > Key: OAK-7373 > URL: https://issues.apache.org/jira/browse/OAK-7373 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1334 has failed. > First failed run: [Jackrabbit Oak > #1334|https://builds.apache.org/job/Jackrabbit%20Oak/1334/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1334/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-5644) Test failure: LargeOperationIT (unable to create new native thread)
[
https://issues.apache.org/jira/browse/OAK-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Deparvu resolved OAK-5644.
---
Resolution: Cannot Reproduce
> Test failure: LargeOperationIT (unable to create new native thread)
> ---
>
> Key: OAK-5644
> URL: https://issues.apache.org/jira/browse/OAK-5644
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: continuous integration, jcr
>Affects Versions: 1.2.23
>Reporter: Hudson
>Priority: Major
> Labels: test-failure, ubuntu
> Attachments: Build 1420 logs.zip
>
>
> 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=integrationTesting #1420 has failed.
> First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK
> 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting
> #1420|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1420/]
> [console
> log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1420/console]
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.02 sec <<<
> FAILURE!
> initializationError(org.apache.jackrabbit.oak.jcr.LargeOperationIT) Time
> elapsed: 0.002 sec <<< ERROR!
> java.lang.OutOfMemoryError: unable to create new native thread
> at java.lang.Thread.start0(Native Method)
> at java.lang.Thread.start(Thread.java:714)
> at com.mongodb.Mongo.(Mongo.java:326)
> at com.mongodb.Mongo.(Mongo.java:304)
> at com.mongodb.MongoClient.(MongoClient.java:253)
> at
> org.apache.jackrabbit.oak.plugins.document.util.MongoConnection.(MongoConnection.java:45)
> at
> org.apache.jackrabbit.oak.jcr.NodeStoreFixture$DocumentFixture.createNodeStore(NodeStoreFixture.java:180)
> at
> org.apache.jackrabbit.oak.jcr.NodeStoreFixture$DocumentFixture.isAvailable(NodeStoreFixture.java:211)
> at
> org.apache.jackrabbit.oak.jcr.LargeOperationIT.fixtures(LargeOperationIT.java:146)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OAK-5534) Build timed out
[ https://issues.apache.org/jira/browse/OAK-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Deparvu resolved OAK-5534. --- Resolution: Cannot Reproduce > Build timed out > --- > > Key: OAK-5534 > URL: https://issues.apache.org/jira/browse/OAK-5534 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > Labels: CI, test-failure, ubuntu > Fix For: 1.0.43 > > Attachments: console-1432-document-rdb.txt, console-1432-segment.txt, > console.txt > > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1384 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting > #1384|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OAK-5534) Build timed out
[ https://issues.apache.org/jira/browse/OAK-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Deparvu closed OAK-5534. - > Build timed out > --- > > Key: OAK-5534 > URL: https://issues.apache.org/jira/browse/OAK-5534 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > Labels: CI, test-failure, ubuntu > Fix For: 1.0.43 > > Attachments: console-1432-document-rdb.txt, console-1432-segment.txt, > console.txt > > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1384 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting > #1384|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1384/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7375) Wrong full text parsing in Oak Solr index with boolean operators
[ https://issues.apache.org/jira/browse/OAK-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved OAK-7375. -- Resolution: Fixed Fix Version/s: 1.8.3 fixed in trunk (r1827486), 1.8 (r1827493), 1.6 (r1827497). > Wrong full text parsing in Oak Solr index with boolean operators > > > Key: OAK-7375 > URL: https://issues.apache.org/jira/browse/OAK-7375 > Project: Jackrabbit Oak > Issue Type: Bug > Components: solr >Affects Versions: 1.8.2 >Reporter: Tommaso Teofili >Assignee: Tommaso Teofili >Priority: Major > Fix For: 1.9.0, 1.8.3, 1.6.11 > > > Parsing of JCR full text clauses in Solr index has a bug so that queries like > _'foo AND bar'_ get translated into Solr queries like _'field:foo AND > field:AND AND field:bar'_. The _field:AND_ clause is the problematic one > because _AND_ is a protected operator in the Lucene / Solr syntax and > therefore needs to be either escaped or put into quotes. > However the right fix would be to skip including the _AND_ (and _OR_) terms > in the fielded query below. > So the JCR query _/jcr:root//*[jcr:contains(., 'foo AND bar')]_ should be > converted into _'field:foo AND field:bar'_. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7352) Build failure: ExecutionException: Invalid object ID
[ https://issues.apache.org/jira/browse/OAK-7352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Deparvu updated OAK-7352: -- Summary: Build failure: ExecutionException: Invalid object ID (was: Build Jackrabbit Oak #1316 failed) > Build failure: ExecutionException: Invalid object ID > > > Key: OAK-7352 > URL: https://issues.apache.org/jira/browse/OAK-7352 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1316 has failed. > First failed run: [Jackrabbit Oak > #1316|https://builds.apache.org/job/Jackrabbit%20Oak/1316/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1316/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7373) Build failure: OutOfMemoryError
[ https://issues.apache.org/jira/browse/OAK-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Deparvu updated OAK-7373: -- Summary: Build failure: OutOfMemoryError (was: Build Jackrabbit Oak #1334 failed) > Build failure: OutOfMemoryError > --- > > Key: OAK-7373 > URL: https://issues.apache.org/jira/browse/OAK-7373 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1334 has failed. > First failed run: [Jackrabbit Oak > #1334|https://builds.apache.org/job/Jackrabbit%20Oak/1334/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1334/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7373) Build Jackrabbit Oak #1334 failed
[ https://issues.apache.org/jira/browse/OAK-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409514#comment-16409514 ] Hudson commented on OAK-7373: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #1335|https://builds.apache.org/job/Jackrabbit%20Oak/1335/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1335/console] > Build Jackrabbit Oak #1334 failed > - > > Key: OAK-7373 > URL: https://issues.apache.org/jira/browse/OAK-7373 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1334 has failed. > First failed run: [Jackrabbit Oak > #1334|https://builds.apache.org/job/Jackrabbit%20Oak/1334/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1334/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7375) Wrong full text parsing in Oak Solr index with boolean operators
Tommaso Teofili created OAK-7375: Summary: Wrong full text parsing in Oak Solr index with boolean operators Key: OAK-7375 URL: https://issues.apache.org/jira/browse/OAK-7375 Project: Jackrabbit Oak Issue Type: Bug Components: solr Affects Versions: 1.8.2 Reporter: Tommaso Teofili Assignee: Tommaso Teofili Fix For: 1.9.0, 1.6.11 Parsing of JCR full text clauses in Solr index has a bug so that queries like _'foo AND bar'_ get translated into Solr queries like _'field:foo AND field:AND AND field:bar'_. The _field:AND_ clause is the problematic one because _AND_ is a protected operator in the Lucene / Solr syntax and therefore needs to be either escaped or put into quotes. However the right fix would be to skip including the _AND_ (and _OR_) terms in the fielded query below. So the JCR query _/jcr:root//*[jcr:contains(., 'foo AND bar')]_ should be converted into _'field:foo AND field:bar'_. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7374) Investigate changing the UUID generation algorithm / format to reduce index size, improve speed
[ https://issues.apache.org/jira/browse/OAK-7374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-7374: Component/s: core > Investigate changing the UUID generation algorithm / format to reduce index > size, improve speed > --- > > Key: OAK-7374 > URL: https://issues.apache.org/jira/browse/OAK-7374 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Thomas Mueller >Assignee: Thomas Mueller >Priority: Major > Fix For: 1.10 > > > UUIDs are currently randomly generated, which is bad for indexing; specially > read and writes access, due to low locality. > If we could add a time component, I think the index churn (amount of writes) > would shrink, and lookup would be faster. > It should be fairly easy to verify if that's really true (create a > proof-of-concept, and measure). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7374) Investigate changing the UUID generation algorithm / format to reduce index size, improve speed
Thomas Mueller created OAK-7374: --- Summary: Investigate changing the UUID generation algorithm / format to reduce index size, improve speed Key: OAK-7374 URL: https://issues.apache.org/jira/browse/OAK-7374 Project: Jackrabbit Oak Issue Type: Improvement Reporter: Thomas Mueller Assignee: Thomas Mueller Fix For: 1.10 UUIDs are currently randomly generated, which is bad for indexing; specially read and writes access, due to low locality. If we could add a time component, I think the index churn (amount of writes) would shrink, and lookup would be faster. It should be fairly easy to verify if that's really true (create a proof-of-concept, and measure). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7373) Build Jackrabbit Oak #1334 failed
Hudson created OAK-7373: --- Summary: Build Jackrabbit Oak #1334 failed Key: OAK-7373 URL: https://issues.apache.org/jira/browse/OAK-7373 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit Oak #1334 has failed. First failed run: [Jackrabbit Oak #1334|https://builds.apache.org/job/Jackrabbit%20Oak/1334/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1334/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7338) Javadocs for the org.apache.jackrabbit.oak.segment.spi
[ https://issues.apache.org/jira/browse/OAK-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409392#comment-16409392 ] Tomek Rękawek commented on OAK-7338: Updated javadocs in [r1827478|https://svn.apache.org/r1827478]. [~mduerig], [~frm] - I'd appreciate feedback on these. > Javadocs for the org.apache.jackrabbit.oak.segment.spi > -- > > Key: OAK-7338 > URL: https://issues.apache.org/jira/browse/OAK-7338 > Project: Jackrabbit Oak > Issue Type: Task > Components: doc, segment-tar >Reporter: Tomek Rękawek >Assignee: Tomek Rękawek >Priority: Major > Fix For: 1.9.0, 1.10 > > > Add Javadoc to the public methods and classes in > org.apache.jackrabbit.oak.segment.spi.* describing the general contracts and > relevant post conditions, pre conditions dependencies and invariants. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7338) Javadocs for the org.apache.jackrabbit.oak.segment.spi
[ https://issues.apache.org/jira/browse/OAK-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomek Rękawek resolved OAK-7338. Resolution: Fixed Fix Version/s: 1.9.0 > Javadocs for the org.apache.jackrabbit.oak.segment.spi > -- > > Key: OAK-7338 > URL: https://issues.apache.org/jira/browse/OAK-7338 > Project: Jackrabbit Oak > Issue Type: Task > Components: doc, segment-tar >Reporter: Tomek Rękawek >Assignee: Tomek Rękawek >Priority: Major > Fix For: 1.9.0, 1.10 > > > Add Javadoc to the public methods and classes in > org.apache.jackrabbit.oak.segment.spi.* describing the general contracts and > relevant post conditions, pre conditions dependencies and invariants. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7338) Javadocs for the org.apache.jackrabbit.oak.segment.spi
[ https://issues.apache.org/jira/browse/OAK-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomek Rękawek updated OAK-7338: --- Component/s: (was: segmentmk) segment-tar > Javadocs for the org.apache.jackrabbit.oak.segment.spi > -- > > Key: OAK-7338 > URL: https://issues.apache.org/jira/browse/OAK-7338 > Project: Jackrabbit Oak > Issue Type: Task > Components: doc, segment-tar >Reporter: Tomek Rękawek >Assignee: Tomek Rękawek >Priority: Major > Fix For: 1.9.0, 1.10 > > > Add Javadoc to the public methods and classes in > org.apache.jackrabbit.oak.segment.spi.* describing the general contracts and > relevant post conditions, pre conditions dependencies and invariants. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OAK-7338) Javadocs for the org.apache.jackrabbit.oak.segment.spi
[ https://issues.apache.org/jira/browse/OAK-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomek Rękawek reassigned OAK-7338: -- Assignee: Tomek Rękawek > Javadocs for the org.apache.jackrabbit.oak.segment.spi > -- > > Key: OAK-7338 > URL: https://issues.apache.org/jira/browse/OAK-7338 > Project: Jackrabbit Oak > Issue Type: Task > Components: doc, segmentmk >Reporter: Tomek Rękawek >Assignee: Tomek Rękawek >Priority: Major > Fix For: 1.10 > > > Add Javadoc to the public methods and classes in > org.apache.jackrabbit.oak.segment.spi.* describing the general contracts and > relevant post conditions, pre conditions dependencies and invariants. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-6770) Convert oak-segment-tar to OSGi R6 annotations
[
https://issues.apache.org/jira/browse/OAK-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409333#comment-16409333
]
Robert Munteanu commented on OAK-6770:
--
The provisioning model works fine for defining variables, but the problem we're
facing with that is that variables are defined at build time. So imagine we
have a setting like
{noformat}
[variables]
sling.home=sling
[configurations]
org.apache.jackrabbit.foo
location=${sling.home}/foo
org.apache.jackrabbit.bar
location=${sling.home}/bar
{noformat}
The sling.home setting is set in stone to be {{sling}} and I can't change it at
runtime. In contrast, framework properties can be set at runtime so having
{{org.apache.jackrabbit.bar}} inspect the {{sling.home}} framework property is
quite beneficial.
For that reason I'd argue for allowing a fallback to the framework properties
in Oak components.
> Convert oak-segment-tar to OSGi R6 annotations
> --
>
> Key: OAK-6770
> URL: https://issues.apache.org/jira/browse/OAK-6770
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: segment-tar
>Reporter: Robert Munteanu
>Assignee: Francesco Mari
>Priority: Minor
> Labels: osgi
> Fix For: 1.10
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OAK-7354) Test failure ExternalIdentityImporterTest.importExternalUserWithPrincipalNames
[
https://issues.apache.org/jira/browse/OAK-7354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Deparvu resolved OAK-7354.
---
Resolution: Fixed
found a diff to the default setup, changed it with
http://svn.apache.org/viewvc?rev=1827473=rev
> Test failure ExternalIdentityImporterTest.importExternalUserWithPrincipalNames
> --
>
> Key: OAK-7354
> URL: https://issues.apache.org/jira/browse/OAK-7354
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: auth-external, continuous integration
>Reporter: Hudson
>Assignee: Alex Deparvu
>Priority: Major
> Fix For: 1.9.0, 1.10
>
>
> The build Jackrabbit Oak #1318 has failed.
> First failed run: [Jackrabbit Oak
> #1318|https://builds.apache.org/job/Jackrabbit%20Oak/1318/] [console
> log|https://builds.apache.org/job/Jackrabbit%20Oak/1318/console]
> {noformat}Test results:
> 2 tests failed.
> FAILED:
> org.apache.jackrabbit.oak.spi.security.authentication.external.impl.principal.ExternalIdentityImporterTest.importExternalUserWithPrincipalNames
> Error Message:
> Node with the same UUID exists:/rep:security/rep:authorizables/rep:users/t: {
> jcr:primaryType = rep:AuthorizableFolder, t7 = { ... }}
> Stack Trace:
> javax.jcr.ItemExistsException: Node with the same UUID
> exists:/rep:security/rep:authorizables/rep:users/t: { jcr:primaryType =
> rep:AuthorizableFolder, t7 = { ... }}
> at
> org.apache.jackrabbit.oak.spi.security.authentication.external.impl.principal.ExternalIdentityImporterTest.doImport(ExternalIdentityImporterTest.java:132)
> at
> org.apache.jackrabbit.oak.spi.security.authentication.external.impl.principal.ExternalIdentityImporterTest.importExternalUserWithPrincipalNames(ExternalIdentityImporterTest.java:167)
> FAILED:
> org.apache.jackrabbit.oak.spi.security.authentication.external.impl.principal.ExternalIdentityImporterTest.importExternalUser
> Error Message:
> Node with the same UUID exists:/rep:security/rep:authorizables/rep:users/t: {
> jcr:primaryType = rep:AuthorizableFolder, tt = { ... }}
> Stack Trace:
> javax.jcr.ItemExistsException: Node with the same UUID
> exists:/rep:security/rep:authorizables/rep:users/t: { jcr:primaryType =
> rep:AuthorizableFolder, tt = { ... }}
> at
> org.apache.jackrabbit.oak.spi.security.authentication.external.impl.principal.ExternalIdentityImporterTest.doImport(ExternalIdentityImporterTest.java:132)
> at
> org.apache.jackrabbit.oak.spi.security.authentication.external.impl.principal.ExternalIdentityImporterTest.importExternalUser(ExternalIdentityImporterTest.java:153)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OAK-7372) Update FileDataStore recommendation
Marcel Reutegger created OAK-7372: - Summary: Update FileDataStore recommendation Key: OAK-7372 URL: https://issues.apache.org/jira/browse/OAK-7372 Project: Jackrabbit Oak Issue Type: Documentation Components: doc Reporter: Marcel Reutegger Fix For: 1.10 The BlobStore documentation currently mentions use of a FileDataStore only for deployments when the data store is shared between multiple repository instances. The documentation should be updated to also recommend the FileDataStore when a repository has many binaries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7356) CugConfiguration may not pick up CugExclude
[
https://issues.apache.org/jira/browse/OAK-7356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved OAK-7356.
-
Resolution: Fixed
Committed revision 1827472.
> CugConfiguration may not pick up CugExclude
> ---
>
> Key: OAK-7356
> URL: https://issues.apache.org/jira/browse/OAK-7356
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: authorization-cug
>Reporter: angela
>Assignee: angela
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7356-2.patch, OAK-7356.patch
>
>
> It seems that the {{CugConfiguration}} may under some circumstances not
> properly pick up the {{CugExclude}}, which results in the
> {{CugConfiguration}} falling back to the default, that only excludes the
> {{AdminPrincipal}}, {{SystemPrincipal}} and {{SystemUserPrincipals}} from CUG
> evaluation.
> In order to address the issue without disrupting the default setup, I would
> like to propose the following changes:
> - {{CugConfiguration}}: Change reference cardinality of the the
> {{CugExclude}} from {{ReferenceCardinality.OPTIONAL_UNARY}} to
> {{ReferenceCardinality.MANDATORY_UNARY}}
> - {{CugExcludeImpl}}: Don't require an explicit configuration (i.e. drop
> {{ConfigurationPolicy.REQUIRE}}). Since it extends from
> {{CugExclude.Default}} the default behavior in absense of a configured set of
> principal names will be equivalent to the intended default in
> {{CugConfiguration}} with the optional reference.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7356) CugConfiguration may not pick up CugExclude
[
https://issues.apache.org/jira/browse/OAK-7356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409250#comment-16409250
]
angela commented on OAK-7356:
-
[~stillalex], probably better to tack that separately...
> CugConfiguration may not pick up CugExclude
> ---
>
> Key: OAK-7356
> URL: https://issues.apache.org/jira/browse/OAK-7356
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: authorization-cug
>Reporter: angela
>Assignee: angela
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7356-2.patch, OAK-7356.patch
>
>
> It seems that the {{CugConfiguration}} may under some circumstances not
> properly pick up the {{CugExclude}}, which results in the
> {{CugConfiguration}} falling back to the default, that only excludes the
> {{AdminPrincipal}}, {{SystemPrincipal}} and {{SystemUserPrincipals}} from CUG
> evaluation.
> In order to address the issue without disrupting the default setup, I would
> like to propose the following changes:
> - {{CugConfiguration}}: Change reference cardinality of the the
> {{CugExclude}} from {{ReferenceCardinality.OPTIONAL_UNARY}} to
> {{ReferenceCardinality.MANDATORY_UNARY}}
> - {{CugExcludeImpl}}: Don't require an explicit configuration (i.e. drop
> {{ConfigurationPolicy.REQUIRE}}). Since it extends from
> {{CugExclude.Default}} the default behavior in absense of a configured set of
> principal names will be equivalent to the intended default in
> {{CugConfiguration}} with the optional reference.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7356) CugConfiguration may not pick up CugExclude
[
https://issues.apache.org/jira/browse/OAK-7356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409247#comment-16409247
]
Alex Deparvu commented on OAK-7356:
---
patch looks good, +1
for exposing the OSGi config I was talking about felix inventory integration
(OAK-6179). should we track this as a separate issue?
> CugConfiguration may not pick up CugExclude
> ---
>
> Key: OAK-7356
> URL: https://issues.apache.org/jira/browse/OAK-7356
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: authorization-cug
>Reporter: angela
>Assignee: angela
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7356-2.patch, OAK-7356.patch
>
>
> It seems that the {{CugConfiguration}} may under some circumstances not
> properly pick up the {{CugExclude}}, which results in the
> {{CugConfiguration}} falling back to the default, that only excludes the
> {{AdminPrincipal}}, {{SystemPrincipal}} and {{SystemUserPrincipals}} from CUG
> evaluation.
> In order to address the issue without disrupting the default setup, I would
> like to propose the following changes:
> - {{CugConfiguration}}: Change reference cardinality of the the
> {{CugExclude}} from {{ReferenceCardinality.OPTIONAL_UNARY}} to
> {{ReferenceCardinality.MANDATORY_UNARY}}
> - {{CugExcludeImpl}}: Don't require an explicit configuration (i.e. drop
> {{ConfigurationPolicy.REQUIRE}}). Since it extends from
> {{CugExclude.Default}} the default behavior in absense of a configured set of
> principal names will be equivalent to the intended default in
> {{CugConfiguration}} with the optional reference.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7356) CugConfiguration may not pick up CugExclude
[
https://issues.apache.org/jira/browse/OAK-7356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409228#comment-16409228
]
angela commented on OAK-7356:
-
[~stillalex], attached an updated patch that also fixes javadoc and the
documentation. If the {{principalNames}} config option within
{{CugExcludeImpl}} is empty, it will essentially behave the same as the
{{CugExclude.Default}}. I adjusted the description accordingly. wdyt?
> CugConfiguration may not pick up CugExclude
> ---
>
> Key: OAK-7356
> URL: https://issues.apache.org/jira/browse/OAK-7356
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: authorization-cug
>Reporter: angela
>Assignee: angela
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7356-2.patch, OAK-7356.patch
>
>
> It seems that the {{CugConfiguration}} may under some circumstances not
> properly pick up the {{CugExclude}}, which results in the
> {{CugConfiguration}} falling back to the default, that only excludes the
> {{AdminPrincipal}}, {{SystemPrincipal}} and {{SystemUserPrincipals}} from CUG
> evaluation.
> In order to address the issue without disrupting the default setup, I would
> like to propose the following changes:
> - {{CugConfiguration}}: Change reference cardinality of the the
> {{CugExclude}} from {{ReferenceCardinality.OPTIONAL_UNARY}} to
> {{ReferenceCardinality.MANDATORY_UNARY}}
> - {{CugExcludeImpl}}: Don't require an explicit configuration (i.e. drop
> {{ConfigurationPolicy.REQUIRE}}). Since it extends from
> {{CugExclude.Default}} the default behavior in absense of a configured set of
> principal names will be equivalent to the intended default in
> {{CugConfiguration}} with the optional reference.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7356) CugConfiguration may not pick up CugExclude
[
https://issues.apache.org/jira/browse/OAK-7356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-7356:
Attachment: OAK-7356-2.patch
> CugConfiguration may not pick up CugExclude
> ---
>
> Key: OAK-7356
> URL: https://issues.apache.org/jira/browse/OAK-7356
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: authorization-cug
>Reporter: angela
>Assignee: angela
>Priority: Major
> Fix For: 1.9.0, 1.10
>
> Attachments: OAK-7356-2.patch, OAK-7356.patch
>
>
> It seems that the {{CugConfiguration}} may under some circumstances not
> properly pick up the {{CugExclude}}, which results in the
> {{CugConfiguration}} falling back to the default, that only excludes the
> {{AdminPrincipal}}, {{SystemPrincipal}} and {{SystemUserPrincipals}} from CUG
> evaluation.
> In order to address the issue without disrupting the default setup, I would
> like to propose the following changes:
> - {{CugConfiguration}}: Change reference cardinality of the the
> {{CugExclude}} from {{ReferenceCardinality.OPTIONAL_UNARY}} to
> {{ReferenceCardinality.MANDATORY_UNARY}}
> - {{CugExcludeImpl}}: Don't require an explicit configuration (i.e. drop
> {{ConfigurationPolicy.REQUIRE}}). Since it extends from
> {{CugExclude.Default}} the default behavior in absense of a configured set of
> principal names will be equivalent to the intended default in
> {{CugConfiguration}} with the optional reference.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7304) Deploy oak-pojosr as part of standard deployment
[
https://issues.apache.org/jira/browse/OAK-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-7304:
-
Labels: (was: candidate_oak_1_8)
Fix Version/s: 1.8.3
Merged to 1.8 with 1827468
> Deploy oak-pojosr as part of standard deployment
>
>
> Key: OAK-7304
> URL: https://issues.apache.org/jira/browse/OAK-7304
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: pojosr
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: 1.9.0, 1.10, 1.8.3
>
>
> oak-pojosr currently has {{skip.deployment}} set to true and hence is being
> skipped from deployment. This setting should be removed
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OAK-7371) Build Jackrabbit Oak #1332 failed
[ https://issues.apache.org/jira/browse/OAK-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Deparvu resolved OAK-7371. --- Resolution: Duplicate > Build Jackrabbit Oak #1332 failed > - > > Key: OAK-7371 > URL: https://issues.apache.org/jira/browse/OAK-7371 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1332 has failed. > First failed run: [Jackrabbit Oak > #1332|https://builds.apache.org/job/Jackrabbit%20Oak/1332/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1332/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
