[
https://issues.apache.org/jira/browse/DRILL-8504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870695#comment-17870695
]
ASF GitHub Bot commented on DRILL-8504:
---------------------------------------
jnturton commented on code in PR #2929:
URL: https://github.com/apache/drill/pull/2929#discussion_r1702679723
##########
contrib/storage-splunk/pom.xml:
##########
@@ -58,6 +58,12 @@
</exclusion>
</exclusions>
</dependency>
+ <dependency>
+ <groupId>com.github.ben-manes.caffeine</groupId>
+ <artifactId>caffeine</artifactId>
+ <version>2.9.3</version>
Review Comment:
Can we achieve the same thing using Guava's caching? The reason I ask is
that we already have this insanely big dependency tree and Guava is already in
it...
https://www.baeldung.com/guava-cache
> Add Schema Caching to Splunk Plugin
> -----------------------------------
>
> Key: DRILL-8504
> URL: https://issues.apache.org/jira/browse/DRILL-8504
> Project: Apache Drill
> Issue Type: Improvement
> Components: Storage - Splunk
> Affects Versions: 1.21.2
> Reporter: Charles Givre
> Assignee: Charles Givre
> Priority: Major
> Fix For: 1.22.0
>
>
> See PR
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
