[jira] [Updated] (OAK-8540) Effective policies should implememt PrincipalAccessControlList

2019-08-14 Thread angela (JIRA)


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

angela updated OAK-8540:

Fix Version/s: 1.18.0

> Effective policies should implememt PrincipalAccessControlList
> --
>
> Key: OAK-8540
> URL: https://issues.apache.org/jira/browse/OAK-8540
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: authorization-principalbased
>Reporter: angela
>Assignee: angela
>Priority: Major
> Fix For: 1.18.0
>
>
> currently the policies returned upon 
> {{AccessControlManager.getEffectivePolicies(String)}} and 
> {{JackrabbitAccessControlManager.getEffectivePolicies(Set)}} are 
> instances of {{ImmutableACL}}, which doesn't reflect the fact that the 
> implementation handles {{PrincipalAccessControlList}}. This makes it a bit 
> confising to 'read' in a composite setup in particular when comparing the 
> return value of {{getPolicies}} with {{getEffectivePolicies}}.
> therefore i would suggest to introduce an extension of {{ImmutableACL}} 
> implementing {{PrincipalAccessControlList}} and using this for the return 
> value of both methods covering effective policies.
> [~stillalex], fyi



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Created] (OAK-8540) Effective policies should implememt PrincipalAccessControlList

2019-08-14 Thread angela (JIRA)
angela created OAK-8540:
---

 Summary: Effective policies should implememt 
PrincipalAccessControlList
 Key: OAK-8540
 URL: https://issues.apache.org/jira/browse/OAK-8540
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: authorization-principalbased
Reporter: angela
Assignee: angela


currently the policies returned upon 
{{AccessControlManager.getEffectivePolicies(String)}} and 
{{JackrabbitAccessControlManager.getEffectivePolicies(Set)}} are 
instances of {{ImmutableACL}}, which doesn't reflect the fact that the 
implementation handles {{PrincipalAccessControlList}}. This makes it a bit 
confising to 'read' in a composite setup in particular when comparing the 
return value of {{getPolicies}} with {{getEffectivePolicies}}.
therefore i would suggest to introduce an extension of {{ImmutableACL}} 
implementing {{PrincipalAccessControlList}} and using this for the return value 
of both methods covering effective policies.

[~stillalex], fyi



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (OAK-8540) Effective policies should implememt PrincipalAccessControlList

2019-08-14 Thread angela (JIRA)


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

angela resolved OAK-8540.
-
Resolution: Fixed

Committed revision 1865092.


> Effective policies should implememt PrincipalAccessControlList
> --
>
> Key: OAK-8540
> URL: https://issues.apache.org/jira/browse/OAK-8540
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: authorization-principalbased
>Reporter: angela
>Assignee: angela
>Priority: Major
> Fix For: 1.18.0
>
>
> currently the policies returned upon 
> {{AccessControlManager.getEffectivePolicies(String)}} and 
> {{JackrabbitAccessControlManager.getEffectivePolicies(Set)}} are 
> instances of {{ImmutableACL}}, which doesn't reflect the fact that the 
> implementation handles {{PrincipalAccessControlList}}. This makes it a bit 
> confising to 'read' in a composite setup in particular when comparing the 
> return value of {{getPolicies}} with {{getEffectivePolicies}}.
> therefore i would suggest to introduce an extension of {{ImmutableACL}} 
> implementing {{PrincipalAccessControlList}} and using this for the return 
> value of both methods covering effective policies.
> [~stillalex], fyi



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (OAK-8538) Incomplete recovery on long running merge with branch commits

2019-08-14 Thread Marcel Reutegger (JIRA)


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

Marcel Reutegger resolved OAK-8538.
---
   Resolution: Fixed
Fix Version/s: 1.18.0

Fixed in trunk: http://svn.apache.org/r1865110

The recovery process now checks for branch commits that happened before the 
current {{_lastRev}} and were merged after it. Those are the problematic 
changes that must be included in the recovery as well.

> Incomplete recovery on long running merge with branch commits
> -
>
> Key: OAK-8538
> URL: https://issues.apache.org/jira/browse/OAK-8538
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: documentmk
>Affects Versions: 1.16.0
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Major
> Fix For: 1.18.0
>
>
> Recovery of a crashed cluster node that was unable to run a background update 
> after a long running merge with branch commits is incomplete. The recovery 
> will use a start date for the candidate documents that is too recent and not 
> take all the documents of the branch commits into account.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (OAK-8538) Incomplete recovery on long running merge with branch commits

2019-08-14 Thread Marcel Reutegger (JIRA)


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

Marcel Reutegger commented on OAK-8538:
---

Added ignored tests: http://svn.apache.org/r1865108

> Incomplete recovery on long running merge with branch commits
> -
>
> Key: OAK-8538
> URL: https://issues.apache.org/jira/browse/OAK-8538
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: documentmk
>Affects Versions: 1.16.0
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Major
>
> Recovery of a crashed cluster node that was unable to run a background update 
> after a long running merge with branch commits is incomplete. The recovery 
> will use a start date for the candidate documents that is too recent and not 
> take all the documents of the branch commits into account.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Created] (OAK-8541) AbstractRestrictionProvider.createRestriction : Include restriction name in error message

2019-08-14 Thread angela (JIRA)
angela created OAK-8541:
---

 Summary: AbstractRestrictionProvider.createRestriction : Include 
restriction name in error message
 Key: OAK-8541
 URL: https://issues.apache.org/jira/browse/OAK-8541
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: security-spi
Reporter: angela
Assignee: angela
 Fix For: 1.18.0


when calling {{AbstractRestrictionProvider.createRestriction}} with value 
cardinality mismatch or values of the wrong type, the error message of the 
{{AccessControlException}} doesn't indicate the name of restrictions causing 
the error.

[~stillalex], fyi



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (OAK-8531) Reading Azure Journal File while it's modified fails

2019-08-14 Thread Andrei Dulceanu (JIRA)


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

Andrei Dulceanu commented on OAK-8531:
--

[~tomek.rekawek], I was able to consistently reproduce the behaviour with a 
slightly changed version of your IT,  [^AzureJournalFileCouncurrencyITv2.java]. 
The only thing remaining now is that this test fails, although it shouldn't, 
when the {{AZURE_CONNECTION}} environment variable is not set:

