Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-23519

Implement indexing slots for Content ownership changes

    Details

      Description

      With PR https://github.com/ezsystems/ezpublish-kernel/pull/1045 ancestor UserGroups ids for the Content owner are indexed and criterion visitor for GROUP target is implemented.

      With this we will need to reindex owner user Content when:

      • Additional Location for owner user is added
      • User Location (or subtree) is moved
      • Parent user Location is swapped
      • possibly more...

      We also lack SPI to do implement some of those properly. UserService handles this problem by relying on search, but search should not be used in indexing slots as indexing is asynchronous.

        Issue Links

          Activity

          Petar Spanja (Inactive) created issue -
          Petar Spanja (Inactive) made changes -
          Field Original Value New Value
          Link This issue relates to EZP-23329 [ EZP-23329 ]
          Petar Spanja (Inactive) made changes -
          Link This issue discovered while testing EZP-23400 [ EZP-23400 ]
          Hide
          André Rømcke added a comment -

          Changes to owner on content is the easy part, the more tricky part is changes to groups of owner. Basically on any location changes on owner, any of it's parents, direct and inherited, causing all content of a owner to be reindexed.

          So we really should try to look harder at finding better way to model this, maybe custom user objects indexed separately, then at least we won't have to reindex all content belonging to a user on group changes.

          Show
          André Rømcke added a comment - Changes to owner on content is the easy part, the more tricky part is changes to groups of owner. Basically on any location changes on owner, any of it's parents, direct and inherited, causing all content of a owner to be reindexed. So we really should try to look harder at finding better way to model this, maybe custom user objects indexed separately, then at least we won't have to reindex all content belonging to a user on group changes.
          Hide
          Petar Spanja (Inactive) added a comment -

          @André Rømcke

          Should be possible to index that data separately and then use parent-child (not nested) join.

          Show
          Petar Spanja (Inactive) added a comment - @ André Rømcke Should be possible to index that data separately and then use parent-child (not nested) join.
          André Rømcke made changes -
          Status Open [ 1 ] Confirmed [ 10037 ]
          André Rømcke made changes -
          Status Confirmed [ 10037 ] Backlog [ 10000 ]
          André Rømcke made changes -
          Epic Link EZP-24178 [ 44321 ]
          André Rømcke made changes -
          Workflow eZ Engineering Scrumban Workflow [ 64944 ] EZ* Development Workflow [ 69725 ]
          Alex Schuster made changes -
          Workflow EZ* Development Workflow [ 69725 ] EZEE Development Workflow [ 108000 ]
          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Confirmed Confirmed
          148d 19h 25m 1 André Rømcke 24/Mar/15 2:50 PM
          Confirmed Confirmed Backlog Backlog
          2s 1 André Rømcke 24/Mar/15 2:50 PM

            People

            • Assignee:
              Unassigned
              Reporter:
              Petar Spanja (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: