[jira] [Updated] (APEXCORE-656) Upgrade org.apache.httpcomponents.httpclient

[ https://issues.apache.org/jira/browse/APEXCORE-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-656: Issue Type: Dependency upgrade (was: Improvement) > Upgrade org.apache.httpcomponents.httpclient

Re: [VOTE] Apache Apex Malhar Release 3.7.0 (RC1)

+1 Verified signatures Verified build successfully Verified presence of README.md, CHANGELOG.md, LICENSE, NOTICE files ~ Bhupesh ___ Bhupesh Chawda E: bhup...@datatorrent.com | Twitter: @bhupeshsc www.datatorrent.com | apex.apache.org

creating and updating JIRAs

I'd suggest to update contributor guideline to include that it is contributor responsibility 1. To assign bug to him/herself prior to starting work on a JIRA (already there) 2. If bug is already assigned and in progress, send a courtesy e-mail to the assigner and check the status. 3. Confirm

[jira] [Created] (APEXMALHAR-2464) Move exactly-once, maprapp, unifiers and remaining parser examples

Velineni Lakshmi Prasanna created APEXMALHAR-2464: - Summary: Move exactly-once, maprapp, unifiers and remaining parser examples Key: APEXMALHAR-2464 URL:

[jira] [Updated] (APEXMALHAR-2466) Upgrade org.couchbase.mock.CouchbaseMock

[ https://issues.apache.org/jira/browse/APEXMALHAR-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXMALHAR-2466: --- Labels: contrib easyfix newbie (was: ) > Upgrade org.couchbase.mock.CouchbaseMock >

[jira] [Created] (APEXMALHAR-2466) Upgrade org.couchbase.mock.CouchbaseMock

Vlad Rozov created APEXMALHAR-2466: -- Summary: Upgrade org.couchbase.mock.CouchbaseMock Key: APEXMALHAR-2466 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2466 Project: Apache Apex Malhar

Re: creating and updating JIRAs

Yep, it isn't the release managers responsibility to clean up JIRA. Everything should be in place by the time PRs are merged. For new features, the JIRA should have a sufficiently comprehensive description and/or links to documentation that can be used to compile release notes. Vlad, please add

[jira] [Created] (APEXMALHAR-2465) Travis build is failing because of excessive logging

Velineni Lakshmi Prasanna created APEXMALHAR-2465: - Summary: Travis build is failing because of excessive logging Key: APEXMALHAR-2465 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2465

[jira] [Commented] (APEXCORE-685) Update contributor guidelines

[ https://issues.apache.org/jira/browse/APEXCORE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15949307#comment-15949307 ] Vlad Rozov commented on APEXCORE-685: -

[GitHub] apex-malhar pull request #593: Apexmalhar 2274.merge matt fixes

Github user amberarrow closed the pull request at: https://github.com/apache/apex-malhar/pull/593 --- 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

[GitHub] apex-malhar pull request #597: Apexmalhar 2274.merge pr490

GitHub user amberarrow opened a pull request: https://github.com/apache/apex-malhar/pull/597 Apexmalhar 2274.merge pr490 This is just #490 with merge conflicts resolved. It looks good to me, so I'll merge it in a day or two unless I hear any additional requests for change.

Re: [VOTE] Apache Apex Malhar Release 3.7.0 (RC1)

+1 Verified file and builder integrity. Built source package successfully. Regards, - Tushar. On Thu, Mar 30, 2017 at 11:39 AM, AJAY GUPTA wrote: > In the release notes, the S3 Line by line module was in Bug. Should have > been in new feature. I have updated the JIRA

[jira] [Created] (APEXCORE-686) AppPackage fails when .apa contains zero length stored entry

Vlad Rozov created APEXCORE-686: --- Summary: AppPackage fails when .apa contains zero length stored entry Key: APEXCORE-686 URL: https://issues.apache.org/jira/browse/APEXCORE-686 Project: Apache Apex

[GitHub] apex-malhar pull request #598: Flume operator and agent

GitHub user PramodSSImmaneni opened a pull request: https://github.com/apache/apex-malhar/pull/598 Flume operator and agent This PR adds support for flume. It contains flume input operator and an agent to use on the flume side. You can merge this pull request into a Git repository

[GitHub] apex-malhar pull request #475: APEXMALHAR-2324 Megh flume

Github user PramodSSImmaneni closed the pull request at: https://github.com/apache/apex-malhar/pull/475 --- 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

[jira] [Commented] (APEXMALHAR-2324) Add support for flume

[ https://issues.apache.org/jira/browse/APEXMALHAR-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15949952#comment-15949952 ] ASF GitHub Bot commented on APEXMALHAR-2324: Github user PramodSSImmaneni closed the pull

[jira] [Commented] (APEXMALHAR-2462) Move JDBC related examples from datatorrent examples to apex-malhar examples

[ https://issues.apache.org/jira/browse/APEXMALHAR-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948466#comment-15948466 ] Thomas Weise commented on APEXMALHAR-2462: -- I would think that "jdbc" would be the

[jira] [Updated] (APEXMALHAR-2303) S3 Line By Line Module

[ https://issues.apache.org/jira/browse/APEXMALHAR-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Gupta updated APEXMALHAR-2303: --- Issue Type: New Feature (was: Bug) > S3 Line By Line Module > -- >

Re: [VOTE] Apache Apex Malhar Release 3.7.0 (RC1)

In the release notes, the S3 Line by line module was in Bug. Should have been in new feature. I have updated the JIRA type to new feature. On Thu, Mar 30, 2017 at 9:49 AM, Pramod Immaneni wrote: > +1 binding > > Verified file and builder integrity. > Verified licenses. >

[jira] [Commented] (APEXCORE-685) Update contributor guidelines

[ https://issues.apache.org/jira/browse/APEXCORE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948439#comment-15948439 ] Thomas Weise commented on APEXCORE-685: ---

[GitHub] apex-core pull request #502: APEXCORE-686 AppPackage fails when .apa contain...

GitHub user vrozov opened a pull request: https://github.com/apache/apex-core/pull/502 APEXCORE-686 AppPackage fails when .apa contains zero length stored entry @PramodSSImmaneni Please review You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (APEXCORE-686) AppPackage fails when .apa contains zero length stored entry

[ https://issues.apache.org/jira/browse/APEXCORE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950217#comment-15950217 ] Vlad Rozov commented on APEXCORE-686: - The solution is to use ZipArchiveInputStream instead of

[jira] [Commented] (APEXCORE-686) AppPackage fails when .apa contains zero length stored entry

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