{noformat}
[INFO] Running 
org.apache.jackrabbit.oak.segment.azure.AzureJournalFileConcurrencyIT
[ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.09 s 
<<< FAILURE! - in 
org.apache.jackrabbit.oak.segment.azure.AzureJournalFileConcurrencyIT
[ERROR] org.apache.jackrabbit.oak.segment.azure.AzureJournalFileConcurrencyIT  
Time elapsed: 0.089 s  <<< ERROR!
org.junit.AssumptionViolatedException: got: <[null]>, expected: every item is 
not null
at 
org.apache.jackrabbit.oak.segment.azure.AzureJournalFileConcurrencyIT.connectToAzure(AzureJournalFileConcurrencyIT.java:54)

[ERROR] org.apache.jackrabbit.oak.segment.azure.AzureJournalFileConcurrencyIT  
Time elapsed: 0.09 s  <<< ERROR!
java.lang.NullPointerException
at 
org.apache.jackrabbit.oak.segment.azure.AzureJournalFileConcurrencyIT.cleanupContainer(AzureJournalFileConcurrencyIT.java:70)
{noformat}

I'm running this with Java 8:

{noformat}
java version "1.8.0_181"
Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
{noformat}

> Reading Azure Journal File while it's modified fails
> 
>
> Key: OAK-8531
> URL: https://issues.apache.org/jira/browse/OAK-8531
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: segment-azure
>Affects Versions: 1.16.0
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Major
> Attachments: AzureJournalFileConcurrencyIT.java, 
> AzureJournalFileCouncurrencyITv2.java, OAK-8531.patch
>
>
> Trying to read the Azure Journal File while it's modified triggers the 
> following exception:
> {noformat}
> java.io.IOException: com.microsoft.azure.storage.StorageException: The 
> condition specified using HTTP conditional header(s) is not met.
> ! at 
> org.apache.jackrabbit.oak.segment.azure.ReverseFileReader.readBlock(ReverseFileReader.java:70)
> ! at 
> org.apache.jackrabbit.oak.segment.azure.ReverseFileReader.readLine(ReverseFileReader.java:96)
> ! at 
> org.apache.jackrabbit.oak.segment.azure.AzureJournalFile$AzureJournalReader.readLine(AzureJournalFile.java:126)
> ! at 
> org.apache.jackrabbit.oak.segment.azure.AzureJournalFile$CombinedReader.readLine(AzureJournalFile.java:240)
> ! at 
> org.apache.jackrabbit.oak.segment.azure.tool.SegmentStoreMigrator.migrateJournal(SegmentStoreMigrator.java:99)
> ! at 
> org.apache.jackrabbit.oak.segment.azure.tool.SegmentStoreMigrator.migrate(SegmentStoreMigrator.java:84)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (OAK-8531) Reading Azure Journal File while it's modified fails

2019-08-14 Thread Andrei Dulceanu (JIRA)


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

Andrei Dulceanu updated OAK-8531:
-
Attachment: AzureJournalFileCouncurrencyITv2.java

> Reading Azure Journal File while it's modified fails
> 
>
> Key: OAK-8531
> URL: https://issues.apache.org/jira/browse/OAK-8531
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: segment-azure
>Affects Versions: 1.16.0
>Reporter: Andrei Dulceanu
>Assignee: Andrei Dulceanu
>Priority: Major
> Attachments: AzureJournalFileConcurrencyIT.java, 
> AzureJournalFileCouncurrencyITv2.java, OAK-8531.patch
>
>
> Trying to read the Azure Journal File while it's modified triggers the 
> following exception:
> {noformat}
> java.io.IOException: com.microsoft.azure.storage.StorageException: The 
> condition specified using HTTP conditional header(s) is not met.
> ! at 
> org.apache.jackrabbit.oak.segment.azure.ReverseFileReader.readBlock(ReverseFileReader.java:70)
> ! at 
> org.apache.jackrabbit.oak.segment.azure.ReverseFileReader.readLine(ReverseFileReader.java:96)
> ! at 
> org.apache.jackrabbit.oak.segment.azure.AzureJournalFile$AzureJournalReader.readLine(AzureJournalFile.java:126)
> ! at 
> org.apache.jackrabbit.oak.segment.azure.AzureJournalFile$CombinedReader.readLine(AzureJournalFile.java:240)
> ! at 
> org.apache.jackrabbit.oak.segment.azure.tool.SegmentStoreMigrator.migrateJournal(SegmentStoreMigrator.java:99)
> ! at 
> org.apache.jackrabbit.oak.segment.azure.tool.SegmentStoreMigrator.migrate(SegmentStoreMigrator.java:84)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (OAK-8541) AbstractRestrictionProvider.createRestriction : Include restriction name in error message

2019-08-14 Thread angela (JIRA)


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

angela resolved OAK-8541.
-
Resolution: Fixed

Committed revision 1865112.


> AbstractRestrictionProvider.createRestriction : Include restriction name in 
> error message
> -
>
> Key: OAK-8541
> URL: https://issues.apache.org/jira/browse/OAK-8541
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: security-spi
>Reporter: angela
>Assignee: angela
>Priority: Trivial
> Fix For: 1.18.0
>
>
> when calling {{AbstractRestrictionProvider.createRestriction}} with value 
> cardinality mismatch or values of the wrong type, the error message of the 
> {{AccessControlException}} doesn't indicate the name of restrictions causing 
> the error.
> [~stillalex], fyi



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (OAK-8542) Test failure: ConcurrentCopyOnReadDirectoryTest.concurrentPrefetchWithTimeout

2019-08-14 Thread Marcel Reutegger (JIRA)


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

Marcel Reutegger updated OAK-8542:
--
Summary: Test failure: 
ConcurrentCopyOnReadDirectoryTest.concurrentPrefetchWithTimeout  (was: Build 
Jackrabbit Oak #2318 failed)

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



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (OAK-8511) Build Jackrabbit Oak #2299 failed

2019-08-14 Thread Marcel Reutegger (JIRA)


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

Marcel Reutegger resolved OAK-8511.
---
Resolution: Duplicate

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



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Closed] (OAK-8511) Build Jackrabbit Oak #2299 failed

2019-08-14 Thread Marcel Reutegger (JIRA)


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

Marcel Reutegger closed OAK-8511.
-

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



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (OAK-8513) Concurrent index access via CopyOnRead directory can lead to reading directly off of remote

2019-08-14 Thread Thomas Mueller (JIRA)


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

Thomas Mueller commented on OAK-8513:
-

[~catholicon] sorry for the late review! Just saw it now. The logic seems 
correct, as we discussed. I think it's OK to ignore the interrupted exception 
for now.

> Concurrent index access via CopyOnRead directory can lead to reading directly 
> off of remote
> ---
>
> Key: OAK-8513
> URL: https://issues.apache.org/jira/browse/OAK-8513
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: lucene
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
>Priority: Major
> Fix For: 1.18.0
>
>
> Even with prefetch enabled having 2 CopyOnRead directories pointing to same 
> index can lead to one of the instance reading index files directly off of 
> remote index.
> The reason this happens is because {{COR#copyFilesToLocal}} explicitly 
> chooses to work with remote if index copier reports that a copy is in 
> progress.
> This wasn't a problem earlier when COR was only used via IndexTracker so 
> concurrent COR instances weren't expected (COR's avoid local for conc copy 
> was probably worried about non-prefetch case).
> But with OAK-8097, {{DefaultDirectoryFactory}} also uses COR to bring the 
> files. Which means that if there's a query against an index which is getting 
> updated as well then either of COR instance could read directly from remote.
> The condition should only be relevant during early app start up but since 
> this can happen in default configuration, we should attempt to fix this.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Created] (OAK-8542) Build Jackrabbit Oak #2318 failed

2019-08-14 Thread Hudson (JIRA)
Hudson created OAK-8542:
---

 Summary: Build Jackrabbit Oak #2318 failed
 Key: OAK-8542
 URL: https://issues.apache.org/jira/browse/OAK-8542
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: continuous integration
Reporter: Hudson


No description is provided

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



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Closed] (OAK-8527) Build Jackrabbit Oak #2308 failed

