[
https://issues.apache.org/jira/browse/DRILL-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18061106#comment-18061106
]
ASF GitHub Bot commented on DRILL-8529:
---------------------------------------
cgivre commented on code in PR #3023:
URL: https://github.com/apache/drill/pull/3023#discussion_r2854008575
##########
exec/java-exec/src/main/java/org/apache/drill/exec/server/options/SystemOptionManager.java:
##########
@@ -82,6 +82,10 @@ public static CaseInsensitiveMap<OptionDefinition>
createDefaultOptionDefinition
// here.
@SuppressWarnings("deprecation")
final OptionDefinition[] definitions = new OptionDefinition[]{
+ new OptionDefinition(PlannerSettings.PLAN_CACHE),
+ // new OptionDefinition(PlannerSettings.PLAN_CACHE_TTL),
Review Comment:
@vdegans @TomIsFrank, please remove above commented out lines and then we
can merge this.
Thanks!
> Caching QueryPlan Results
> -------------------------
>
> Key: DRILL-8529
> URL: https://issues.apache.org/jira/browse/DRILL-8529
> Project: Apache Drill
> Issue Type: Improvement
> Components: Query Planning & Optimization
> Reporter: Vincent de Gans
> Priority: Minor
> Fix For: Future
>
>
> I propose introducing a caching mechanism for the output of `getQueryPlan()`
> in cases where:
> - The input SQL query is the same as a previously seen one
> - The schema or relevant metadata used for planning has not changed
> - The cached result has not expired, based on a configurable time-to-live
> (TTL)
> Proposed Caching Features
> - Toggle to enable or disable query plan caching
> - Configurable TTL-based invalidation
> - Optional schema metadata verification to detect changes in underlying data
> sources
> Motivation
> - Reduce planner overhead for repeated queries
> - Improve response times in environments where query plans are reused
> - Provide an optional optimization that can be enabled when beneficial
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
