[
https://issues.apache.org/jira/browse/OAK-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14496000#comment-14496000
]
Michael Dürig commented on OAK-2772:
------------------------------------
Commits are merge when the observation commit queue becomes full as means of
graceful degradation. If increasing the queue is not an option we need to
investigate in how to apply back pressure to the system. Some initial support
is already there. See {{CommitRateLimiter}}.
OTOH, the userId - which pertains to the commit boundary - is never available
for cluster external changes. For such changes we cannot retain the commit
boundary without changing Oak's underlying consistency model. Oak is
sequentially consistent, which is slightly weaker then linearisable and which
allows us to achieve horizontal scalability.
> Make Event Subjects Available in All Cases
> ------------------------------------------
>
> Key: OAK-2772
> URL: https://issues.apache.org/jira/browse/OAK-2772
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.2
> Reporter: Dominique Jäggi
>
> as per SLING-4624 subject support is needed for repository events in order to
> overcome the use of loginAdministrative calls which is a major security
> concern.
> currently oak cannot guarantee availability of subject (userid) for
> propagated events as commits may be merged under certain conditions and the
> information is thus lost.
> we should explore whether and how this issue can be resolved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
