[
https://issues.apache.org/jira/browse/OAK-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819906#comment-13819906
]
Michael Dürig commented on OAK-1145:
------------------------------------
While the journal might seem convenient here, I don't think such a solution
would scale well. For example skipping to a time stamp will force the
repository to go through *all* commits rather through just the data related to
the feed. Furthermore time stamps are only available for cluster local commits.
In a clustered environment you thus won't be able to reliably skip to feed
entries contributed on a different cluster node.
As an alternative solution you could use a query (and a custom index) to get
new feed entries. Such a query could either run periodically or be triggered by
an observation listener, which listens on a specific property indicating the
time of the latest feed entry.
> [Observation] Support for EventJournal in Oak
> ---------------------------------------------
>
> Key: OAK-1145
> URL: https://issues.apache.org/jira/browse/OAK-1145
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: jcr
> Affects Versions: 0.10
> Reporter: Daniel Platon
> Labels: features
> Fix For: 0.14
>
>
> Please add support for EventJournal in Oak, as it was present in Jackrabbit 2.
> Thank you.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
