[
https://issues.apache.org/jira/browse/SLING-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990460#comment-14990460
]
Jörg Hoh commented on SLING-5259:
---------------------------------
Is a synchronous property index really the best approach here?
Async lucene indexes offer some nice capabilities like limiting them to a
certain path (thus reducing the time to create the index) and the reduced
probability of merge conflicts during save operations, which in my experience
can be quite a problem under load. And sling eventing is asynchronous by
default and I am not aware of any hard requirement, that the index should be
maintained synchronously (which means, that right after a session.save() you
can get the saved items via a query).
> 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)
