[
https://issues.apache.org/jira/browse/CALCITE-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved CALCITE-1117.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: next)
1.7.0
Fixed in
https://git1-us-west.apache.org/repos/asf?p=calcite.git;a=commit;h=ec3d8d37c9d38a8f041c2b1b3aa68711c085b939
> Use commons httpclient instead of JDK http client
> -------------------------------------------------
>
> Key: CALCITE-1117
> URL: https://issues.apache.org/jira/browse/CALCITE-1117
> Project: Calcite
> Issue Type: Sub-task
> Components: avatica
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 1.7.0
>
>
> I've been stumbling around, trying to get a better understanding of how
> HttpURLConnection works (with http/1.1), applying it to some of the knowledge
> I have with the distributed key-value stores on Hadoop I'm familiar with.
> Along the way, I found lots of recommendations to move to Apache Commons
> HttpClient (http://hc.apache.org) with the broad suggestion that "it's just
> generally better". I mocked this up and was pleasantly surprised to find that
> this netted about a 20% improvement over the existing http client
> implementation (with a stubbed-out JDBC driver inside Avatica -- just
> measuring Avatica itself).
> Thankfully, we have an interface for the http client, so it should be easy to
> add a new implementation with a factory to do some client-side configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
