[
https://issues.apache.org/jira/browse/IGNITE-12610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031376#comment-17031376
]
Ivan Pavlukhin commented on IGNITE-12610:
-----------------------------------------
[~artsiom_panko], yes your understanding is right. In H2 {{SysProperties}}
there is a following code:
{code}
public static final boolean OBJECT_CACHE = Utils.getProperty("h2.objectCache",
true);
{code}
_true_ is a default value. But for Ignite SQL we would like to override this
property value to _false_. And it was done in the past but after some
refactoring we lost that overriding. One way to reach the desired effect is set
this property in {{IgniteH2Indexing}} static initializer. Perhaps there is a
better way. Also it would be good to create a unit test ensuring that H2 object
cache is disabled.
> Disable H2 object cache reliably
> --------------------------------
>
> Key: IGNITE-12610
> URL: https://issues.apache.org/jira/browse/IGNITE-12610
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.8
> Reporter: Ivan Pavlukhin
> Priority: Major
> Labels: newbie
> Fix For: 2.9
>
>
> Internally H2 maintains a cache of {{org.h2.value.Value}} objects. It can be
> disabled by using "h2.objectCache" system property. There is a clear intent
> to disable this cache because the system property is set to "false" in
> {{org.apache.ignite.internal.processors.query.h2.ConnectionManager}}. But
> apparently it is too late, because the property is read by H2 internals
> before it. Consequently the object cache is enabled by default.
> We need to set this property earlier.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
