@Nirav,
I tried your query on the sample dataset you sent, with the latest
Drill master branch. The query is successful, either as a standalone
query, or embedded in a CTAS.
Can you please double check if you have JDK install on "every" node in
your drill cluster? The run-time code generation
Sure, I will check and revert. Anyway thanks for spending time on this.
Regards,
Nirav
On Thu, Dec 17, 2015 at 10:10 PM, Jinfeng Ni wrote:
> @Nirav,
>
> I tried your query on the sample dataset you sent, with the latest
> Drill master branch. The query is successful,
Nirav,
Attachments typically don't work since Apache mailing lists strip them off.
Can you put the query into a gist on github or some such?
On Tue, Dec 8, 2015 at 1:09 PM, Nirav Shah wrote:
> Hi Abdel & Jacques
> I have observed that if we put more than 40 columns
@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
Let me know if you don't get attached query.
@Jinfeng,
I am not getting "JDK error".
I have tried "alter session set `exec.java_compiler` = 'JDK';" this doesn't
help.
Best,
Nirav
On Tue, Dec 8, 2015 at 8:20 PM, Ted Dunning wrote:
> Nirav,
>
> Attachments typically
Hi Abdel & Jacques
I have observed that if we put more than 40 columns with count or some
aggregation function this issue arises. I have attached query in the first
mail which gives this error, if you need sample data let me know.
If we break this query it works fine.
Thanks,
Nirav
On Dec 4, 2015
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
I am not sure but seeing a related exception while executing a big query.
org.apache.drill.common.exceptions.UserException: SYSTEM ERROR:
JaninoRuntimeException: Code attribute in class "org.apache.
drill.exec.test.generated.ProjectorGen189" grows beyond 64 KB
On Fri, Dec 4, 2015 at 5:12 PM,
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
Hi Nirav,
can you give us more information to help reproduce this issue ?
thanks
On Fri, Dec 4, 2015 at 3:42 AM, Nirav Shah wrote:
> Hello,
>
> I am getting below error while running big query.
>
> ===
>
> Error: SYSTEM ERROR:
If JDK is not available, according to [1], there would be a warning in
drillbit.log.
[1]
https://github.com/apache/drill/blob/master/exec/java-exec/src/main/java/org/apache/drill/exec/compile/JDKClassCompiler.java#L47
On Fri, Dec 4, 2015 at 11:11 AM, Jason Altekruse
I think we might want to do more than just log in this case. Here enabling
the option is a good suggestion for possibly fixing the issue, but if a JDK
is not installed it looks like there will now just be a warning logged and
the same error will be produced.
It would probably be worth it to just
I'm guessing this is due to an extremely large number of columns,
complicated expressions or extremely long column names. We test up to a
fairly large size here [1] but you may have exceeded what we test. Can you
share the query?
[1]
You may consider switching the java_compiler from DEFALT to JDK, by :
alter session set `exec.java_compiler` = 'JDK';
All Drill will automatically switch fro janino compiler to JDK, when
the source code length is beyond certain limit. If your query happens
to have smaller code than that limit,
Do we have something that checks a JDK is installed when launching Drill?
Based on this JIRA it looks like we will fall back to janino if we cannot
find a JDK. It is possible that this option does nothing if a JDK is not
available, or it may fail with an error. We should test this out in various
15 matches
Mail list logo