phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jared Katz <jared.k...@jet.com>
Subject RE: Phoenix Query Server - 413 Entity Too Large
Date Thu, 31 Mar 2016 20:25:38 GMT
Hi Josh,

Thanks a lot for the info. I began attempting to update Phoenix manually, but after digging
around a bit, I suspect Azure does some non-standard automagic configuration that I shouldn't
tamper with. I reached out to Azure for help with the upgrade. 

Thanks again,
Jared

-----Original Message-----
From: Josh Elser [mailto:josh.elser@gmail.com] 
Sent: Wednesday, March 30, 2016 6:30 PM
To: user@phoenix.apache.org
Subject: Re: Phoenix Query Server - 413 Entity Too Large

Hi Jared,

Sounds like https://issues.apache.org/jira/browse/CALCITE-780

That version of Phoenix (probably) is using Calcite-1.2.0-incubating.

You could ask the vendor to update to a newer version, or use Phoenix
4.7.0 (directly from Apache) which is using Calcite-1.6.0.

Jared Katz wrote:
> This is my first post to this mailing list, so I hope I'm doing this 
> correctly...
>
> My question is pretty simple: I'm trying to execute a pretty large DML 
> query over the Phoenix Query Server, and I get a "413 Entity Too Large"
> error. Smaller queries run fine. Is there a setting I can change in a 
> config somewhere to allow for larger queries?
>
> Thanks!
>
> Jared
>
> P.S. - I'm currently running the Phoenix Query Server on a (Ubuntu) 
> Azure HDInsights cluster, and I'm running the following version of
> Phoenix: 4.4.0.2.3.3.1-1
>

Mime
View raw message