2019-08-14 Thread Marcel Reutegger (JIRA)


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

Marcel Reutegger closed OAK-8527.
-

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



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (OAK-8527) Build Jackrabbit Oak #2308 failed

2019-08-14 Thread Marcel Reutegger (JIRA)


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

Marcel Reutegger resolved OAK-8527.
---
Resolution: Duplicate

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



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (OAK-8542) Test failure: ConcurrentCopyOnReadDirectoryTest.concurrentPrefetchWithTimeout

2019-08-14 Thread Marcel Reutegger (JIRA)


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

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

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

{noformat}
java.lang.NullPointerException
at 
org.apache.jackrabbit.oak.plugins.index.lucene.directory.ConcurrentCopyOnReadDirectoryTest.concurrentPrefetchWithTimeout(ConcurrentCopyOnReadDirectoryTest.java:154)
{noformat}

  was:
No description is provided

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

Component/s: lucene

[~catholicon], it looks like this test was added for OAK-8513. I'm able to 
reproduce this issue when I let my IDE run the tests in this class in a loop. 
After a few iterations, the test then fails with the NPE.

> Test failure: ConcurrentCopyOnReadDirectoryTest.concurrentPrefetchWithTimeout
> -
>
> Key: OAK-8542
> URL: https://issues.apache.org/jira/browse/OAK-8542
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, lucene
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #2318 has failed.
> First failed run: [Jackrabbit Oak 
> #2318|https://builds.apache.org/job/Jackrabbit%20Oak/2318/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/2318/console]
> {noformat}
> java.lang.NullPointerException
>   at 
> org.apache.jackrabbit.oak.plugins.index.lucene.directory.ConcurrentCopyOnReadDirectoryTest.concurrentPrefetchWithTimeout(ConcurrentCopyOnReadDirectoryTest.java:154)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (OAK-8516) Build Jackrabbit Oak #2302 failed

2019-08-14 Thread Marcel Reutegger (JIRA)


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

Marcel Reutegger resolved OAK-8516.
---
Resolution: Duplicate

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



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Closed] (OAK-8516) Build Jackrabbit Oak #2302 failed

2019-08-14 Thread Marcel Reutegger (JIRA)


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

Marcel Reutegger closed OAK-8516.
-

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



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Assigned] (OAK-8542) Test failure: ConcurrentCopyOnReadDirectoryTest.concurrentPrefetchWithTimeout

2019-08-14 Thread Vikas Saurabh (JIRA)


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

Vikas Saurabh reassigned OAK-8542:
--

Assignee: Vikas Saurabh

> Test failure: ConcurrentCopyOnReadDirectoryTest.concurrentPrefetchWithTimeout
> -
>
> Key: OAK-8542
> URL: https://issues.apache.org/jira/browse/OAK-8542
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, lucene
>Reporter: Hudson
>Assignee: Vikas Saurabh
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #2318 has failed.
> First failed run: [Jackrabbit Oak 
> #2318|https://builds.apache.org/job/Jackrabbit%20Oak/2318/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/2318/console]
> {noformat}
> java.lang.NullPointerException
>   at 
> org.apache.jackrabbit.oak.plugins.index.lucene.directory.ConcurrentCopyOnReadDirectoryTest.concurrentPrefetchWithTimeout(ConcurrentCopyOnReadDirectoryTest.java:154)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (OAK-8542) Test failure: ConcurrentCopyOnReadDirectoryTest.concurrentPrefetchWithTimeout

2019-08-14 Thread Vikas Saurabh (JIRA)


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

Vikas Saurabh resolved OAK-8542.

   Resolution: Fixed
Fix Version/s: 1.18.0

Thanks for looking into it [~mreutegg]. Fixed incorrectly initialized list that 
was failing the test at [r1865136|https://svn.apache.org/r1865136].

> Test failure: ConcurrentCopyOnReadDirectoryTest.concurrentPrefetchWithTimeout
> -
>
> Key: OAK-8542
> URL: https://issues.apache.org/jira/browse/OAK-8542
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration, lucene
>Reporter: Hudson
>Assignee: Vikas Saurabh
>Priority: Major
> Fix For: 1.18.0
>
>
> No description is provided
> The build Jackrabbit Oak #2318 has failed.
> First failed run: [Jackrabbit Oak 
> #2318|https://builds.apache.org/job/Jackrabbit%20Oak/2318/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/2318/console]
> {noformat}
> java.lang.NullPointerException
>   at 
> org.apache.jackrabbit.oak.plugins.index.lucene.directory.ConcurrentCopyOnReadDirectoryTest.concurrentPrefetchWithTimeout(ConcurrentCopyOnReadDirectoryTest.java:154)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Created] (OAK-8543) Javadoc of IndexCopier#waitForCopyCompletion refers to boolean return

2019-08-14 Thread Vikas Saurabh (JIRA)
Vikas Saurabh created OAK-8543:
--

 Summary: Javadoc of IndexCopier#waitForCopyCompletion refers to 
boolean return
 Key: OAK-8543
 URL: https://issues.apache.org/jira/browse/OAK-8543
 Project: Jackrabbit Oak
  Issue Type: Documentation
  Components: lucene
Reporter: Vikas Saurabh
Assignee: Vikas Saurabh


As noted by [~frm] at https://twitter.com/frm1025/status/1161640994787536896, 
javadoc of {{IndexCopier#waitForCopyCompletion}} shouldn't talk about false 
return when the method returns void.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)