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

Internal RepositoryCache CreateNode events should include node type info for new node and parent

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Blocker
    • 4.0.0.Alpha1
    • 3.0.0.Alpha1
    • JCR

    Description

      It may be useful to include in the "create node" events (within the RepositoryCache) all of the node types (primary type and mixin types) of newly-created nodes as well as of their parent node. While this will increase the size of the event, it would save the ModeShape ObservationManager-related code from having to look up that node type information when determining whether the event should be forwarded to listeners registered with node type constraints.

      We may need to run some performance tests before going this route, measuring the performance improvement is indeed worth the increase in event size (which would affect the amount of information sent between processes in the cluster).

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users MODE-1683 Add event journal

          • 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

          Feature Request - Feature requests from customers and/or users MODE-2018 Query engine should work with no indexes and with defined indexes

          • 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

          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
          relates to

          Feature Request - Feature requests from customers and/or users MODE-2064 Support JSR-333 (aka, "JCR 2.1") API

          • 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.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: