Uploaded image for project: 'ModeShape'
  1. ModeShape
  2. MODE-1683

Add event journal

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Blocker
    • 4.0.0.Alpha1
    • 3.0.0.Final
    • Clustering, JCR, Query
    • None

    Description

      ModeShape should have a log/journal file that records all of the changes made to the system. The log should obviously be transactional and should work in both clustered and non-clustered configurations; in clustered deployments, the journal should contain local and remote events. It should be possible to use the log to implement delta backups, as well as the JCR journaled observation (MODE-2019).

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users MODE-2019 Support JCR event journal functionality

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) MODE-1903 Rebuild indexes from a point in time

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          is blocked by

          Task - Represents a small unit of work that is not end-user facing. MODE-1372 Internal RepositoryCache CreateNode events should include node type info for new node and parent

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. MODE-2135 Event journal should use MapDB's append-only file

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              hchiorean Horia Chiorean (Inactive)
              rhauch Randall Hauch (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: