[GitHub] apex-malhar pull request #336: APEXMALHAR-2135 Upgrade Kafka dependency to 0...
Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/336 --- 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-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&focusedCommentId=15369453#comment-15369453 ] ASF GitHub Bot commented on APEXMALHAR-2135: Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/336 > Upgrade Kafka 0.8 input operator to support 0.8.2 client > > > Key: APEXMALHAR-2135 > URL: https://issues.apache.org/jira/browse/APEXMALHAR-2135 > Project: Apache Apex Malhar > Issue Type: Bug >Reporter: Siyuan Hua >Assignee: Thomas Weise > > Right now, if you are using 0.8.2 client with 0.8 kafka inputoperator. > You will get exception: > *java.lang.NoSuchMethodError: > > kafka.cluster.Broker.getConnectionString()Ljava/lang/String;* > > > > > > > > *at > > com.datatorrent.contrib.kafka.KafkaMetadataUtil.getBrokers(KafkaMetadataUtil.java:114)* > > > > *at > > com.datatorrent.contrib.kafka.KafkaConsumer.initBrokers(KafkaConsumer.java:131)* > > > > *at > > com.datatorrent.contrib.kafka.AbstractKafkaInputOperator.definePartitions(AbstractKafkaInputOperator.java:488)* > > > > > We should support both. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (APEXCORE-484) Increase JVM PermGen size while running engine Unit test
Vlad Rozov created APEXCORE-484:
---
Summary: Increase JVM PermGen size while running engine Unit test
Key: APEXCORE-484
URL: https://issues.apache.org/jira/browse/APEXCORE-484
Project: Apache Apex Core
Issue Type: Task
Affects Versions: 3.5.0
Reporter: Vlad Rozov
Assignee: Vlad Rozov
Priority: Minor
Build in travis-ci environment fails with OutOfMemoryError due to insufficient
PermGen:
{noformat}
2016-07-09 18:29:22,507 [main] INFO event.ExecutionEventLogger mojoStarted -
2016-07-09 18:29:22,507 [main] INFO event.ExecutionEventLogger mojoStarted -
--- maven-assembly-plugin:2.2-beta-5:single (app-package-assembly) @ mydtapp ---
2016-07-09 18:29:29,911 [main] INFO event.ExecutionEventLogger logResult -
2016-07-09 18:29:29,911 [main] INFO event.ExecutionEventLogger logResult -
BUILD FAILURE
2016-07-09 18:29:29,911 [main] INFO event.ExecutionEventLogger logStats -
2016-07-09 18:29:29,911 [main] INFO event.ExecutionEventLogger logStats -
Total time: 15.632 s
2016-07-09 18:29:29,911 [main] INFO event.ExecutionEventLogger logStats -
Finished at: 2016-07-09T18:29:29+00:00
2016-07-09 18:29:32,083 [main] INFO event.ExecutionEventLogger logStats -
Final Memory: 141M/1787M
2016-07-09 18:29:32,084 [main] INFO event.ExecutionEventLogger sessionEnded -
2016-07-09 18:29:32,084 [main] ERROR support.StramTestSupport$1 logSummary -
PermGen space -> [Help 1]
2016-07-09 18:29:32,084 [main] ERROR support.StramTestSupport$1 execute -
2016-07-09 18:29:32,084 [main] ERROR support.StramTestSupport$1 execute - To
see the full stack trace of the errors, re-run Maven with the -e switch.
2016-07-09 18:29:32,086 [main] ERROR support.StramTestSupport$1 execute -
Re-run Maven using the -X switch to enable full debug logging.
2016-07-09 18:29:32,086 [main] ERROR support.StramTestSupport$1 execute -
2016-07-09 18:29:32,086 [main] ERROR support.StramTestSupport$1 execute - For
more information about the errors and possible solutions, please read the
following articles:
2016-07-09 18:29:32,086 [main] ERROR support.StramTestSupport$1 execute - [Help
1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (APEXCORE-484) Increase JVM PermGen size while running engine Unit test
[
https://issues.apache.org/jira/browse/APEXCORE-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369700#comment-15369700
]
ASF GitHub Bot commented on APEXCORE-484:
-
GitHub user vrozov opened a pull request:
https://github.com/apache/apex-core/pull/354
APEXCORE-484 - Increase JVM PermGen size while running engine Unit test
@tweise please review
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vrozov/apex-core APEXCORE-484
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-core/pull/354.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 #354
commit 8007b863b0a565f393f95ba2e18a5e3ec7fbe40c
Author: Vlad Rozov
Date: 2016-07-10T16:08:15Z
APEXCORE-484 - Increase JVM PermGen size while running engine Unit test
> Increase JVM PermGen size while running engine Unit test
>
>
> Key: APEXCORE-484
> URL: https://issues.apache.org/jira/browse/APEXCORE-484
> Project: Apache Apex Core
> Issue Type: Task
>Affects Versions: 3.5.0
>Reporter: Vlad Rozov
>Assignee: Vlad Rozov
>Priority: Minor
>
> Build in travis-ci environment fails with OutOfMemoryError due to
> insufficient PermGen:
> {noformat}
> 2016-07-09 18:29:22,507 [main] INFO event.ExecutionEventLogger mojoStarted -
> 2016-07-09 18:29:22,507 [main] INFO event.ExecutionEventLogger mojoStarted -
> --- maven-assembly-plugin:2.2-beta-5:single (app-package-assembly) @ mydtapp
> ---
> 2016-07-09 18:29:29,911 [main] INFO event.ExecutionEventLogger logResult -
>
> 2016-07-09 18:29:29,911 [main] INFO event.ExecutionEventLogger logResult -
> BUILD FAILURE
> 2016-07-09 18:29:29,911 [main] INFO event.ExecutionEventLogger logStats -
>
> 2016-07-09 18:29:29,911 [main] INFO event.ExecutionEventLogger logStats -
> Total time: 15.632 s
> 2016-07-09 18:29:29,911 [main] INFO event.ExecutionEventLogger logStats -
> Finished at: 2016-07-09T18:29:29+00:00
> 2016-07-09 18:29:32,083 [main] INFO event.ExecutionEventLogger logStats -
> Final Memory: 141M/1787M
> 2016-07-09 18:29:32,084 [main] INFO event.ExecutionEventLogger sessionEnded
> -
> 2016-07-09 18:29:32,084 [main] ERROR support.StramTestSupport$1 logSummary -
> PermGen space -> [Help 1]
> 2016-07-09 18:29:32,084 [main] ERROR support.StramTestSupport$1 execute -
> 2016-07-09 18:29:32,084 [main] ERROR support.StramTestSupport$1 execute - To
> see the full stack trace of the errors, re-run Maven with the -e switch.
> 2016-07-09 18:29:32,086 [main] ERROR support.StramTestSupport$1 execute -
> Re-run Maven using the -X switch to enable full debug logging.
> 2016-07-09 18:29:32,086 [main] ERROR support.StramTestSupport$1 execute -
> 2016-07-09 18:29:32,086 [main] ERROR support.StramTestSupport$1 execute - For
> more information about the errors and possible solutions, please read the
> following articles:
> 2016-07-09 18:29:32,086 [main] ERROR support.StramTestSupport$1 execute -
> [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] apex-core pull request #354: APEXCORE-484 - Increase JVM PermGen size while ...
GitHub user vrozov opened a pull request: https://github.com/apache/apex-core/pull/354 APEXCORE-484 - Increase JVM PermGen size while running engine Unit test @tweise please review You can merge this pull request into a Git repository by running: $ git pull https://github.com/vrozov/apex-core APEXCORE-484 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-core/pull/354.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 #354 commit 8007b863b0a565f393f95ba2e18a5e3ec7fbe40c Author: Vlad Rozov Date: 2016-07-10T16:08:15Z APEXCORE-484 - Increase JVM PermGen size while running engine Unit test --- 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] [Created] (APEXCORE-485) Upgrade maven surefire plugin to the latest version
Vlad Rozov created APEXCORE-485: --- Summary: Upgrade maven surefire plugin to the latest version Key: APEXCORE-485 URL: https://issues.apache.org/jira/browse/APEXCORE-485 Project: Apache Apex Core Issue Type: Task Reporter: Vlad Rozov Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (APEXCORE-485) Upgrade maven surefire plugin to the latest version
[ https://issues.apache.org/jira/browse/APEXCORE-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov reassigned APEXCORE-485: --- Assignee: Vlad Rozov > Upgrade maven surefire plugin to the latest version > --- > > Key: APEXCORE-485 > URL: https://issues.apache.org/jira/browse/APEXCORE-485 > Project: Apache Apex Core > Issue Type: Task >Reporter: Vlad Rozov >Assignee: Vlad Rozov >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15369851#comment-15369851 ] Thomas Weise commented on APEXCORE-483: --- If Apex has a newer version, then this version should be first in the classpath (similar to jackson). Where exactly does the problem occur? > Dependency to httpclient version 4.3.5 causing problem with newer versions of > Hadoop > > > Key: APEXCORE-483 > URL: https://issues.apache.org/jira/browse/APEXCORE-483 > Project: Apache Apex Core > Issue Type: Bug >Reporter: Pramod Immaneni >Assignee: Pramod Immaneni > > Engine uses artifact org.apache.httpcomponents:httpclient:4.3.5 for kerberos > SPNEGO related functionality. This artifact does not appear as a transitive > dependency anywhere in the dependency tree including dependencies of hadoop > 2.2.0, the hadoop version we build against. However newer versions of hadoop > are including an earlier version of the above artifact version 4.2.5 in the > classpath that does not have the necessary functionality. This results in > multiple versions of the artifact to getting included in the classpath at > runtime causing runtime exceptions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (APEXCORE-485) Upgrade maven surefire plugin to the latest version
[ https://issues.apache.org/jira/browse/APEXCORE-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-485: Description: maven-surefire-plugin 2.14.1 is 3 years old and there is significant amount of bug fixes and enchancements > Upgrade maven surefire plugin to the latest version > --- > > Key: APEXCORE-485 > URL: https://issues.apache.org/jira/browse/APEXCORE-485 > Project: Apache Apex Core > Issue Type: Task >Reporter: Vlad Rozov >Assignee: Vlad Rozov >Priority: Minor > > maven-surefire-plugin 2.14.1 is 3 years old and there is significant amount > of bug fixes and enchancements -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (APEXCORE-485) Upgrade maven surefire plugin to the latest version
[ https://issues.apache.org/jira/browse/APEXCORE-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Rozov updated APEXCORE-485: Description: maven-surefire-plugin 2.14.1 is 3 years old and there is significant amount of bug fixes and enhancements provided by maven-surefire-plugin and junit 4.7 provider. (was: maven-surefire-plugin 2.14.1 is 3 years old and there is significant amount of bug fixes and enchancements ) > Upgrade maven surefire plugin to the latest version > --- > > Key: APEXCORE-485 > URL: https://issues.apache.org/jira/browse/APEXCORE-485 > Project: Apache Apex Core > Issue Type: Task >Reporter: Vlad Rozov >Assignee: Vlad Rozov >Priority: Minor > > maven-surefire-plugin 2.14.1 is 3 years old and there is significant amount > of bug fixes and enhancements provided by maven-surefire-plugin and junit 4.7 > provider. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Windowed Operator PR
+1 on merging it. This is a big feature addition. Thks Amol On Fri, Jul 8, 2016 at 4:17 PM, Siyuan Hua wrote: > +1 > > We should merge this ASAP. > I don't think we could solve all the problems in one PR and I think David's > PR is good enough that we can keep working on this incrementally and in > parallel. > > Regards, > Siyuan > > On Fri, Jul 8, 2016 at 4:10 PM, David Yan wrote: > > > Hi all, > > > > The Windowed Operator PR is ready to be merged. Thank you very much for > all > > your feedback so far. > > > > https://github.com/apache/apex-malhar/pull/319 > > > > Merging this PR will make projects related to the WindowedOperator go on > > more easily, which includes High level API, Apache Calcite support, Apex > > runner in Beam and Dedup operator. Please speak up now If you think there > > are reasons for not merging it. > > > > Also please note that all the classes and interfaces are marked > "Evolving" > > so we can always change them later. > > > > Thanks, > > > > David > > >
Re: Windowed Operator PR
+1 on merging. On Mon, Jul 11, 2016 at 11:00 AM, Amol Kekre wrote: > +1 on merging it. This is a big feature addition. > > Thks > Amol > > > On Fri, Jul 8, 2016 at 4:17 PM, Siyuan Hua wrote: > > > +1 > > > > We should merge this ASAP. > > I don't think we could solve all the problems in one PR and I think > David's > > PR is good enough that we can keep working on this incrementally and in > > parallel. > > > > Regards, > > Siyuan > > > > On Fri, Jul 8, 2016 at 4:10 PM, David Yan wrote: > > > > > Hi all, > > > > > > The Windowed Operator PR is ready to be merged. Thank you very much for > > all > > > your feedback so far. > > > > > > https://github.com/apache/apex-malhar/pull/319 > > > > > > Merging this PR will make projects related to the WindowedOperator go > on > > > more easily, which includes High level API, Apache Calcite support, > Apex > > > runner in Beam and Dedup operator. Please speak up now If you think > there > > > are reasons for not merging it. > > > > > > Also please note that all the classes and interfaces are marked > > "Evolving" > > > so we can always change them later. > > > > > > Thanks, > > > > > > David > > > > > >
Re: Windowed Operator PR
+1 for merging and incremental additions. ~ Yogi On 11 July 2016 at 11:04, Chinmay Kolhatkar wrote: > +1 on merging. > > On Mon, Jul 11, 2016 at 11:00 AM, Amol Kekre wrote: > > > +1 on merging it. This is a big feature addition. > > > > Thks > > Amol > > > > > > On Fri, Jul 8, 2016 at 4:17 PM, Siyuan Hua > wrote: > > > > > +1 > > > > > > We should merge this ASAP. > > > I don't think we could solve all the problems in one PR and I think > > David's > > > PR is good enough that we can keep working on this incrementally and in > > > parallel. > > > > > > Regards, > > > Siyuan > > > > > > On Fri, Jul 8, 2016 at 4:10 PM, David Yan > wrote: > > > > > > > Hi all, > > > > > > > > The Windowed Operator PR is ready to be merged. Thank you very much > for > > > all > > > > your feedback so far. > > > > > > > > https://github.com/apache/apex-malhar/pull/319 > > > > > > > > Merging this PR will make projects related to the WindowedOperator go > > on > > > > more easily, which includes High level API, Apache Calcite support, > > Apex > > > > runner in Beam and Dedup operator. Please speak up now If you think > > there > > > > are reasons for not merging it. > > > > > > > > Also please note that all the classes and interfaces are marked > > > "Evolving" > > > > so we can always change them later. > > > > > > > > Thanks, > > > > > > > > David > > > > > > > > > >
