jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Egli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3085) Add timestamp property to journal entries
Date Mon, 20 Jul 2015 09:30:04 GMT

    [ https://issues.apache.org/jira/browse/OAK-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633217#comment-14633217
] 

Stefan Egli commented on OAK-3085:
----------------------------------

[~reschke], I can only find setting {{_modified}} explicitly in {{NodeDocument.setModified}}
- ie it is only done for the {{nodes}} collection from a DocumentStore-independent point of
view. Are you saying the RDBDocumentStore is also setting {{_modified}} for all the other
collections? MongoDocumentStore doesn't do this afaics. So we'd have to add it eg to {{JournalEntry.asUpdateOp}}
- would that work for the RDB case?

> Add timestamp property to journal entries
> -----------------------------------------
>
>                 Key: OAK-3085
>                 URL: https://issues.apache.org/jira/browse/OAK-3085
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk
>    Affects Versions: 1.2.2, 1.3.2
>            Reporter: Stefan Egli
>             Fix For: 1.2.3, 1.3.3
>
>         Attachments: OAK-3085.patch, OAK-3085.v2.patch
>
>
> OAK-3001 is about improving the JournalGarbageCollector by querying on a separated-out
timestamp property (rather than the id that encapsulated the timestamp).
> In order to remove OAK-3001 as a blocker ticket from the 1.2.3 release, this ticket is
about adding a timestamp property to the journal entry but not making use of it yet. Later
on, when OAK-3001 is tackled, this timestamp property already exists and migration is not
an issue anymore (as 1.2.3 introduces the journal entry first time)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message