[jira] [Commented] (SLING-8710) IndexingClient should have configurable lanes

[ https://issues.apache.org/jira/browse/SLING-8710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16930534#comment-16930534 ] Vikas Saurabh commented on SLING-8710: -- Just created a PR https://github.com/apache

[jira] [Commented] (SLING-8710) IndexingClient should have configurable lanes

[ https://issues.apache.org/jira/browse/SLING-8710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16930445#comment-16930445 ] Vikas Saurabh commented on SLING-8710: -- bq. repository directly using JCR Remoting,

[jira] [Commented] (SLING-8710) IndexingClient should have configurable lanes

[ https://issues.apache.org/jira/browse/SLING-8710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16930332#comment-16930332 ] Vikas Saurabh commented on SLING-8710: -- Ack. In that direction, I think allowing con

[jira] [Commented] (SLING-8710) IndexingClient should have configurable lanes

[ https://issues.apache.org/jira/browse/SLING-8710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16930307#comment-16930307 ] Vikas Saurabh commented on SLING-8710: -- [~volteanu], were you referring to adding co

[jira] [Commented] (SLING-8710) IndexingClient should have configurable lanes

[ https://issues.apache.org/jira/browse/SLING-8710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16930111#comment-16930111 ] Vikas Saurabh commented on SLING-8710: -- ... alternatively, an argument could be made

[jira] [Created] (SLING-8710) IndexingClient should have configurable lanes

Vikas Saurabh created SLING-8710: Summary: IndexingClient should have configurable lanes Key: SLING-8710 URL: https://issues.apache.org/jira/browse/SLING-8710 Project: Sling Issue Type: Impro

[jira] [Commented] (SLING-8407) JobManagerImpl.findJobs should prevent traversal

[ https://issues.apache.org/jira/browse/SLING-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837424#comment-16837424 ] Vikas Saurabh commented on SLING-8407: -- [~marett], option traversal fail is a loose

[jira] [Commented] (SLING-8407) JobManagerImpl.findJobs should prevent traversal

[ https://issues.apache.org/jira/browse/SLING-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837320#comment-16837320 ] Vikas Saurabh commented on SLING-8407: -- [~marett], bq. to wait on a specific m

[jira] [Commented] (SLING-8407) JobManagerImpl.findJobs should prevent traversal

[ https://issues.apache.org/jira/browse/SLING-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837309#comment-16837309 ] Vikas Saurabh commented on SLING-8407: -- bq. register a service implementing this API

[jira] [Commented] (SLING-4216) Limit the number of vanityPath MapEntry

[ https://issues.apache.org/jira/browse/SLING-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251612#comment-14251612 ] Vikas Saurabh commented on SLING-4216: -- bq. That is why the description of resource.

[jira] [Commented] (SLING-4216) Limit the number of vanityPath MapEntry

[ https://issues.apache.org/jira/browse/SLING-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248824#comment-14248824 ] Vikas Saurabh commented on SLING-4216: -- [~asanso], I tried reading through the patch

[jira] [Comment Edited] (SLING-4216) Limit the number of vanityPath MapEntry

[ https://issues.apache.org/jira/browse/SLING-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244094#comment-14244094 ] Vikas Saurabh edited comment on SLING-4216 at 12/12/14 1:11 PM:

[jira] [Commented] (SLING-4216) Limit the number of vanityPath MapEntry

[ https://issues.apache.org/jira/browse/SLING-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244094#comment-14244094 ] Vikas Saurabh commented on SLING-4216: -- bq. And I did actually did not change my mind

[jira] [Commented] (SLING-4216) Limit the number of vanityPath MapEntry

[ https://issues.apache.org/jira/browse/SLING-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244077#comment-14244077 ] Vikas Saurabh commented on SLING-4216: -- Sorry, I typed that in a hurry... I meant as

[jira] [Commented] (SLING-4216) Limit the number of vanityPath MapEntry

[ https://issues.apache.org/jira/browse/SLING-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244063#comment-14244063 ] Vikas Saurabh commented on SLING-4216: -- [~asanso], I just realized that serialization

[jira] [Updated] (SLING-3245) TenantAdapterFactory can return incorrect 'null' tenants depending on order of pathMatchers

[ https://issues.apache.org/jira/browse/SLING-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Saurabh updated SLING-3245: - Attachment: fix_early_tenantQuery_exit.patch patch for the fix of the issue > TenantAdapterFacto

[jira] [Created] (SLING-3245) TenantAdapterFactory can return incorrect 'null' tenants depending on order of pathMatchers

Vikas Saurabh created SLING-3245: Summary: TenantAdapterFactory can return incorrect 'null' tenants depending on order of pathMatchers Key: SLING-3245 URL: https://issues.apache.org/jira/browse/SLING-3245