[
https://issues.apache.org/jira/browse/PHOENIX-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-7520:
---------------------------------
Release Note:
The Phoenix startup scripts (sqlline.py, psql.py, performance.py) now try to
parse and apply environment variables set in hbase-env.sh / hbase-env.cmd.
Also, the contents of the HBASE_OPTS enviroment variable is now added to the
java command when starting the above scripts
This new behaviour can be disabled by setting the SKIP_HBASE_ENV environment
variable to any value.
was:
The Phoenix startup scripts now try to parse and apply environment variables
set in hbase-env.sh / hbase-env.cmd.
Also, the contents of the HBASE_OPTS enviroment variable is now added to the
java command in sqlline.py, psql.py and performance.py.
This new behaviour can be disabled by setting the SKIP_HBASE_ENV environment
variable to any value.
> Use HBASE_OPTS from hbase-env.sh in startup scripts
> ---------------------------------------------------
>
> Key: PHOENIX-7520
> URL: https://issues.apache.org/jira/browse/PHOENIX-7520
> Project: Phoenix
> Issue Type: Improvement
> Components: core, queryserver
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> The startup scripts already read JAVA_HOME from hbase-env.sh
> We should read and apply HBASE_OPTS in the startup scripts.
> This came up on a FIPS system where the security provider was defined in
> hbase-env.sh, but is useful for GC settings, etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
