Directory ApacheDS
  1. Directory ApacheDS
  2. DIRSERVER-1648

Disabling a schema should throw an error when there are still entries depending on that schema in the DIT

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Blocker Blocker
    • Resolution: Unresolved
    • Affects Version/s: 2.0.0-M2
    • Fix Version/s: 2.1.0
    • Component/s: None
    • Labels:
      None

      Description

      Following DIRSERVER-1647 (Unable to enable/modify/delete schema), I think there's a big issue in the case where we're disabling a schema.
      We should throw an error when there are still entries depending on that schema in the DIT.
      Currently it ends successfully, leaving the database in a not coherent state.
      Any restart of the server will fail after this.

        Activity

        Hide
        Pierre-Arnaud Marcelot added a comment -

        Version 2.0.0-M3 has been released a couple months ago.

        Assigned the remaining opened JIRA to the next iteration (2.0.0-M4).

        Show
        Pierre-Arnaud Marcelot added a comment - Version 2.0.0-M3 has been released a couple months ago. Assigned the remaining opened JIRA to the next iteration (2.0.0-M4).
        Hide
        Emmanuel Lecharny added a comment -

        This is extremely problematic. The only simple way to get this fixed would be to check all the entries to see if they are using the disabled schema, and it would take a very long time....

        Show
        Emmanuel Lecharny added a comment - This is extremely problematic. The only simple way to get this fixed would be to check all the entries to see if they are using the disabled schema, and it would take a very long time....
        Hide
        Emmanuel Lecharny added a comment -

        We can fix that the same way we did for the index creation when the index is created after some data has been injected :
        we check all the entries, and if we find one with the deleted element, we can either remove the entry, or inform the user that the element is in use.

        However, it's a huge modification. I suggest we postpone it to a later version

        Show
        Emmanuel Lecharny added a comment - We can fix that the same way we did for the index creation when the index is created after some data has been injected : we check all the entries, and if we find one with the deleted element, we can either remove the entry, or inform the user that the element is in use. However, it's a huge modification. I suggest we postpone it to a later version

          People

          • Assignee:
            Unassigned
            Reporter:
            Pierre-Arnaud Marcelot
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development