You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2014/10/30 23:20:37 UTC

[jira] [Updated] (SLIDER-590) Need some convenient debugability of command script during/post development time

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

Ted Yu updated SLIDER-590:
--------------------------
    Summary: Need some convenient debugability of command script during/post development time  (was: Need some convinient debug ability of command script  during/post development time)

> Need some convenient debugability of command script during/post development time
> --------------------------------------------------------------------------------
>
>                 Key: SLIDER-590
>                 URL: https://issues.apache.org/jira/browse/SLIDER-590
>             Project: Slider
>          Issue Type: Bug
>            Reporter: Siyuan Hua
>            Assignee: Sumit Mohanty
>             Fix For: Slider 2.0.0
>
>
> Nowadays, whatever errors I made in command script to launch the component, I have to modify the python code repackage and redeployed to hdfs and relaunch the application. It's quite inconvenient. I hope there is a way to run, test and debug the command script right after they are installed on target machine. 



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