Re: Ignite in-memory + other SQL store without fully loading all data into Ignite

Hey Denis, It's been a while. Hope you've been keeping well! A meet the second week of Jan will be great. The agenda looks good too. We've been watching the calcite SQL engine wiki and task list

Re: Ignite in-memory + other SQL store without fully loading all data into Ignite

Hi Courtney, Glad to hear from you! It's been a while since we met last time. It's truly disappointing seeing you struggle with Ignite that much. Thanks for being open and kicking the discussion off. How about three of us (you, Val, and I) meet the second week of January and talk out the issues?

Re: Ignite in-memory + other SQL store without fully loading all data into Ignite

Hi Val, Thanks. You're not missing anything and we have been using Ignite persistence for years. Among the reasons we want to switch to in-memory only is how easily we seem to get corrupt nodes. I mentioned in the first email. We haven't had a situation where upgrading corrupts more than 1 of our 3

Re: Ignite in-memory + other SQL store without fully loading all data into Ignite

Hi Courtney, Thanks for your feedback! To cut the story short, Ignite implements page memory architecture. All data is split into fixed-sized pages and any page can reside either both in memory and on disk or on disk only. Since the in-memory layer and persistence layer are natively integrated -

Re: Ignite in-memory + other SQL store without fully loading all data into Ignite

I know this was over the holiday so bumping. Can anyone provide any pointers on where to start looking or anything else mentioned in the previous email? Thanks On Sat, Dec 26, 2020 at 8:39 PM Courtney Robinson wrote: > We've been using Ignite in production for almost 3 years and we love the > pl

Ignite in-memory + other SQL store without fully loading all data into Ignite

We've been using Ignite in production for almost 3 years and we love the platform but there are some increasingly frustrating points we run into. Before the holidays a few of our engineers started looking around and have now presented a serious case for migrating from Ignite. We would end up using