Thanks Dmitro! >From what you explained, the "key" names list are programmatically generated. >If that's the case, do we still have to update this role_command_order.json >file?
From: Dmitro Lysnichenko [mailto:[email protected]] Sent: Wednesday, February 11, 2015 3:45 PM To: [email protected] Subject: Re: role_command_order.json specification Names are programmatically generated. Like start/stop/install. Not sure about restart, decommission and others since they are "custom commands" (in terms of advanced, non-standard) On 11/02/2015 10:34 PM, Yu, Tao wrote: Hi Dmitro, Is there a list of the "key" and "value" so user can look up? how are they defined? Thanks, -Tao From: Dmitro Lysnichenko [mailto:[email protected]] Sent: Wednesday, February 11, 2015 3:00 PM To: [email protected]<mailto:[email protected]> Subject: Re: role_command_order.json specification Hi As I remember, key is just an action (e.g. start component HIVE_SERVER), and value is just a list "what should be executed before". role_command_order.json complements dependencies inherited from parent stack, if any. Hope this helps On 11/02/2015 09:52 PM, Yu, Tao wrote: Hi, I am new to Ambari and trying to create my own non-HDP stack. Could anyone please tell me any detailed specification info about the file role_command_order.json, like how to define the key-value pair in this file? Thanks, -Tao
