Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • Docs Required, Release Notes Required

    Description

      Ignite provides metastore for internal components or plugins to store some information.
      There is some scenario when by-hand removal from metastore required.

      1. Blocker bug - we delete some class that was written to metastore from the new version.
      2. Migration between custom Ignite distributions where one of them has a custom class and the other doesn’t.

      We should provide to the cluster administrator the ability to remove any key from the metastore.
      JMX beans to remove metastore key should be introduced:

      In the scope of IEP-35 System view API introduced.
      A new API should use the same identifier that is used in the corresponding System View(metastore, distributed_metastore).

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              nizhikov Nikolay Izhikov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: