Re: Saving Spark Data Frames merged to master

Agree, it is ok to merge, since we are waiting for the page replacement (eviction) performance fix anyway. Spark data frames is a long-awaited feature by our users, so it does make sense to provide a complete support in 2.4. D. On Fri, Feb 9, 2018 at 2:55 PM, Denis Magda wrote: > +1 > > It was

Re: Saving Spark Data Frames merged to master

+1 It wasn’t an undiscussed merge. The question was raised here before [1]. Anyway, Anton thanks for being on guard all the times! :) [1] http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-4-release-td26031i20.html#a26807

Re: Saving Spark Data Frames merged to master

I think it's OK to merge it to 2.4, especially since the release is delayed. This is a fairly small feature which is fully isolated from everything else, so there are no risks. At the same time, it makes data frames integration much more valuable. -Val On Fri, Feb 9, 2018 at 5:20 AM, Nikolay Izhi

Re: Saving Spark Data Frames merged to master

Hello, Anton. I have no any objections. Seems like some kind of misunderstanding from my side. As far as I can understand mail from Dmitriy Setrakyan [1] He agreed to include IGNITE-7337 to 2.4. If the Ccommuntiy decides to postpone this feature in 2.5 release I'm fully OK with it. [1] http://a

Re: Saving Spark Data Frames merged to master

Nikolay, 2.4 is almost ready to be released. We're fixing final issues to provide stable and fast release. Merging something to 2.4 except blockers is not possible at this phase of release process. Hope, 2.5, with your changes, will be released soon :) On Fri, Feb 9, 2018 at 7:19 AM, Nikolay Izh