[
https://issues.apache.org/jira/browse/IGNITE-9458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602396#comment-16602396
]
ASF GitHub Bot commented on IGNITE-9458:
----------------------------------------
GitHub user pavel-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/4675
IGNITE-9458: Changed behaviour of --mvcc flag in benchmark server.
Don't override ignite config's "mvccEnabled" property in benchmark server.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9458
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4675.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4675
----
commit 2c69fbe538f66497a5b6cc1a1ac8900bd7efb7ef
Author: Pavel Kuznetsov <palmihal@...>
Date: 2018-09-03T18:37:20Z
IGNITE-9458: Changed behaviour of --mvcc flag in benchmark server.
----
> SQL benchmarks: absence of "--mvcc" benchmark flag should not overwrite
> config values
> -------------------------------------------------------------------------------------
>
> Key: IGNITE-9458
> URL: https://issues.apache.org/jira/browse/IGNITE-9458
> Project: Ignite
> Issue Type: Bug
> Reporter: Pavel Kuznetsov
> Assignee: Pavel Kuznetsov
> Priority: Minor
>
> Currently, IgniteNode benchmark application ignores mvccEnable property of
> IgniteConfiguration.
> Absence of --mvcc flag is treateted as "turn mvcc off forcibly", existence as
> "turn mvcc on forcibly".
> We need to change sematics of absence of this flag as "Use value from config".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
