1. why do we need the storage (whether native or 3rd party)? I need the
storage because 1) down time for production deployment. 2) the data in the
cache may be crashed and All ignite clusters are completed down (sorry)
2. So I need a storage to store the data that have been committed when
Hi,
MVCC in Ignite is targeted to provide transactional consistency
guarantees. I suppose that with eventually consistent 3rd party store
it would be impossible to give much guarantees in general. Do think
that such eventually consistent store will be widely used? What kind
of guarantees should
Hi Ilya,
It'd better if this was mentioned in Ignite Doc.
It seems very limited if MVCC only supports the Ignite native persistence.
Yes, supporting MVCC in 3rd party persistence is challenging. However, do
we really need MVCC when the data from Cache (where MVCC already enabled) is
ready
Hello!
Yes, unfortunately MVCC does not support 3rd party persistence (and I'm not
sure that it is possible by design).
Regards,
--
Ilya Kasnacheev
чт, 28 февр. 2019 г. в 00:29, xmw45688 :
> Hi Ilya,
>
> Since I'm using Cassandra as data store, it raises the following exceptions
> once MVCC
Hi Ilya,
Since I'm using Cassandra as data store, it raises the following exceptions
once MVCC is enabled -
class org.apache.ignite.IgniteCheckedException: Grid configuration parameter
invalid: readThrough cannot be used with TRANSACTIONAL_SNAPSHOT atomicity
mode
at
It seems that this enhancement has not been implemented yet for the following
cases:
trx.start() {
1. update t1 set col1='a' where col2='c';
2. update the same table t1 with cache API.
}
trx.end();
Can someone confirm?
many thanks, Xinmin
--
Sent from:
No, this is not implemented yet. Here is the ticket where you can track the
progress: https://issues.apache.org/jira/browse/IGNITE-3478
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi, val，is 2.3.0 version fix this problem? when I update to 2.3.0 and I get
IgniteSQLException：
Exception in thread "main" javax.cache.CacheException: class
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
update some keys because they had been modified concurrently
sage in context:
http://apache-ignite-users.70518.x6.nabble.com/same-cache-cannot-update-twice-in-one-transaction-tp14639p15270.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
/same-cache-cannot-update-twice-in-one-transaction-tp14639p15258.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
in context:
http://apache-ignite-users.70518.x6.nabble.com/same-cache-cannot-update-twice-in-one-transaction-tp14639p15225.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
-users.70518.x6.nabble.com/same-cache-cannot-update-twice-in-one-transaction-tp14639p15145.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
ile/n15108/IgniteDemoV2-log4j.zip>
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/same-cache-cannot-update-twice-in-one-transaction-tp14639p15108.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
-update-twice-in-one-transaction-tp14639p14888.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
14 matches
Mail list logo
