[
https://issues.apache.org/jira/browse/HBASE-10081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889662#comment-13889662
]
Nicolas Liochon commented on HBASE-10081:
-----------------------------------------
I didn't see the new messages - sorry about this.
bq. When did it become ok picking up config from environment?
It's something I typically do on my dev environment.
But I've seen it as well as a way to be sure that nothing is defined in the
product itself, to be sure that we don't modify anything that is a part of the
product (and hence modified when you upgrade).
bq. Should be fine, yes?
I'm not sure :-). [~liushaohui], what do you think?
> Since HBASE-7091, HBASE_OPTS cannot be set on the command line
> --------------------------------------------------------------
>
> Key: HBASE-10081
> URL: https://issues.apache.org/jira/browse/HBASE-10081
> Project: HBase
> Issue Type: Bug
> Components: scripts
> Affects Versions: 0.98.0, 0.96.0
> Reporter: Nicolas Liochon
> Assignee: Liu Shaohui
> Priority: Minor
> Attachments: HBASE-10081-v1.diff
>
>
> Discussed in HBASE-7091.
> It's not critical, but a little bit surprising, as the comments in bin/hbase
> doesn't say anything about this. If you create your own hbase-env then it's
> not an issue...
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
