[
https://issues.apache.org/jira/browse/IGNITE-12610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037802#comment-17037802
]
Ivan Pavlukhin commented on IGNITE-12610:
-----------------------------------------
[~artsiom_panko], here are my comments:
# It is not good to call same code twice, please check
{{org.apache.ignite.internal.processors.query.h2.ConnectionManager}} static
initializer. It worth checking that other properties should be set in
{{IgniteH2Indexing}} as well.
# I think it is better to start an Ignite instance in test to check expected
property initialization in a wider context.
> 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)
