ignite-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From agoncha...@apache.org
Subject [10/50] [abbrv] ignite git commit: IGNITE-6431 Web console: Fixed duplicate "Partition loss policy" field. (cherry picked from commit 2299589)
Date Tue, 26 Sep 2017 10:48:23 GMT
IGNITE-6431 Web console: Fixed duplicate "Partition loss policy" field.
(cherry picked from commit 2299589)


Project: http://git-wip-us.apache.org/repos/asf/ignite/repo
Commit: http://git-wip-us.apache.org/repos/asf/ignite/commit/43387996
Tree: http://git-wip-us.apache.org/repos/asf/ignite/tree/43387996
Diff: http://git-wip-us.apache.org/repos/asf/ignite/diff/43387996

Branch: refs/heads/ignite-gg-12822
Commit: 433879963db63103ba597e67e703f6ab7d3c64e1
Parents: 915682b
Author: vsisko <vsisko@gridgain.com>
Authored: Wed Sep 20 00:10:46 2017 +0700
Committer: Alexey Kuznetsov <akuznetsov@apache.org>
Committed: Wed Sep 20 00:12:21 2017 +0700

----------------------------------------------------------------------
 .../states/configuration/caches/general.pug     | 23 ++------------------
 1 file changed, 2 insertions(+), 21 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/ignite/blob/43387996/modules/web-console/frontend/app/modules/states/configuration/caches/general.pug
----------------------------------------------------------------------
diff --git a/modules/web-console/frontend/app/modules/states/configuration/caches/general.pug
b/modules/web-console/frontend/app/modules/states/configuration/caches/general.pug
index 87c67f5..50f39e6 100644
--- a/modules/web-console/frontend/app/modules/states/configuration/caches/general.pug
+++ b/modules/web-console/frontend/app/modules/states/configuration/caches/general.pug
@@ -45,25 +45,6 @@ include /app/helpers/jade/mixins
                 .settings-row
                     +cacheMode('Mode:', `${model}.cacheMode`, '"cacheMode"', 'PARTITIONED')
 
-                //- Since ignite 2.0
-                .settings-row(ng-if='$ctrl.available("2.0.0")')
-                    +dropdown('Partition loss policy:', model + '.partitionLossPolicy', '"partitionLossPolicy"',
'true', 'IGNORE',
-                        '[\
-                            {value: "READ_ONLY_SAFE", label: "READ_ONLY_SAFE"},\
-                            {value: "READ_ONLY_ALL", label: "READ_ONLY_ALL"},\
-                            {value: "READ_WRITE_SAFE", label: "READ_WRITE_SAFE"},\
-                            {value: "READ_WRITE_ALL", label: "READ_WRITE_ALL"},\
-                            {value: "IGNORE", label: "IGNORE"}\
-                        ]',
-                        'Defines how cache will behave in a case when one or more partitions
are lost:\
-                        <ul>\
-                            <li>READ_ONLY_SAFE - all writes to the cache will be failed
with an exception, reads will only be allowed for keys in non-lost partitions</li>\
-                            <li>READ_ONLY_ALL - all writes to the cache will be failed
with an exception, all reads will proceed as if all partitions were in a consistent state</li>\
-                            <li>READ_WRITE_SAFE - all reads and writes will be allowed
for keys in valid partitions</li>\
-                            <li>READ_WRITE_ALL - all reads and writes will proceed
as if all partitions were in a consistent state</li>\
-                            <li>IGNORE - if partition is lost, reset its state and
do not clear intermediate data</li>\
-                        </ul>')
-
                 .settings-row
                     +dropdown('Atomicity:', `${model}.atomicityMode`, '"atomicityMode"',
'true', 'ATOMIC',
                         '[\
@@ -96,10 +77,10 @@ include /app/helpers/jade/mixins
                         <li>READ_ONLY_SAFE - in this mode all writes to the cache will
be failed with an exception,\
                             reads will only be allowed for keys in  non-lost partitions.\
                             Reads from lost partitions will be failed with an exception.</li>\
-                        <li>READ_ONLY_ALL - in this mode фll writes to the cache will
be failed with an exception.\
+                        <li>READ_ONLY_ALL - in this mode all writes to the cache will
be failed with an exception.\
                             All reads will proceed as if all partitions were in a consistent
state.\
                             The result of reading from a lost partition is undefined and
may be different on different nodes in the cluster.</li>\
-                        <li>READ_WRITE_SAFE - in this mode Aall reads and writes will
be allowed for keys in valid partitions.\
+                        <li>READ_WRITE_SAFE - in this mode all reads and writes will
be allowed for keys in valid partitions.\
                             All reads and writes for keys in lost partitions will be failed
with an exception.</li>\
                         <li>READ_WRITE_ALL - in this mode all reads and writes will
proceed as if all partitions were in a consistent state.\
                             The result of reading from a lost partition is undefined and
may be different on different nodes in the cluster.</li>\


Mime
View raw message