[jira] [Updated] (FLINK-33266) Support plan cache for DQL in SQL Gateway
[ https://issues.apache.org/jira/browse/FLINK-33266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-33266: --- Labels: pull-request-available (was: ) > Support plan cache for DQL in SQL Gateway > - > > Key: FLINK-33266 > URL: https://issues.apache.org/jira/browse/FLINK-33266 > Project: Flink > Issue Type: Sub-task >Reporter: Dan Zou >Assignee: Dan Zou >Priority: Major > Labels: pull-request-available > > In OLAP scenarios, running a single query typically cost hundreds of > milliseconds or a few seconds, of which it takes about tens of milliseconds > to parse, validate, optimize, and translate it to Flink transformations. > Adding cache to cache the transformations corresponding to queries is > meaningful for scenarios where certain queries are often executed repeatedly. > We focus on submitting DQL through SQL gateway in this ticket. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-33266) Support plan cache for DQL in SQL Gateway
[ https://issues.apache.org/jira/browse/FLINK-33266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Zou updated FLINK-33266: Description: In OLAP scenarios, running a single query typically cost hundreds of milliseconds or a few seconds, of which it takes about tens of milliseconds to parse, validate, optimize, and translate it to Flink transformations. Adding cache to cache the transformations corresponding to queries is meaningful for scenarios where certain queries are often executed repeatedly. We focus on submitting DQL through SQL gateway in this ticket. was:In OLAP scenarios, running a single query typically cost hundreds of milliseconds or a few seconds, of which it takes about tens of milliseconds to parse, validate, optimize, and translate it to Flink transformations. Adding cache to cache the transformations corresponding to queries is meaningful for scenarios where certain queries are often executed repeatedly. > Support plan cache for DQL in SQL Gateway > - > > Key: FLINK-33266 > URL: https://issues.apache.org/jira/browse/FLINK-33266 > Project: Flink > Issue Type: Sub-task >Reporter: Dan Zou >Assignee: Dan Zou >Priority: Major > > In OLAP scenarios, running a single query typically cost hundreds of > milliseconds or a few seconds, of which it takes about tens of milliseconds > to parse, validate, optimize, and translate it to Flink transformations. > Adding cache to cache the transformations corresponding to queries is > meaningful for scenarios where certain queries are often executed repeatedly. > We focus on submitting DQL through SQL gateway in this ticket. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-33266) Support plan cache for DQL in SQL Gateway
[ https://issues.apache.org/jira/browse/FLINK-33266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Zou updated FLINK-33266: Summary: Support plan cache for DQL in SQL Gateway (was: Support plan cache for SQL jobs) > Support plan cache for DQL in SQL Gateway > - > > Key: FLINK-33266 > URL: https://issues.apache.org/jira/browse/FLINK-33266 > Project: Flink > Issue Type: Sub-task >Reporter: Dan Zou >Assignee: Dan Zou >Priority: Major > > In OLAP scenarios, running a single query typically cost hundreds of > milliseconds or a few seconds, of which it takes about tens of milliseconds > to parse, validate, optimize, and translate it to Flink transformations. > Adding cache to cache the transformations corresponding to queries is > meaningful for scenarios where certain queries are often executed repeatedly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
