Re: Nested/Chained case statements generate codegen over 64k exception

[Jonathan Gray <jo...@gmail.com>]

I came back to this to try and investigate further using the latest version
of the project.  However, I don't have enough experience with the code base
to understand fully what is now happening, could someone take a look at the
testcase attached to this JIRA and run on the latest version of the code
base?

It currently appears as one branch of the code receives the code
compilation exception and so applies the fallback.  However, subsequent a
similar exception is thrown for different branches of the code (does the
non-compilable code get put into a cache somewhere?)  So, where it should
now be falling back to non-codegen it doesn't appear to completely.

On 19 May 2016 at 09:25, Jonathan Gray <jo...@gmail.com> wrote:

> That makes sense, I will take a look there first. That will at least give
> a clearer understanding of the problem space to determine when to fallback.
> On 15 May 2016 3:02 am, "Reynold Xin" <rx...@databricks.com> wrote:
>
>> It might be best to fix this with fallback first, and then figure out how
>> we can do it more intelligently.
>>
>>
>>
>> On Sat, May 14, 2016 at 2:29 AM, Jonathan Gray <jo...@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I've raised JIRA SPARK-15258 (with code attached to re-produce problem)
>>> and would like to have a go at fixing it but don't really know where to
>>> start.  Could anyone provide some pointers?
>>>
>>> I've looked at the code associated with SPARK-13242 but was hoping to
>>> find a way to avoid the codegen fallback.  Is this something that is
>>> possible?
>>>
>>> Thanks,
>>> Jon
>>>
>>
>>