Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
When the query is too long, we receive a `ParseException`. The bigQuery is attached, and the ddl can be found at here
I checked the cc log, the query is fully printed so it shouldn't be a network chunk issue.
The error stack is as following:
Aug 11, 2017 11:50:37 AM org.apache.asterix.api.http.server.QueryServiceServlet handleExecuteStatementException INFO: null org.apache.asterix.common.exceptions.CompilationException: null at org.apache.asterix.lang.sqlpp.parser.SQLPPParser.parse(SQLPPParser.java:267) at org.apache.asterix.api.http.server.QueryServiceServlet.executeStatement(QueryServiceServlet.java:458) at org.apache.asterix.api.http.server.QueryServiceServlet.handleRequest(QueryServiceServlet.java:418) at org.apache.asterix.api.http.server.QueryServiceServlet.post(QueryServiceServlet.java:93) at org.apache.hyracks.http.server.AbstractServlet.handle(AbstractServlet.java:78) at org.apache.hyracks.http.server.HttpRequestHandler.handle(HttpRequestHandler.java:70) at org.apache.hyracks.http.server.HttpRequestHandler.call(HttpRequestHandler.java:55) at org.apache.hyracks.http.server.HttpRequestHandler.call(HttpRequestHandler.java:36) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744) Caused by: org.apache.asterix.lang.sqlpp.parser.ParseException ... 12 more