[jira] [Updated] (APEXCORE-483) Dependency to httpclient version 4.3.5 causing problem with newer versions of Hadoop

[ https://issues.apache.org/jira/browse/APEXCORE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni updated APEXCORE-483: - Summary: Dependency to httpclient version 4.3.5 causing problem with newer versions of

[jira] [Comment Edited] (APEXCORE-483) Dependency to httpclient version 3.5 causing problem with newer versions of Hadoop

[ https://issues.apache.org/jira/browse/APEXCORE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369382#comment-15369382 ] Pramod Immaneni edited comment on APEXCORE-483 at 7/10/16 1:57 AM: --- To

[jira] [Commented] (APEXCORE-483) Dependency to httpclient version 3.5 causing problem with newer versions of Hadoop

[ https://issues.apache.org/jira/browse/APEXCORE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369382#comment-15369382 ] Pramod Immaneni commented on APEXCORE-483: -- To get this around the problem we will shade the

Re: Issue with httpclient

We could go with a separate artifact although I think we should have a stronger reason than builds to create one, such as the likelihood of others needing it. If it were shaded internally, in every build the mapping would still remain the same isn't it, so there would be no changes to things like

[jira] [Created] (APEXCORE-483) Dependency to httpclient version 3.5 causing problem with newer versions of Hadoop

Pramod Immaneni created APEXCORE-483: Summary: Dependency to httpclient version 3.5 causing problem with newer versions of Hadoop Key: APEXCORE-483 URL: https://issues.apache.org/jira/browse/APEXCORE-483

[GitHub] apex-core pull request #353: Removed deployment documentation as it is inclu...

GitHub user PramodSSImmaneni opened a pull request: https://github.com/apache/apex-core/pull/353 Removed deployment documentation as it is included in the release documentation A pull request has been submitted to apex-site to deploy documentation as part of the release process.

[GitHub] apex-site pull request #42: Added updating documentation to release process

GitHub user PramodSSImmaneni opened a pull request: https://github.com/apache/apex-site/pull/42 Added updating documentation to release process I had some updates to docs and had noticed that we don't include building and staging documentation as part of the release process even

[jira] [Commented] (APEXMALHAR-2135) Upgrade Kafka 0.8 input operator to support 0.8.2 client

[ https://issues.apache.org/jira/browse/APEXMALHAR-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369260#comment-15369260 ] ASF GitHub Bot commented on APEXMALHAR-2135: GitHub user tweise opened a pull request:

[jira] [Updated] (APEXMALHAR-2135) Upgrade Kafka 0.8 input operator to support 0.8.2 client

[ https://issues.apache.org/jira/browse/APEXMALHAR-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2135: - Summary: Upgrade Kafka 0.8 input operator to support 0.8.2 client (was: Upgrade

[jira] [Updated] (APEXMALHAR-2135) Upgrade Kafka 0.8 input operator to support 0.8.2

[ https://issues.apache.org/jira/browse/APEXMALHAR-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2135: - Assignee: Thomas Weise > Upgrade Kafka 0.8 input operator to support 0.8.2 >

[jira] [Updated] (APEXMALHAR-2135) Upgrade Kafka 0.8 input operator to support 0.8.2

[ https://issues.apache.org/jira/browse/APEXMALHAR-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated APEXMALHAR-2135: - Summary: Upgrade Kafka 0.8 input operator to support 0.8.2 (was: Upgrade Kafka 0.8

[GitHub] apex-core pull request #352: Fixed the typo while determing the pending depl...

Github user asfgit closed the pull request at: https://github.com/apache/apex-core/pull/352 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Issue with httpclient

Keeping shaded dependencies as separate artifacts simplifies the build and allows others to use them as well. Why shade a dependency on every build invocation when it never changes? We could also consider building a single shaded artifact for multiple dependencies in case we are adding more in

[GitHub] apex-core pull request #350: APEXCORE-222 Purging the stale data present in ...

GitHub user sandeshh reopened a pull request: https://github.com/apache/apex-core/pull/350 APEXCORE-222 Purging the stale data present in the bufferserver, dire… …ctly from the streaming container. You can merge this pull request into a Git repository by running: $ git

[jira] [Commented] (APEXCORE-222) Delegate Buffer Server purge to StreamingContainer

[ https://issues.apache.org/jira/browse/APEXCORE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369135#comment-15369135 ] ASF GitHub Bot commented on APEXCORE-222: - GitHub user sandeshh reopened a pull request:

[jira] [Commented] (APEXCORE-222) Delegate Buffer Server purge to StreamingContainer

[ https://issues.apache.org/jira/browse/APEXCORE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369134#comment-15369134 ] ASF GitHub Bot commented on APEXCORE-222: - Github user sandeshh closed the pull request at:

[GitHub] apex-core pull request #350: APEXCORE-222 Purging the stale data present in ...

Github user sandeshh closed the pull request at: https://github.com/apache/apex-core/pull/350 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature