Re: how do i force unit test to do whole stage codegen

Thanks Koert for the kind words. That part however is easy to fix and was surprised to have seen the old style referenced (!) Pozdrawiam, Jacek Laskowski https://medium.com/@jaceklaskowski/ Mastering Apache Spark 2 https://bit.ly/mastering-apache-spark Follow me at

Re: how do i force unit test to do whole stage codegen

its pretty much impossible to be fully up to date with spark given how fast it moves! the book is a very helpful reference On Wed, Apr 5, 2017 at 11:15 AM, Jacek Laskowski wrote: > Hi, > > I'm very sorry for not being up to date with the current style (and > "promoting" the

Re: how do i force unit test to do whole stage codegen

Hi, I'm very sorry for not being up to date with the current style (and "promoting" the old style) and am going to review that part soon. I'm very close to touch it again since I'm with Optimizer these days. Jacek On 5 Apr 2017 6:08 a.m., "Kazuaki Ishizaki" wrote: > Hi, >

Re: how do i force unit test to do whole stage codegen

got it. thats good to know. thanks! On Wed, Apr 5, 2017 at 12:07 AM, Kazuaki Ishizaki wrote: > Hi, > The page in the URL explains the old style of physical plan output. > The current style adds "*" as a prefix of each operation that the > whole-stage codegen can be apply

Re: how do i force unit test to do whole stage codegen

Hi, The page in the URL explains the old style of physical plan output. The current style adds "*" as a prefix of each operation that the whole-stage codegen can be apply to. So, in your test case, whole-stage codegen has been already enabled!! FYI. I think that it is a good topic for