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 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. > > Built source package successfully > > Launched and ran pi demo successfully. > > > > Thanks > > > > On Mon, Mar 27, 2017 at 11:53 PM, Thomas Weise wrote: > > > > > Dear Community, > > > > > > Please vote on the following Apache Apex Malhar 3.7.0 release > candidate. > > > > > > This is a source release with binary artifacts published to Maven. > > > > > > This release is based on Apex Core 3.4 and resolves 69 issues. > > > > > > List of all issues fixed: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > > version=12338771&projectId=12318824 > > > User documentation: http://apex.apache.org/docs/malhar-3.7/ > > > > > > Staging directory: > > > https://dist.apache.org/repos/dist/dev/apex/apache-apex- > > malhar-3.7.0-RC1/ > > > Source zip: > > > https://dist.apache.org/repos/dist/dev/apex/apache-apex- > > > malhar-3.7.0-RC1/apache-apex-malhar-3.7.0-source-release.zip > > > Source tar.gz: > > > https://dist.apache.org/repos/dist/dev/apex/apache-apex- > > > malhar-3.7.0-RC1/apache-apex-malhar-3.7.0-source-release.tar.gz > > > Maven staging repository: > > > https://repository.apache.org/content/repositories/orgapacheapex-1022/ > > > > > > Git source: > > > https://git-wip-us.apache.org/repos/asf?p=apex-malhar.git;a= > > > commit;h=refs/tags/v3.7.0-RC1 > > > (commit: 207b373f2f828636a03294bb388a279d03c5593b) > > > > > > PGP key: > > > http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=t...@apache.org > > > KEYS file: > > > https://dist.apache.org/repos/dist/release/apex/KEYS > > > > > > More information at: > > > http://apex.apache.org > > > > > > Please try the release and vote; vote will be open for at least 72 > hours. > > > > > > [ ] +1 approve (and what verification was done) > > > [ ] -1 disapprove (and reason why) > > > > > > http://www.apache.org/foundation/voting.html > > > > > > How to verify release candidate: > > > > > > http://apex.apache.org/verification.html > > > > > > Thanks, > > > Thomas > > > > > >
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 On Thu, Mar 30, 2017 at 12:35 PM, Tushar Gosavi wrote: > +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 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. > > > Built source package successfully > > > Launched and ran pi demo successfully. > > > > > > Thanks > > > > > > On Mon, Mar 27, 2017 at 11:53 PM, Thomas Weise wrote: > > > > > > > Dear Community, > > > > > > > > Please vote on the following Apache Apex Malhar 3.7.0 release > > candidate. > > > > > > > > This is a source release with binary artifacts published to Maven. > > > > > > > > This release is based on Apex Core 3.4 and resolves 69 issues. > > > > > > > > List of all issues fixed: > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > > > version=12338771&projectId=12318824 > > > > User documentation: http://apex.apache.org/docs/malhar-3.7/ > > > > > > > > Staging directory: > > > > https://dist.apache.org/repos/dist/dev/apex/apache-apex- > > > malhar-3.7.0-RC1/ > > > > Source zip: > > > > https://dist.apache.org/repos/dist/dev/apex/apache-apex- > > > > malhar-3.7.0-RC1/apache-apex-malhar-3.7.0-source-release.zip > > > > Source tar.gz: > > > > https://dist.apache.org/repos/dist/dev/apex/apache-apex- > > > > malhar-3.7.0-RC1/apache-apex-malhar-3.7.0-source-release.tar.gz > > > > Maven staging repository: > > > > https://repository.apache.org/content/repositories/ > orgapacheapex-1022/ > > > > > > > > Git source: > > > > https://git-wip-us.apache.org/repos/asf?p=apex-malhar.git;a= > > > > commit;h=refs/tags/v3.7.0-RC1 > > > > (commit: 207b373f2f828636a03294bb388a279d03c5593b) > > > > > > > > PGP key: > > > > http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=t...@apache.org > > > > KEYS file: > > > > https://dist.apache.org/repos/dist/release/apex/KEYS > > > > > > > > More information at: > > > > http://apex.apache.org > > > > > > > > Please try the release and vote; vote will be open for at least 72 > > hours. > > > > > > > > [ ] +1 approve (and what verification was done) > > > > [ ] -1 disapprove (and reason why) > > > > > > > > http://www.apache.org/foundation/voting.html > > > > > > > > How to verify release candidate: > > > > > > > > http://apex.apache.org/verification.html > > > > > > > > Thanks, > > > > Thomas > > > > > > > > > >
[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 > > > Key: APEXCORE-656 > URL: https://issues.apache.org/jira/browse/APEXCORE-656 > Project: Apache Apex Core > Issue Type: Dependency upgrade >Reporter: Vlad Rozov >Assignee: Vlad Rozov >Priority: Trivial > Fix For: 3.6.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
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 type, priority and other JIRA fields. In many cases default values are not the best one. Committer responsibility 1. Resolve the JIRA with proper resolution 2. Verify that other JIRA fields (type, priority, assignee) are correct Please remove [VOTE] from the subject line if not voting on the release. Thank you, Vlad //On 3/29/17 23:09, 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 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. Built source package successfully Launched and ran pi demo successfully. Thanks On Mon, Mar 27, 2017 at 11:53 PM, Thomas Weise wrote: Dear Community, Please vote on the following Apache Apex Malhar 3.7.0 release candidate. This is a source release with binary artifacts published to Maven. This release is based on Apex Core 3.4 and resolves 69 issues. List of all issues fixed: https://issues.apache.org/jira/secure/ReleaseNote.jspa? version=12338771&projectId=12318824 User documentation: http://apex.apache.org/docs/malhar-3.7/ Staging directory: https://dist.apache.org/repos/dist/dev/apex/apache-apex- malhar-3.7.0-RC1/ Source zip: https://dist.apache.org/repos/dist/dev/apex/apache-apex- malhar-3.7.0-RC1/apache-apex-malhar-3.7.0-source-release.zip Source tar.gz: https://dist.apache.org/repos/dist/dev/apex/apache-apex- malhar-3.7.0-RC1/apache-apex-malhar-3.7.0-source-release.tar.gz Maven staging repository: https://repository.apache.org/content/repositories/orgapacheapex-1022/ Git source: https://git-wip-us.apache.org/repos/asf?p=apex-malhar.git;a= commit;h=refs/tags/v3.7.0-RC1 (commit: 207b373f2f828636a03294bb388a279d03c5593b) PGP key: http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=t...@apache.org KEYS file: https://dist.apache.org/repos/dist/release/apex/KEYS More information at: http://apex.apache.org Please try the release and vote; vote will be open for at least 72 hours. [ ] +1 approve (and what verification was done) [ ] -1 disapprove (and reason why) http://www.apache.org/foundation/voting.html How to verify release candidate: http://apex.apache.org/verification.html Thanks, Thomas
[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: https://issues.apache.org/jira/browse/APEXMALHAR-2464 Project: Apache Apex Malhar Issue Type: Sub-task Reporter: Velineni Lakshmi Prasanna Assignee: Velineni Lakshmi Prasanna Priority: Minor Malhar currently depends on apex-core 3.4. With this version of apex-core, tests are failing for examples such as exactly-once, maprapp, unifiers and also fixedwidthparser, xmlparser which are grouped under parser example. So, will be moved once apex-core dependency for malhar is updated to 3.5. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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 Project: Apache Apex Malhar Issue Type: Bug Reporter: Velineni Lakshmi Prasanna Priority: Minor Recently many examples were added from datatorrent/examples. This seems to have pushed the amount of logs been generated during running of tests in the build, beyond the limit of what Travis allows. This is causing Travis build to fail. This needs to be addressed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
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 link to APEXCORE-685 so that it goes into next batch of updates. On Thu, Mar 30, 2017 at 7:05 AM, Vlad Rozov wrote: > 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 type, priority and other JIRA fields. In many cases default > values are not the best one. > > Committer responsibility > 1. Resolve the JIRA with proper resolution > 2. Verify that other JIRA fields (type, priority, assignee) are correct > > Please remove [VOTE] from the subject line if not voting on the release. > > Thank you, > > Vlad > > //On 3/29/17 23:09, 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 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. >>> Built source package successfully >>> Launched and ran pi demo successfully. >>> >>> Thanks >>> >>> On Mon, Mar 27, 2017 at 11:53 PM, Thomas Weise wrote: >>> >>> Dear Community, Please vote on the following Apache Apex Malhar 3.7.0 release candidate. This is a source release with binary artifacts published to Maven. This release is based on Apex Core 3.4 and resolves 69 issues. List of all issues fixed: https://issues.apache.org/jira/secure/ReleaseNote.jspa? version=12338771&projectId=12318824 User documentation: http://apex.apache.org/docs/malhar-3.7/ Staging directory: https://dist.apache.org/repos/dist/dev/apex/apache-apex- >>> malhar-3.7.0-RC1/ >>> Source zip: https://dist.apache.org/repos/dist/dev/apex/apache-apex- malhar-3.7.0-RC1/apache-apex-malhar-3.7.0-source-release.zip Source tar.gz: https://dist.apache.org/repos/dist/dev/apex/apache-apex- malhar-3.7.0-RC1/apache-apex-malhar-3.7.0-source-release.tar.gz Maven staging repository: https://repository.apache.org/content/repositories/orgapacheapex-1022/ Git source: https://git-wip-us.apache.org/repos/asf?p=apex-malhar.git;a= commit;h=refs/tags/v3.7.0-RC1 (commit: 207b373f2f828636a03294bb388a279d03c5593b) PGP key: http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=t...@apache.org KEYS file: https://dist.apache.org/repos/dist/release/apex/KEYS More information at: http://apex.apache.org Please try the release and vote; vote will be open for at least 72 hours. [ ] +1 approve (and what verification was done) [ ] -1 disapprove (and reason why) http://www.apache.org/foundation/voting.html How to verify release candidate: http://apex.apache.org/verification.html Thanks, Thomas >
[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
Issue Type: Dependency upgrade
Reporter: Vlad Rozov
Priority: Minor
There must be no dependencies on SNAPSHOT versions, but contrib pom.xml depends
on 0.8-SNAPSHOT version of org.couchbase.mock.CouchbaseMock
{noformat}
org.couchbase.mock
CouchbaseMock
0.8-SNAPSHOT
test
jar
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[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
>
>
> Key: APEXMALHAR-2466
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2466
> Project: Apache Apex Malhar
> Issue Type: Dependency upgrade
>Reporter: Vlad Rozov
>Priority: Minor
> Labels: contrib, easyfix, newbie
>
> There must be no dependencies on SNAPSHOT versions, but contrib pom.xml
> depends on 0.8-SNAPSHOT version of org.couchbase.mock.CouchbaseMock
> {noformat}
>
> org.couchbase.mock
> CouchbaseMock
> 0.8-SNAPSHOT
> test
> jar
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (APEXCORE-685) Update contributor guidelines
[ https://issues.apache.org/jira/browse/APEXCORE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949307#comment-15949307 ] Vlad Rozov commented on APEXCORE-685: - https://lists.apache.org/thread.html/489d1141bb3351d5f1bcd2dc13118692869797a1cc81e88ff03fdb23@%3Cdev.apex.apache.org%3E > Update contributor guidelines > - > > Key: APEXCORE-685 > URL: https://issues.apache.org/jira/browse/APEXCORE-685 > Project: Apache Apex Core > Issue Type: Task > Components: Website >Reporter: Thomas Weise > > Additions that have been discussed on the mailing list. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (APEXCORE-685) Update contributor guidelines
[ https://issues.apache.org/jira/browse/APEXCORE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949316#comment-15949316 ] Pramod Immaneni commented on APEXCORE-685: -- https://lists.apache.org/thread.html/40448aebada13fbd15ec88525b7edba13fb95095eae18c0018ddcda4@%3Cdev.apex.apache.org%3E > Update contributor guidelines > - > > Key: APEXCORE-685 > URL: https://issues.apache.org/jira/browse/APEXCORE-685 > Project: Apache Apex Core > Issue Type: Task > Components: Website >Reporter: Thomas Weise > > Additions that have been discussed on the mailing list. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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. @tushargosavi @PramodSSImmaneni Please take a look You can merge this pull request into a Git repository by running: $ git pull https://github.com/amberarrow/incubator-apex-malhar APEXMALHAR-2274.merge-pr490 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-malhar/pull/597.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 #597 commit cbe8f44c6cc2540476bc072be92138ad3781762f Author: Matt Zhang Date: 2017-01-03T22:03:35Z APEXMALHAR-2274 Handle large number of files for AbstractFileInputOperator commit 56e5af5a1a1d12202dd54932d76e4aa14ad66e7b Author: Munagala V. Ramanath Date: 2017-03-30T16:37:44Z APEXMALHAR-2274 closes #490 Merge branch 'APEXMALHAR-2274' of https://github.com/mattqzhang/apex-malhar Fix merge conflicts. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[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 by running: $ git pull https://github.com/PramodSSImmaneni/apex-malhar flume Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-malhar/pull/598.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 #598 commit 1798139de61cec96d773808e0b1406a3aed30735 Author: Chetan Narsude Date: 2017-02-19T15:57:29Z Flume source commit 98711ef414c054f881351c0c273b9421049dc889 Author: gaurav Date: 2017-02-19T15:59:56Z Storage commit b8477fab5e6064087953cb7febb441741ca2af83 Author: Chandni Singh Date: 2017-02-19T16:04:49Z Interceptor and hdfs test source commit fe53a6310a9a9a4554c83f6723ff488c8a0358c0 Author: Apex Dev Date: 2017-02-19T16:31:34Z Licensing changes to make it ready for addition into apex commit 193f6190a3f799f2a189cdb417c96f399ee17d60 Author: Pramod Immaneni Date: 2017-02-19T18:56:00Z Changed package path for files to be included under malhar. Modifications to build files for project to build under malhar. commit f3dc59ce70fe4aa1915dba56fc93f7b2c5a102cb Author: Oliver Winke Date: 2017-03-14T19:12:07Z Add and test ApplicationTests & complete README --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[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&focusedCommentId=15949952#comment-15949952 ] ASF GitHub Bot commented on APEXMALHAR-2324: Github user PramodSSImmaneni closed the pull request at: https://github.com/apache/apex-malhar/pull/475 > Add support for flume > - > > Key: APEXMALHAR-2324 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2324 > Project: Apache Apex Malhar > Issue Type: Improvement >Reporter: Pramod Immaneni >Assignee: Pramod Immaneni > > Flume support and operators are available in Megh project that DataTorrent > recently made open source under apache 2.0 license. DataTorrent would like to > contribute the flume code to Apex Malhar. > Contribution proposal: > https://docs.google.com/document/d/1BzWAwJDEUs0G42DWTuGYvM5sm0Uu5nTP7cUQOAlVs0g/edit#heading=h.hvt3x3bvj6xh > Megh is available here https://github.com/datatorrent/megh -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[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 Core
Issue Type: Bug
Reporter: Vlad Rozov
Assignee: Vlad Rozov
Fix For: 3.6.0
JarInputStream/ZipInputStream does not support valid formats of .jar/.zip file
{noformat}
java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor
at java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:309)
at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:121)
at java.util.jar.JarInputStream.(JarInputStream.java:83)
at java.util.jar.JarInputStream.(JarInputStream.java:62)
at com.datatorrent.stram.client.AppPackage.(AppPackage.java:215)
at com.datatorrent.stram.client.AppPackage.(AppPackage.java:196)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[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&focusedCommentId=15950217#comment-15950217
]
Vlad Rozov commented on APEXCORE-686:
-
The solution is to use ZipArchiveInputStream instead of JarInputStream that
allows to support such files.
> AppPackage fails when .apa contains zero length stored entry
>
>
> Key: APEXCORE-686
> URL: https://issues.apache.org/jira/browse/APEXCORE-686
> Project: Apache Apex Core
> Issue Type: Bug
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
> Fix For: 3.6.0
>
>
> JarInputStream/ZipInputStream does not support valid formats of .jar/.zip file
> {noformat}
> java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor
> at java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:309)
> at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:121)
> at java.util.jar.JarInputStream.(JarInputStream.java:83)
> at java.util.jar.JarInputStream.(JarInputStream.java:62)
> at com.datatorrent.stram.client.AppPackage.(AppPackage.java:215)
> at com.datatorrent.stram.client.AppPackage.(AppPackage.java:196)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[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 https://github.com/vrozov/apex-core APEXCORE-686 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-core/pull/502.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 #502 commit 22eb76a50afc5bd12f7479168f91e8858b014992 Author: Vlad Rozov Date: 2017-03-31T01:16:03Z APEXCORE-686 AppPackage fails when .apa contains zero length stored entry --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[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&focusedCommentId=15950218#comment-15950218
]
ASF GitHub Bot commented on APEXCORE-686:
-
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 https://github.com/vrozov/apex-core APEXCORE-686
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-core/pull/502.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 #502
commit 22eb76a50afc5bd12f7479168f91e8858b014992
Author: Vlad Rozov
Date: 2017-03-31T01:16:03Z
APEXCORE-686 AppPackage fails when .apa contains zero length stored entry
> AppPackage fails when .apa contains zero length stored entry
>
>
> Key: APEXCORE-686
> URL: https://issues.apache.org/jira/browse/APEXCORE-686
> Project: Apache Apex Core
> Issue Type: Bug
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
> Fix For: 3.6.0
>
>
> JarInputStream/ZipInputStream does not support valid formats of .jar/.zip file
> {noformat}
> java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor
> at java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:309)
> at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:121)
> at java.util.jar.JarInputStream.(JarInputStream.java:83)
> at java.util.jar.JarInputStream.(JarInputStream.java:62)
> at com.datatorrent.stram.client.AppPackage.(AppPackage.java:215)
> at com.datatorrent.stram.client.AppPackage.(AppPackage.java:196)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
