[
https://issues.apache.org/jira/browse/HBASE-10081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881263#comment-13881263
]
Jesse Yates commented on HBASE-10081:
-------------------------------------
It wouldn't erase it in the shell, I _think_, but rather just update it for the
the scripts and all child processes. So, the calling shell would still have the
variable you set.
As an example, say I have (checked locally on my Mac):
{code}
bash$ export HBASE_OPTS="-XX:+UseConcMarkSweepGC"
{code}
and in my hbase-env.sh have
{code}
HBASE_OPTS="$HBASE_OPTS -XX:CustomThingy"
{code}
then after running bin/start-hbase.sh, I would still just see
{code}
bash$ echo $HBASE_OPTS
-XX:+UseConcMarkSweepGC"
{code}
Should be fine, yes?
> 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)
