ebean - Possible to change behavior of setUseQueryCache(true) from "MUST USE" to "USE IF POSSIBLE?"

Question

I am in the process of testing IGNITE for level 2 caching on my project. It has a lot of promise and I am excited to be using it.

One of the issues is that for development purposes, it's pretty heavy and since it starts up a full IGNITE node on dev workstations, is reduces engineers efficiency. This is because of the memory footprint and the fact that when source code is changed and class files are automatically reloaded, IGNITE is started again and again and complains mightily

This is a long-winded way to get to the point, which is that when I disable the l2Cache (ie, IGNITE) using the recommended approach:

ebean.disableL2Cache=true

I get a slew of runtime errors because we are using query caching extensively throughout the codebase. The error messages essentially state that .setUseQueryCache(true) cannot be run because there is no l2Cache enabled.

It seems like treating the semantics of .setUseQueryCache(true) from "you must use the query cache or fail noisily" to "use the query cache if possible" would be a minor change and would save [me, at least] a lot of grief.

question from:https://stackoverflow.com/questions/65557474/possible-to-change-behavior-of-setusequerycachetrue-from-must-use-to-use-if

Answer 1

Waitting for answers