You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2015/02/24 03:45:12 UTC

[jira] [Updated] (IGNITE-186) Access to IgniteFS via Visorcmd

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

Alexey Kuznetsov updated IGNITE-186:
------------------------------------
    Fix Version/s:     (was: sprint-2)
                   sprint-3

> Access to IgniteFS via Visorcmd
> -------------------------------
>
>                 Key: IGNITE-186
>                 URL: https://issues.apache.org/jira/browse/IGNITE-186
>             Project: Ignite
>          Issue Type: Task
>          Components: UI
>    Affects Versions: sprint-1
>            Reporter: Alexey Kuznetsov
>            Assignee: Alexey Kuznetsov
>             Fix For: sprint-3
>
>
> Now IgniteFS is part of Ignite-fabric and doesn't need hadoop libs anymore.
> But hadoop provided access to IgniteFS via hadoop fs. 
> I suggest to introduce following:
> 1. Add support filesystem commands by visorcmd similar hadoop fs
> 2. Add command-line option to visorcmd to execute an one command and exit, for instance:
> bin/visorcmd.sh -e mkdir /123



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)