[
https://issues.apache.org/jira/browse/SLING-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990468#comment-14990468
]
Stefan Seifert commented on SLING-5259:
---------------------------------------
i did not think much on that, i just looked what property type for
slingevent:eventId was defined in a well-known commercial CMS using sling and
jobs, and there it was the same.
after thinking about it i assume a synchronous index makes really sense here
for how the job API is built. although executing job is asynchronous, the job
API manages queues to where the job is put immediately and synchronously. and
the API provides a "getJobById" method which takes jobs in this queues into
account as well.
but you're right - one should always think about this before defining another
synchronous index.
> Oak Server: Add property index for slingevent:eventId
> -----------------------------------------------------
>
> Key: SLING-5259
> URL: https://issues.apache.org/jira/browse/SLING-5259
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Minor
> Fix For: JCR Oak Server 1.0.2
>
>
> for better supporting fetching jobs by id a property index for
> {{slingevent:eventId}} should be defined.
> currently only a property index for {{event.job.topic}} exists.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
