@Nirav,

If possible, could you please post a small sample dataset? For the
compilation problem of run-time generated code,  the thing matters is
the input column type. It would be nice if you could share some sample
data. Also, which version of Drill are you using?

I tried to use the following data in JSON format, by guessing the
column type from the query. I then run the query against the JSON file
in both 1.2 and 1.4.0. Both are running ok. However, I did notice for
one of the Project operator, Drill uses JDKClassCompiler, and the
total java source file has more than 17k line of codes, totaling 752.4
KB size.

Here is the compiling info for Project's generated code:

"
org.apache.drill.exec.compile.JDKClassCompiler:  Compiling (source
size=752.4 KiB):
"


{"userid": "USER1",
 "channelid" : 2,
 "id" : "/window/rewardtooltip/",
 "event" : "EVENT1",
 "mprizetype" : 2,
 "mgametype": "cfp",
 "misfmg" : "MG1",
 "sessionid":  "SESSION1"
}

On Tue, Dec 8, 2015 at 9:36 PM, Nirav Shah <[email protected]> wrote:
> Hi Boris,
>
> As a workaround I broke my query and rejoin results. In case need any help
> on this let me know.
>
> Best,
> Nirav
>
> On Sat, Dec 5, 2015 at 9:17 PM, Boris Chmiel <[email protected]
>> wrote:
>
>> Hello
>> I am getting the same error on huge queries. My query is about 10K
>> characters. This error is a regression and is directly related to 1.3
>> since I have already ran queries more than twice biggers (nearly 30K
>> characters) with 1.1 and 1.2 I'm downgrading to 1.2
>>
>> Boris
>>
>>
>>
>>
>>     Le Vendredi 4 décembre 2015 12h42, Nirav Shah <
>> [email protected]> a écrit :
>>
>>
>>  Hello,
>>
>> I am getting below error while running big query.
>>
>> =======================================
>>
>> Error: SYSTEM ERROR: CompileException: File
>> 'org.apache.drill.exec.compile.DrillJavaFileObject[ProjectorGen2825.java]',
>> Line 5799, Column 17: ProjectorGen2825.java:5799: error: code too large
>>     public void doEval(int inIndex, int outIndex)
>>                 ^ (compiler.err.limit.code)
>>
>>
>> Regards,
>> Nirav
>>
>>
>>
>>

Reply via email to