[jira] [Commented] (OAK-3825) Including Resource name to suggestions
[ https://issues.apache.org/jira/browse/OAK-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092224#comment-15092224 ] Amit Gupta commented on OAK-3825: - [~mmarth] you are right, it depends on the use case. In some use cases i.e. digital asset management, users are used to naming convention for asset (from file system days) and since they bring those same files to JCR. Asset name (node name) are some time meaningful and suggestion is desirable. As this would be based on index definition, I think that it would be configurable for system. > Including Resource name to suggestions > -- > > Key: OAK-3825 > URL: https://issues.apache.org/jira/browse/OAK-3825 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Reporter: Ankit Agarwal >Assignee: Vikas Saurabh > Fix For: 1.4 > > > Currently it is possible to include properties of a resource into > suggestions. > There should be a way so that its possible to include resource name itself > into suggestions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-2981) Access control logging
[
https://issues.apache.org/jira/browse/OAK-2981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589748#comment-14589748
]
Amit Gupta commented on OAK-2981:
-
>having a tool that logs all the paths that are accessed by the application,
>and shows the user and the permissions that are tested, helps >tremendously to
>cleanup and streamline a system. similar to a request or access log that helps
>understand the http traffic.
+1, looks useful
> Access control logging
> --
>
> Key: OAK-2981
> URL: https://issues.apache.org/jira/browse/OAK-2981
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core
>Reporter: Alexander Klimetschek
>Assignee: angela
>Priority: Minor
>
> For debugging application behavior and designing ACLs it is useful to have a
> logging of JCR operations and also see if access was granted or not.
> I hacked a quick solution that gives this result:
> {noformat}
> 10.06.2015 15:29:43.658 [admin] ALLOWED
> /jcr:system/rep:namespaces/rep:nsdata/http%3A%2F%2Fsling.apache.org%2Fjcr%2Fevent%2F1.0
> [read property]
> 10.06.2015 15:29:43.658 [admin] ALLOWED
> /var/eventing/jobs/assigned/862f413b-6f03-40a1-aa10-550af9970254 [read]
> 10.06.2015 15:29:43.658 [admin] ALLOWED
> /var/eventing/jobs/assigned/862f413b-6f03-40a1-aa10-550af9970254/jcr:primaryType
> [read property]
> 10.06.2015 15:30:10.484 [aklim...@adobe.com] DENIED
> /libs/wcm/core/content/contentfinder [read]
> 10.06.2015 15:25:12.421 [admin] ALLOWED
> /var/classes/862f413b-6f03-40a1-aa10-550af9970254/sightly/1.0.2/apps/ccebasic/ui/commons/breadcrumbs/SightlyJava_breadcrumbs.java/jcr:content/jcr:content
> [REMOVE_NODE,ADD_NODE]
> {noformat}
> See on my github fork:
> https://github.com/alexkli/jackrabbit-oak/commit/f4ecf7ca6b7d8c7e1d6967d409be4045a634efe2
> Change against the 1.2 branch. [As patch
> file|https://github.com/alexkli/jackrabbit-oak/commit/f4ecf7ca6b7d8c7e1d6967d409be4045a634efe2.patch].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-2594) Backport spellcheck support to 1.0
[ https://issues.apache.org/jira/browse/OAK-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587460#comment-14587460 ] Amit Gupta commented on OAK-2594: - [~teofili] is this part of 1.0.13 or 1.0.15 as mentioned on http://jackrabbit.apache.org/oak/docs/query/query.html > Backport spellcheck support to 1.0 > -- > > Key: OAK-2594 > URL: https://issues.apache.org/jira/browse/OAK-2594 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core, lucene, solr >Reporter: Tommaso Teofili >Assignee: Tommaso Teofili > Fix For: 1.0.13 > > > As spellcheck was available in JR2, 1.0 not having that support results in a > regression. > OAK-2175 should be backported to branch 1.0, that may imply backporting other > issues from trunk to branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-1530) TarMK thread logs warning
[
https://issues.apache.org/jira/browse/OAK-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13939379#comment-13939379
]
Amit Gupta commented on OAK-1530:
-
It is quite possible... since it was consistently reproducible today with
different fresh startups, I will try with virus scan disabled and update it
> TarMK thread logs warning
> -
>
> Key: OAK-1530
> URL: https://issues.apache.org/jira/browse/OAK-1530
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, segmentmk
>Affects Versions: 0.18
> Environment: Windows 7, JDK 1.7.0_51 64 Bit
>Reporter: Marcel Reutegger
>Priority: Minor
>
> From time to time I see warnings from the TarMK flush thread. I'm not sure if
> this is caused by my environment. In any case it would be good to at least
> know why it happens and then fix or document it.
> {noformat}
> 12.03.2014 10:54:45.752 *WARN* [TarMK flush thread: repository]
> org.apache.jackrabbit.oak.plugins.segment.file.FileStore
> Failed to flush the TarMK at repository
> java.io.IOException: The process cannot access the file because another
> process has locked a portion of the file
> at java.nio.MappedByteBuffer.force0(Native Method)
> at java.nio.MappedByteBuffer.force(MappedByteBuffer.java:203)
> at
> org.apache.jackrabbit.oak.plugins.segment.file.MappedAccess.flush(MappedAccess.java:73)
> at
> org.apache.jackrabbit.oak.plugins.segment.file.TarFile.flush(TarFile.java:181)
> at
> org.apache.jackrabbit.oak.plugins.segment.file.FileStore.flush(FileStore.java:225)
> at
> org.apache.jackrabbit.oak.plugins.segment.file.FileStore$1.run(FileStore.java:196)
> at java.lang.Thread.run(Thread.java:744)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (OAK-1530) TarMK thread logs warning
[
https://issues.apache.org/jira/browse/OAK-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938982#comment-13938982
]
Amit Gupta commented on OAK-1530:
-
I saw this with JDK 6 and windows 7 on my laptop as well
18.03.2014 14:28:50.670 *WARN* [TarMK flush thread:
C:\X\repository\segmentstore]
org.apache.jackrabbit.oak.plugins.segment.file.FileStore Failed to flush the
TarMK atC:\X\repository\segmentstore
java.io.IOException: null
at java.nio.MappedByteBuffer.force0(Native Method)
at java.nio.MappedByteBuffer.force(MappedByteBuffer.java:154)
at
org.apache.jackrabbit.oak.plugins.segment.file.MappedAccess.flush(MappedAccess.java:73)
at
org.apache.jackrabbit.oak.plugins.segment.file.TarFile.flush(TarFile.java:181)
at
org.apache.jackrabbit.oak.plugins.segment.file.FileStore.flush(FileStore.java:209)
at
org.apache.jackrabbit.oak.plugins.segment.file.FileStore$1.run(FileStore.java:180)
at java.lang.Thread.run(Thread.java:662)
> TarMK thread logs warning
> -
>
> Key: OAK-1530
> URL: https://issues.apache.org/jira/browse/OAK-1530
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, segmentmk
>Affects Versions: 0.18
> Environment: Windows 7, JDK 1.7.0_51 64 Bit
>Reporter: Marcel Reutegger
>Priority: Minor
>
> From time to time I see warnings from the TarMK flush thread. I'm not sure if
> this is caused by my environment. In any case it would be good to at least
> know why it happens and then fix or document it.
> {noformat}
> 12.03.2014 10:54:45.752 *WARN* [TarMK flush thread: repository]
> org.apache.jackrabbit.oak.plugins.segment.file.FileStore
> Failed to flush the TarMK at repository
> java.io.IOException: The process cannot access the file because another
> process has locked a portion of the file
> at java.nio.MappedByteBuffer.force0(Native Method)
> at java.nio.MappedByteBuffer.force(MappedByteBuffer.java:203)
> at
> org.apache.jackrabbit.oak.plugins.segment.file.MappedAccess.flush(MappedAccess.java:73)
> at
> org.apache.jackrabbit.oak.plugins.segment.file.TarFile.flush(TarFile.java:181)
> at
> org.apache.jackrabbit.oak.plugins.segment.file.FileStore.flush(FileStore.java:225)
> at
> org.apache.jackrabbit.oak.plugins.segment.file.FileStore$1.run(FileStore.java:196)
> at java.lang.Thread.run(Thread.java:744)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
