Re: integrate with prestodb

2017-10-16 Thread Denis Magda
Shawn, What's the purpose of Presto then if you consider holding all the data in RAM? From what I see, Presto is intended for joining the data stored in different storages. As for the Ignite persistence, here are some performance hints you might need to apply:

Re: integrate with prestodb

2017-10-16 Thread Denis Magda
Shawn, Then my suggestion would be to enable Ignite persistence [1] that will store the whole data set you have. RAM will keep only a subset for the performance benefits. Ignite SQL is full supported for the persistence, you can even join data RAM and disk only data sets. Plus, your

Re: integrate with prestodb

2017-10-16 Thread Denis Magda
Hello Shawn, Do I understand properly that you have scarce RAM resources and think to exploit Presto as an alternative SQL engine in Ignite that queries both RAM and disk data sets? If that’s the case than just enable Ignite native persistence [1] and you’ll get all the data stored on disk and

Re: integrate with prestodb

2017-10-16 Thread Alexey Kukushkin
Cross-sending to the DEV community. On Mon, Oct 16, 2017 at 12:14 PM, shawn.du wrote: > Hi community, > > I am trying to implement a connector for presto to connect ignite. > I think it will be a very interest thing to connect ignite and presto. > > In fact, currently