[
https://issues.apache.org/jira/browse/IGNITE-12610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044473#comment-17044473
]
Artsiom Panko edited comment on IGNITE-12610 at 2/25/20 2:17 PM:
-----------------------------------------------------------------
[~Pavlukhin], I moved all H2 setting to one class and change the way of
starting Ignite.
By the way, some sys properties from static import are not used in
SysProperties.class and in Ignite at all
was (Author: artsiom_panko):
[~Pavlukhin], I moved all H2 setting to one class and change the way of
starting Ignite.
By the way, some sys properties from static import are not used in
SysProperties.class, so the only way of testing properties values ps testing
settings the value of properties
> 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
> Assignee: Artsiom Panko
> 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)
