You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/04/16 09:42:00 UTC
[jira] [Commented] (PHOENIX-7523) Parse hbase-env.sh in PQS scripts, and and fall back to HBASE_OPTS in queryserver.py
[ https://issues.apache.org/jira/browse/PHOENIX-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17945017#comment-17945017 ]
ASF GitHub Bot commented on PHOENIX-7523:
-----------------------------------------
stoty merged PR #176:
URL: https://github.com/apache/phoenix-queryserver/pull/176
> Parse hbase-env.sh in PQS scripts, and and fall back to HBASE_OPTS in queryserver.py
> ------------------------------------------------------------------------------------
>
> Key: PHOENIX-7523
> URL: https://issues.apache.org/jira/browse/PHOENIX-7523
> Project: Phoenix
> Issue Type: Improvement
> Components: queryserver
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> We can tune the thick client JVM settings via PHOENIX_OPTS, and with the changes in PHOENIX-7520 HBASE_OPTS is also applied.
> However, there is no similar mechanism for PQS.
> The plan:
> - Parse and apply hbase-env.*, just like Phoenix does
> - Fall back to $HBASE_OPTS if PHOENIX_QUERYSERVER_OPTS is not set starting PQS
--
This message was sent by Atlassian Jira
(v8.20.10#820010)