For separate option, where would updated template be stored ? Cheers
On Jul 10, 2014, at 7:41 AM, Sumit Mohanty <[email protected]> wrote: > Separate option seems good. Should Slider block update if its a running > cluster? > > > On Thu, Jul 10, 2014 at 3:29 AM, Steve Loughran <[email protected]> > wrote: > >> I think it might be a separate option, the way flex is. >> >> something like >> >> slider update cluster --template {other args} >> >> This would make it easier to patch things. It'd have to warn on a patch of >> a running cluster "changes will not take effect", but otherwise just >> load/patch/save the config(s) >> >> >> >> >> On 10 July 2014 00:50, Ted Yu <[email protected]> wrote: >> >>> Hi, >>> I want to get your opinion on whether 'thaw' command should support the >>> specification of template, as in: >>> --template appConfig.json >>> >>> The use case would be: user changes some (hbase) config values and wants >>> the new values to take effect when the cluster is thaw'ed. >>> >>> Please comment. >> >> -- >> CONFIDENTIALITY NOTICE >> NOTICE: This message is intended for the use of the individual or entity to >> which it is addressed and may contain information that is confidential, >> privileged and exempt from disclosure under applicable law. If the reader >> of this message is not the intended recipient, you are hereby notified that >> any printing, copying, dissemination, distribution, disclosure or >> forwarding of this communication is strictly prohibited. If you have >> received this communication in error, please contact the sender immediately >> and delete it from your system. Thank You. >>
