You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Borisov (Jira)" <ji...@apache.org> on 2019/08/29 06:22:00 UTC

[jira] [Assigned] (IGNITE-8096) Web console: add ability to clone cluster configuration entities

     [ https://issues.apache.org/jira/browse/IGNITE-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ilya Borisov reassigned IGNITE-8096:
------------------------------------

    Assignee:     (was: Ilya Borisov)

> Web console: add ability to clone cluster configuration entities
> ----------------------------------------------------------------
>
>                 Key: IGNITE-8096
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8096
>             Project: Ignite
>          Issue Type: New Feature
>          Components: wizards
>            Reporter: Ilya Borisov
>            Priority: Major
>
> New configuration introduced by IGNITE-5466 lacks a way to clone cluster configuration child entities (caches, igfss and domain models).
> *What to do:*
> Implement cluster config entity cloning mechanism. It might be a single (or multiple) items table context action, which creates new entities under the hood using a default unique name generator function, sends one or multiple requests to the backend and shows an error notification if something goes wrong.
> *Potential issues:*
> 1. Nested reference IDs and what to do with them.
> 2. If user decides to clone current edited item, can unsaved changes trigger any unwanted behavior?
> 3. One vs multiple items to clone at the same time.
> *Additional ideas:*
> 1. Clone the item specified amount of times. Useful when user needs 10 caches with similar configuration.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)