[jira] [Created] (OAK-8167) Facet count with statistical mode should cover the case where whole facet results are not accessible

2019-03-25 Thread Kelvin Xu (JIRA)
Kelvin Xu created OAK-8167:
--

 Summary: Facet count with statistical mode should cover the case 
where whole facet results are not accessible
 Key: OAK-8167
 URL: https://issues.apache.org/jira/browse/OAK-8167
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: indexing, lucene, query
Affects Versions: 1.6.16
Reporter: Kelvin Xu


With the statistical mode, facet count is updated proportionally to the 
percentage of accessible samples, which works for secured contents scattered 
across different facets. For edge case where the whole facet (results) is not 
accessible, the count still shows a number after the sampling percent is 
applied. Even if the number is small, user experience is misleading/inaccurate 
as nothing would return when the facet is clicked (applied as a query 
condition).

For example, a ACLs/CUGs guarded "private" folder, in which all the assets are 
tagged with the same facet value. Non authorized user may still see this facet 
with a count but gets nothing when clicking on the facet.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (OAK-7702) [Direct Binary Access] Add CDN support, use S3 Transfer Acceleration only for uploads

2019-03-25 Thread Matt Ryan (JIRA)


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

Matt Ryan reassigned OAK-7702:
--

Assignee: Matt Ryan

