Hi,
Thanks for the response.
We found an option of passing an "application provided Hibernate session" to
Ignite and reuse the same for all the cache stores involved in the
transaction. This way Ignite will use the same Hibernate session for all the
cache updates within the transaction. This is by
Hello!
I don't think you can put any data to Cache Store without actually putting
it in a cache.
Regards,
--
Ilya Kasnacheev
вт, 3 сент. 2019 г. в 14:03, bijunathg :
> Hi,
> Our application wants to do SQL queries and writes on some cached data
> (partitioned) and at the same time update
Hello Uwe,
Why don't you create separate cache corresponding to each table in rdbms?
Best Regards,
Gaurav
On Tue, Sep 3, 2019, 8:31 PM Uwe Geercken wrote:
>
> Hello,
>
> my first post here for Apache Ignite...
>
> I have a question and looking for some advice. I have data from a
> relational
Hello,
my first post here for Apache Ignite...
I have a question and looking for some advice. I have data from a relational database which I will load into Ignite. Each table from the source system has a UID (number), to uniquely identify each record.
If I understand it correctly,
Hi,
By default Ignite will handle only updates that were done using Ignite
cache API.
I guess that you have already read next article:
https://www.gridgain.com/resources/blog/apache-ignite-transactions-architecture-transaction-handling-level-3rd-party
BR,
Andrei
9/3/2019 2:03 PM, bijunathg
Hi,
Our application wants to do SQL queries and writes on some cached data
(partitioned) and at the same time update some other non-cached data in the
same transactional context. We do not want to cache everything for
optimizing the cache memory footprint.
The data-store could be any RDBMS store.
