You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by stanlyxiang <gi...@git.apache.org> on 2017/08/10 15:10:01 UTC

[GitHub] incubator-hawq issue #1277: add hawq start "userinput.ask_yesno"

Github user stanlyxiang commented on the issue:

    https://github.com/apache/incubator-hawq/pull/1277
  
    @wangbincmss  
    Since hawq opened source and use apache JIRA to tracker all the changes, so for every pull request please create a apache jira first for your pull request like other PRs. Use the jira to describe your problem and devs can discuss whether we should do the changes under the jira.
    
    For this pr, I don't think it's reasonable to add "userinput.ask_yesno" for "hawq start". IMO, "hawq init" or "hawq stop" will break the alive cluster if exists. "ask_yesno" will make users think twice for whether there is an alive cluster and whether to proceed. But there is no problem to proceed "hawq start" directly no matter how the cluster state is. "hawq start" will give corresponding hints for different errors.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---