You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2021/09/03 15:18:00 UTC

[jira] [Updated] (IGNITE-15445) Add cache drop (delete, destroy) command to control.sh script

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

Pavel Pereslegin updated IGNITE-15445:
--------------------------------------
    Description: 
Currently, there is no way to delete caches using the control.sh script.

This feature is available through JMX, REST, SQL (partially) and ignitevisor.sh.
However, ignitevisor.sh is not very convenient to use - it needs to start a separate daemon node.

We should add this feature to the control script.

  was:
Currently, there is no way to delete caches using the control.sh script.

This feature is available through via ignitevisor.sh, JMX, REST, and SQL (drop table).
However, ignitevisor.sh is not very convenient to use - it needs to start a separate daemon node.

We should add this feature to the control script.


> Add cache drop (delete, destroy) command to control.sh script
> -------------------------------------------------------------
>
>                 Key: IGNITE-15445
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15445
>             Project: Ignite
>          Issue Type: Improvement
>          Components: control.sh
>            Reporter: Pavel Pereslegin
>            Assignee: Pavel Pereslegin
>            Priority: Major
>
> Currently, there is no way to delete caches using the control.sh script.
> This feature is available through JMX, REST, SQL (partially) and ignitevisor.sh.
> However, ignitevisor.sh is not very convenient to use - it needs to start a separate daemon node.
> We should add this feature to the control script.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)