You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/07/07 20:17:04 UTC

[jira] [Resolved] (CALCITE-780) HTTP error 413 when sending a long string to the Avatica server

     [ https://issues.apache.org/jira/browse/CALCITE-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-780.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.4.0-incubating

Fixed in http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/03111d2b.

> HTTP error 413 when sending a long string to the Avatica server
> ---------------------------------------------------------------
>
>                 Key: CALCITE-780
>                 URL: https://issues.apache.org/jira/browse/CALCITE-780
>             Project: Calcite
>          Issue Type: Bug
>          Components: avatica
>            Reporter: Lukas Lalinsky
>            Assignee: Julian Hyde
>             Fix For: 1.4.0-incubating
>
>
> When I try to execute a query with a very long string, the server returns error 413 "entity too large". My assumption is that this happens, because the RPC uses a HTTP header to pass the RPC request data and most HTTP parsers do not like long headers. The best solution would be to use the body of the HTTP request. It could be made backward-compatible, by checking the header first and if it's missing, then read the body.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)