[
https://issues.apache.org/jira/browse/SOLR-14723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255182#comment-17255182
]
Tim Dillon commented on SOLR-14723:
-----------------------------------
{quote}we should remove the
{{org.apache.solr.core.SolrConfig.PluginOpts.REQUIRE_CLASS}} to the
{{SolrCache}} plugin
{quote}
Doing this seems to have resolved the error.
{quote}You mean the tests aren't deprecated? What's the error?
{quote}
The error was {{org.apache.solr.search.CaffeineCache cannot be cast to class
org.apache.solr.search.LFUCache}} which seems to be happening at
{{org.apache.solr.search.TestLFUCache.testTimeDecayParams(TestLFUCache.java:66)}}.
There was a very similar error in
{{org.apache.solr.search.json.TestJsonRequest}} that seemed to be fixed by
removing the cast to LFUCache. I have not tried to fix the one in
{{org.apache.solr.search.TestLFUCache}} as I wanted to see if these 3 cache
tests should be deprecated first. Maybe we can continue to explore this in the
PR. Thanks for your help!
> Rremove the class atribute for the caches in the _default/example configsets
> ----------------------------------------------------------------------------
>
> Key: SOLR-14723
> URL: https://issues.apache.org/jira/browse/SOLR-14723
> Project: Solr
> Issue Type: Improvement
> Reporter: Tomas Eduardo Fernandez Lobbe
> Priority: Trivial
> Labels: newdev
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In 8.x branch, the default and example configsets include LRUCache and
> FastLRUCache as the implementation for the various caches.
> {code:xml}
> <filterCache class="solr.FastLRUCache"
> size="512"
> initialSize="512"
> autowarmCount="0"/>
> {code}
> Those implementations are deprecated. We should remove the attribute
> completely and let the default take over (as it's in master), this should
> make upgrading configsets easier:
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
