[
https://issues.apache.org/jira/browse/SLING-13061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18052184#comment-18052184
]
Konrad Windszus edited comment on SLING-13061 at 1/15/26 5:04 PM:
------------------------------------------------------------------
Unfortunately this requires knowing the {{jobTopic}} in advance. So one could
either come up with an overridden {{getJobById(String id, String topic)}} or
rely on traversal for the topic name. Also one would need to check the path for
both assigned and unassigned jobs, where assigned jobs use the Sling ID as
intermediate path...
was (Author: kwin):
Unfortunately this requires knowing the {{jobTopic}} in advance. So one could
either come up with an overridden {{getJobById(String id, String topic)}} or
rely on traversal for the topic name. Also one would need to check the path for
both assigned and unassigned jobs (but since this is only two it should be
fine).
> JobManagerImpl.getJobById() should get rid of query
> ---------------------------------------------------
>
> Key: SLING-13061
> URL: https://issues.apache.org/jira/browse/SLING-13061
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Event Impl 4.4.2
>
>
> As JobManagerImpl uses a structured way to store new jobs, its
> {{getJobById(String)}} should not need to rely on a query to find the job in
> the repo but use JobManagerConfiguration.getUniquePath(...) instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
