[jira] [Updated] (FLINK-33203) FLIP-374: Adding a separate configuration for specifying Java Options of the SQL Gateway
[
https://issues.apache.org/jira/browse/FLINK-33203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-33203:
---
Labels: pull-request-available (was: )
> FLIP-374: Adding a separate configuration for specifying Java Options of the
> SQL Gateway
>
>
> Key: FLINK-33203
> URL: https://issues.apache.org/jira/browse/FLINK-33203
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Gateway
>Reporter: Yangze Guo
>Assignee: Yangze Guo
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.19.0
>
>
> {color:#00}The SQL Gateway is an essential component of Flink in OLAP
> scenarios, and its performance and stability determine the SLA of Flink as an
> OLAP service. Just like other components in Flink, we propose adding a
> separate configuration option to specify the Java options for the SQL
> Gateway. This would allow users to fine-tune the memory settings, garbage
> collection behavior, and other relevant Java parameters specific to the SQL
> Gateway, ensuring optimal performance and stability in production
> environments.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33203) FLIP-374: Adding a separate configuration for specifying Java Options of the SQL Gateway
[
https://issues.apache.org/jira/browse/FLINK-33203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yangze Guo updated FLINK-33203:
---
Parent: FLINK-32898
Issue Type: Sub-task (was: Improvement)
> FLIP-374: Adding a separate configuration for specifying Java Options of the
> SQL Gateway
>
>
> Key: FLINK-33203
> URL: https://issues.apache.org/jira/browse/FLINK-33203
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Gateway
>Reporter: Yangze Guo
>Assignee: Yangze Guo
>Priority: Major
> Fix For: 1.19.0
>
>
> {color:#00}The SQL Gateway is an essential component of Flink in OLAP
> scenarios, and its performance and stability determine the SLA of Flink as an
> OLAP service. Just like other components in Flink, we propose adding a
> separate configuration option to specify the Java options for the SQL
> Gateway. This would allow users to fine-tune the memory settings, garbage
> collection behavior, and other relevant Java parameters specific to the SQL
> Gateway, ensuring optimal performance and stability in production
> environments.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