> [Direct Binary Access] Add CDN support, use S3 Transfer Acceleration only for 
> uploads
> -
>
> Key: OAK-7702
> URL: https://issues.apache.org/jira/browse/OAK-7702
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: blob-cloud, blob-cloud-azure
>Reporter: Alexander Klimetschek
>Assignee: Matt Ryan
>Priority: Major
>
> Azure Blob Store and S3 support CDNs in front of private containers/buckets, 
> which also work with presigned URLs ([S3 
> docs|https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-signed-urls.html],
>  [cloudfront presigning 
> java|https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/CFPrivateDistJavaDevelopment.html],
>  [Azure 
> docs|https://docs.microsoft.com/en-us/azure/cdn/cdn-sas-storage-support]). 
> The binary access feature should support these for download URLs via a 
> configuration on the DataStore.
> Currently, the S3 datastore has a config for [transfer 
> acceleration|https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html]
>  that if enabled, will make both upload & download URLs use the acceleration 
> option. However, this feature only makes sense for uploads, especially if CDN 
> is an option for downloads.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (OAK-8166) Index definition with orderable property definitions with and without functions breaks index

2019-03-25 Thread Tom Blackford (JIRA)
Tom Blackford created OAK-8166:
--

 Summary: Index definition with orderable property definitions with 
and without functions breaks index
 Key: OAK-8166
 URL: https://issues.apache.org/jira/browse/OAK-8166
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: indexing
Affects Versions: 1.8.12
Reporter: Tom Blackford


If an index definition contains the same orderable property with and without 
functions, it will fail to index any node which contains that property. The 
failure will be logged as [1].

Steps to reproduce:
* Configure index with the two property definitions shown at [2].
* Refresh the index definition
* Modify a node that falls under the definition - it will fail with the 
exception shown at [1]
* Modify the 'non-function' index definition to not be orderable 
(orderable=false)
* Refresh the index definition
* Modify the same node - note there is no exception.

Thanks to [~catholicon] for assistance identifying root cause.


[1]
{code}
25.03.2019 15:39:04.135 *WARN* [async-index-update-async] 
org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditor Failed to 
index the node [/content/dam/Unknown-2.png]
java.lang.IllegalArgumentException: DocValuesField 
":dvjcr:content/metadata/dc:title" appears more than once in this document 
(only one value is allowed per field)
at 
org.apache.lucene.index.SortedDocValuesWriter.addValue(SortedDocValuesWriter.java:62)
 [org.apache.jackrabbit.oak-lucene:1.8.9]
at 
org.apache.lucene.index.DocValuesProcessor.addSortedField(DocValuesProcessor.java:125)
 [org.apache.jackrabbit.oak-lucene:1.8.9]
at 
org.apache.lucene.index.DocValuesProcessor.addField(DocValuesProcessor.java:59) 
[org.apache.jackrabbit.oak-lucene:1.8.9]
at 
org.apache.lucene.index.TwoStoredFieldsConsumers.addField(TwoStoredFieldsConsumers.java:36)
 [org.apache.jackrabbit.oak-lucene:1.8.9]
at 
org.apache.lucene.index.DocFieldProcessor.processDocument(DocFieldProcessor.java:236)
 [org.apache.jackrabbit.oak-lucene:1.8.9]
at 
org.apache.lucene.index.DocumentsWriterPerThread.updateDocument(DocumentsWriterPerThread.java:253)
 [org.apache.jackrabbit.oak-lucene:1.8.9]
at 
org.apache.lucene.index.DocumentsWriter.updateDocument(DocumentsWriter.java:455)
 [org.apache.jackrabbit.oak-lucene:1.8.9]
at 
org.apache.lucene.index.IndexWriter.updateDocument(IndexWriter.java:1534) 
[org.apache.jackrabbit.oak-lucene:1.8.9]
at 
org.apache.lucene.index.IndexWriter.updateDocument(IndexWriter.java:1507) 
[org.apache.jackrabbit.oak-lucene:1.8.9]
at 
org.apache.jackrabbit.oak.plugins.index.lucene.writer.DefaultIndexWriter.updateDocument(DefaultIndexWriter.java:86)
 [org.apache.jackrabbit.oak-lucene:1.8.9]
at 
org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditor.addOrUpdate(LuceneIndexEditor.java:258)
 [org.apache.jackrabbit.oak-lucene:1.8.9]
at 
org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditor.leave(LuceneIndexEditor.java:140)
 [org.apache.jackrabbit.oak-lucene:1.8.9]
at 
org.apache.jackrabbit.oak.spi.commit.CompositeEditor.leave(CompositeEditor.java:74)
 [org.apache.jackrabbit.oak-store-spi:1.8.9]
{code}


[2] 
{code}
"dcTitle": {
"jcr:primaryType": "nt:unstructured",
"nodeScopeIndex": "true",
"useInSuggest": "true",
"ordered": "false",
"propertyIndex": "true",
"useInSpellcheck": "true",
"name": "jcr:content/metadata/dc:title",
"boost": "2.0"
},
  "dcTitleLowercase": {
"jcr:primaryType": "nt:unstructured",
"ordered": "true",
"propertyIndex": "true",
"function": "fn:lower-case(jcr:content/metadata/@dc:title)"
}
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (OAK-8053) Add intermediate report to ExternalLoginTest

2019-03-25 Thread Alex Deparvu (JIRA)


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

Alex Deparvu edited comment on OAK-8053 at 3/25/19 10:19 AM:
-

http://svn.apache.org/viewvc?rev=1854316=rev, 
http://svn.apache.org/viewvc?rev=1856176=rev


was (Author: alex.parvulescu):
http://svn.apache.org/viewvc?rev=1854316=rev

> Add intermediate report to ExternalLoginTest
> 
>
> Key: OAK-8053
> URL: https://issues.apache.org/jira/browse/OAK-8053
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: benchmarks
>Reporter: Alex Deparvu
>Assignee: Alex Deparvu
>Priority: Trivial
> Fix For: 1.12, 1.11.0
>
>
> Add support for a {{report}} flag that will output some intermediary stats 
> (like duration over the last 1k tests).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OAK-8155) CompositePermissionProvider: add possibility to abort evaluation

2019-03-25 Thread Alex Deparvu (JIRA)


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

Alex Deparvu commented on OAK-8155:
---

could you provide an example? I see some of the code already shortcuts if 
possible.

> CompositePermissionProvider: add possibility to abort evaluation
> 
>
> Key: OAK-8155
> URL: https://issues.apache.org/jira/browse/OAK-8155
> Project: Jackrabbit Oak
>  Issue Type: New Feature
>  Components: security, security-spi
>Reporter: angela
>Assignee: angela
>Priority: Major
> Fix For: 1.12
>
>
> when aggregating multiple authorization models we currently have the ability 
> to choose between CompositionType.AND and CompositionType.OR for the 
> evaluation of effective permissions. In other words as soon as more than 1 
> PermissionProvider is present for the evaluation the results of that 
> evaluation are either combined in an AND or OR fashion.
> however, we currently lack the ability to stop or abort the evaluation if a 
> given provider instance was 'sufficient' to determine if a given set of 
> permissions is granted or denied. 
> [~stillalex], let's discuss ideas and options on how we could achieve this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (OAK-8165) Build Jackrabbit Oak #2034 failed

2019-03-25 Thread Alex Deparvu (JIRA)


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

Alex Deparvu resolved OAK-8165.
---
Resolution: Duplicate

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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (OAK-8165) Build Jackrabbit Oak #2034 failed

2019-03-25 Thread Alex Deparvu (JIRA)


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

Alex Deparvu closed OAK-8165.
-

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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)