You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/12/15 14:02:46 UTC

[jira] [Commented] (FLINK-3173) Bump org.apache.httpcomponents.httpclient version to 4.2.6

    [ https://issues.apache.org/jira/browse/FLINK-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058023#comment-15058023 ] 

ASF GitHub Bot commented on FLINK-3173:
---------------------------------------

GitHub user tillrohrmann opened a pull request:

    https://github.com/apache/flink/pull/1456

    [FLINK-3173] Bump httpclient and httpcore to version 4.2.6 to solve bug in http client

    The bug prevents the `TwitterStream` example from working.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tillrohrmann/flink FLINK-3173

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/1456.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1456
    
----
commit 65c5604c5cb484ee772aa1882d2a0b52171ff0bb
Author: Till Rohrmann <tr...@apache.org>
Date:   2015-12-15T13:00:31Z

    [FLINK-3173] Bump httpclient and httpcore to version 4.2.6 to solve bug in http client

----


> Bump org.apache.httpcomponents.httpclient version to 4.2.6
> ----------------------------------------------------------
>
>                 Key: FLINK-3173
>                 URL: https://issues.apache.org/jira/browse/FLINK-3173
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Minor
>
> Currently, the {{TwitterStream}} example is not working with the {{TwitterSource}}, because we're using httpclient version 4.2. There seems to be bug in the httpclient which causes the connection to the Twitter stream to fail. With version 4.2.6 this issue is fixed. I propose, therefore, to bump the version to 4.2.6.



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