[jira] [Assigned] (HBASE-20304) Flip default "return-values" in shell from false to true

2018-04-02 Thread Appy (JIRA)

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

Appy reassigned HBASE-20304:


Assignee: (was: Josh Elser)

> Flip default "return-values" in shell from false to true
> 
>
> Key: HBASE-20304
> URL: https://issues.apache.org/jira/browse/HBASE-20304
> Project: HBase
>  Issue Type: Bug
>  Components: shell
>Reporter: Josh Elser
>Priority: Blocker
> Attachments: HBASE-20304.001.branch-2.0.patch
>
>
> HBASE-15965 Was trying to be helpful in reducing spam in console output 
> printed back to the user.
> However, [~psomogyi] and [~balazs.meszaros] made a good find that some shell 
> commands (e.g. {{get_table}}) just don't work at all when the default 
> {{return-values=false}}. This would be quite obtuse to try to explain.
> [~appy] and I had mulled over whether we should flip the default from false 
> to true. The above example makes me sure that we should for 2.0.0.
> fyi [~stack]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (HBASE-20304) Flip default "return-values" in shell from false to true

2018-04-02 Thread Appy (JIRA)

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

Appy reassigned HBASE-20304:


Assignee: Josh Elser

> Flip default "return-values" in shell from false to true
> 
>
> Key: HBASE-20304
> URL: https://issues.apache.org/jira/browse/HBASE-20304
> Project: HBase
>  Issue Type: Bug
>  Components: shell
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Blocker
> Attachments: HBASE-20304.001.branch-2.0.patch
>
>
> HBASE-15965 Was trying to be helpful in reducing spam in console output 
> printed back to the user.
> However, [~psomogyi] and [~balazs.meszaros] made a good find that some shell 
> commands (e.g. {{get_table}}) just don't work at all when the default 
> {{return-values=false}}. This would be quite obtuse to try to explain.
> [~appy] and I had mulled over whether we should flip the default from false 
> to true. The above example makes me sure that we should for 2.0.0.
> fyi [~stack]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (HBASE-20304) Flip default "return-values" in shell from false to true

2018-03-28 Thread Sean Busbey (JIRA)

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

Sean Busbey reassigned HBASE-20304:
---

 Assignee: (was: Josh Elser)
Fix Version/s: (was: 2.0.0)

> Flip default "return-values" in shell from false to true
> 
>
> Key: HBASE-20304
> URL: https://issues.apache.org/jira/browse/HBASE-20304
> Project: HBase
>  Issue Type: Bug
>  Components: shell
>Reporter: Josh Elser
>Priority: Blocker
> Attachments: HBASE-20304.001.branch-2.0.patch
>
>
> HBASE-15965 Was trying to be helpful in reducing spam in console output 
> printed back to the user.
> However, [~psomogyi] and [~balazs.meszaros] made a good find that some shell 
> commands (e.g. {{get_table}}) just don't work at all when the default 
> {{return-values=false}}. This would be quite obtuse to try to explain.
> [~appy] and I had mulled over whether we should flip the default from false 
> to true. The above example makes me sure that we should for 2.0.0.
> fyi [~stack]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)