I've just fixed possible root cause in master [1]. However, as exact use
case details is not known, may be it was something else.
Is it possible to provide more info on the use case: cache configuratioh,
model classes?
[1] https://issues.apache.org/jira/browse/IGNITE-8147
On Mon, Apr 2, 2018 at 1
Cross posting to dev.
Vladimir Ozerov, can you please take a look at NPE from query processor
(see below - GridQueryProcessor.typeByValue(GridQueryProcessor.java:1901))?
--Yakov
2018-03-29 0:19 GMT+03:00 smurphy :
> Code works in Ignite 2.1.0. Upgrading to 2.4.0 produces the stack trace
> below
>From my reading of the javadoc of org.apache.ignite.IgniteCache, only methods
that are inherited from javax.cache.Cache are transactional. So, get(..) and
put(..) are transactional, but query(..) is not..
>From the javadoc...:
Transactions
Cache API supports transactions. You can group and set o
Another update..
I changed the code (shown at the beginning of this thread) that deletes
records from:
SqlFieldsQuery sqlQuery = new SqlFieldsQuery("delete from EngineFragment
where " + criteria());
fragmentCache.query(sqlQuery.setArgs(criteria.getArgs()));
to:
_fragmentCache.remove(id);
T
I neglected to say that I also removed Spring's ChainedTransactionManager and
used SpringTransactionManager in the annotation, which also resulted in the
same stack trace..
@Transactional("igniteTxMgr")
// code that deletes from cache...
// Here is how the transaction manager is wired up..
@Bea
Code works in Ignite 2.1.0. Upgrading to 2.4.0 produces the stack trace
below. The delete statement that is causing the error is:
SqlFieldsQuery sqlQuery = new SqlFieldsQuery("delete from EngineFragment
where " + criteria());
fragmentCache.query(sqlQuery.setArgs(criteria.getArgs()));
The code abo
