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

Index is not properly updated when Location is deleted

    Details

      Description

      Deleting a location deletes a whole subtree. In Solr search engine we only update the deleted Location and it's Content, while the whole affected subtree should be properly updated.

        Activity

        Hide
        Rui Silva (Inactive) added a comment -

        Thanks for the info Petar Spanja. I'll have to verify that.
        That will definitely be helpful for other future issues.

        Show
        Rui Silva (Inactive) added a comment - Thanks for the info Petar Spanja . I'll have to verify that. That will definitely be helpful for other future issues.
        Hide
        Rui Silva (Inactive) added a comment -

        Tested and approved by QA for 5.4.
        Not approved (yet) for master though, but closing issue anyway, since known issue prevents correct testing of this on master, and a broader testing scope will cover this when EZP-24621 is fixed (See comments before for more info).

        Show
        Rui Silva (Inactive) added a comment - Tested and approved by QA for 5.4. Not approved (yet) for master though, but closing issue anyway, since known issue prevents correct testing of this on master, and a broader testing scope will cover this when EZP-24621 is fixed (See comments before for more info).
        Hide
        Petar Spanja (Inactive) added a comment -

        [~rui.silva@ez.no] Yes, that's the explanation, it happens because both use SignalSlot system.
        BTW you can increase command verbosity output level and you'll get stack trace.

        Show
        Petar Spanja (Inactive) added a comment - [~rui.silva@ez.no] Yes, that's the explanation, it happens because both use SignalSlot system. BTW you can increase command verbosity output level and you'll get stack trace.
        Hide
        Rui Silva (Inactive) added a comment -

        Petar Spanja, I wrapped it in try catch because for some reason unknown to us (we've dug around this for a while trying to figure it out) it was always throwing the NotFoundException and sometimes it deleted the object anyway, and sometimes it did not (checked though admin interface), and we did not figure out why.
        Thus, unbeknownst to us how this was or was not related to the issue itself, we decided to simply mute it in order to bypass something we could not wrap our heads around that resulted in varying outcomes.
        Where you say "The cause for stuff not being deleted from index is that cache purge fails with NotFoundException", is that the explanation then as to why the contents are not being removed? So this issue is known to only happen on a master? On a 5.4 it did not happen as QA tested it, neither (as far as I can remember) the NotFoundException.

        André Rømcke, I will QA this then for now, and then perhaps when EZP-24621 is fixed (which seems to cover a more broad scope) the testing procedure will cover this as well.

        Show
        Rui Silva (Inactive) added a comment - Petar Spanja , I wrapped it in try catch because for some reason unknown to us (we've dug around this for a while trying to figure it out) it was always throwing the NotFoundException and sometimes it deleted the object anyway, and sometimes it did not (checked though admin interface), and we did not figure out why. Thus, unbeknownst to us how this was or was not related to the issue itself, we decided to simply mute it in order to bypass something we could not wrap our heads around that resulted in varying outcomes. Where you say "The cause for stuff not being deleted from index is that cache purge fails with NotFoundException", is that the explanation then as to why the contents are not being removed? So this issue is known to only happen on a master? On a 5.4 it did not happen as QA tested it, neither (as far as I can remember) the NotFoundException. André Rømcke , I will QA this then for now, and then perhaps when EZP-24621 is fixed (which seems to cover a more broad scope) the testing procedure will cover this as well.
        Hide
        André Rømcke added a comment -

        Cache clearing issues is covered by EZP-24621 and it's related issues.

        QA: Please close this as we have test coverage for this specific case, and rather do the overall system testing when EZP-24621 and EZP-25003 is fixed.

        Show
        André Rømcke added a comment - Cache clearing issues is covered by EZP-24621 and it's related issues. QA: Please close this as we have test coverage for this specific case, and rather do the overall system testing when EZP-24621 and EZP-25003 is fixed.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: