You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/08/14 04:55:01 UTC
[jira] [Commented] (ASTERIXDB-2028) Cannot parse a too-long query
[ https://issues.apache.org/jira/browse/ASTERIXDB-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16125237#comment-16125237 ]
ASF subversion and git services commented on ASTERIXDB-2028:
------------------------------------------------------------
Commit 60f89981d2d9961b3ebc265606d00a95b3d58fc2 in asterixdb's branch refs/heads/master from [~tillw]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=60f8998 ]
[ASTERIXDB-2028][SQL] No recursion for list creation
- user model changes: no more dangling comma for lists in SQL++
- storage format changes: no
- interface changes: no
details:
- change the production to create expression lists to avoid recursion
- report the class name of Errors (not just the message)
Change-Id: I86b65371bc007b57fd80542f6530db12dd936242
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1936
Sonar-Qube: Jenkins <je...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <je...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Yingyi Bu <bu...@gmail.com>
> Cannot parse a too-long query
> -----------------------------
>
> Key: ASTERIXDB-2028
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2028
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: API - HTTP API
> Reporter: Jianfeng Jia
> Assignee: Till
> Attachments: bigQuery, bigQuery
>
>
> When the query is too long, we receive a `ParseException`. The bigQuery is attached, and the ddl can be found at [here|https://github.com/ISG-ICS/cloudberry/blob/81e55ab86d4a8acb2a12a57d8c7334f6f970fabf/examples/twittermap/noah/src/main/resources/twitter/aql/ddl.aql]
> 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:
> {code}
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)