[
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/sling-org-apache-sling-testing-clients/pull/10 and
realized [~volteanu]'s comment.
I can update the PR to have an explicit {{setLanes}} method - although, I think
that would likely require updating tests using a pattern like
{{client.adaptTo(IndexingClient.class).waitForAsyncIndexing}}. So, maybe it's
ok to simply have extra csv of lanes in sling config map itself?
> IndexingClient should have configurable lanes
> ---------------------------------------------
>
> Key: SLING-8710
> URL: https://issues.apache.org/jira/browse/SLING-8710
> Project: Sling
> Issue Type: Improvement
> Components: Launchpad
> Reporter: Vikas Saurabh
> Priority: Major
> Labels: sling-IT
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{IndexingClient}} currently relies on {{OsgiConsoleCient}} to peek into
> system's lane configuration. That, in turn, requires access to
> /system/console which might be blocked on the system which is being tested.
> As indexing lanes in a setup isn't a very dynamic property, a quick work
> around could be for {{IndexingClient}} to allow setting up "expected index
> lanes in target setup".
> This issue would be an improvement over what was implemented in SLING-7169.
> [~rombert] and [~volteanu], since most of the comments over there are from
> you guys, wdyt about this improvement?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
