Re: [VOTE] Retire Gearpump

[Manu Zhang]

Thanks all.

This vote has passed with 6 +1s and 0 -1s.
I will start a vote on IPMC.

On Fri, Sep 14, 2018 at 10:31 AM Kam Kasravi  wrote:

>  +1
> Kam Kasrav
> On Thursday, September 13, 2018, 6:45:36 PM PDT, Stanley Xu <
> sx.a...@googlemail.com.INVALID> wrote:
>
>  +1
>
> Regards,
> Qian Xu (Stanley)
>
> On Fri, Sep 14, 2018 at 2:32 AM, Karol Brejna 
> wrote:
>
> > +1
> >
> > W dniu czw., 13.09.2018 o 07:54 Manu Zhang 
> > napisał(a):
> >
> > > Hi all,
> > >
> > > As per previous discussion
> > > <
> > > https://lists.apache.org/thread.html/77946cfff4557cf10c13c2d35fc165
> > 223583e58c2f7705319acabcf4@%3Cdev.gearpump.apache.org%3E
> > > >,
> > > we agree that it would be better for Gearpump to retire from the ASF
> > > incubator. Here comes the formal vote.
> > >
> > > [ ] +1 to retire
> > > [ ] -1 not to retire because...
> > >
> > > Here's my +1.
> > >
> > > This will be open for at least 72 hours and is a majority vote.
> > >
> > > Thanks,
> > > Manu Zhang
> > >
> >
>
>
>
> --
> Qian Xu (Stanley)
> ___
>
> This e-mail may contain confidential material for the sole use of the
> intended recipient(s). Any review or distribution by others is strictly
> prohibited. If you are not the intended recipient, please contact the
> sender and delete all copies.

[VOTE] Retire Gearpump

[Manu Zhang]

Hi all,

As per previous discussion
<https://lists.apache.org/thread.html/77946cfff4557cf10c13c2d35fc165223583e58c2f7705319acabcf4@%3Cdev.gearpump.apache.org%3E>,
we agree that it would be better for Gearpump to retire from the ASF
incubator. Here comes the formal vote.

[ ] +1 to retire
[ ] -1 not to retire because...

Here's my +1.

This will be open for at least 72 hours and is a majority vote.

Thanks,
Manu Zhang

Re: [DISCUSS] Retire Gearpump

[Manu Zhang]

Thanks everyone for sharing your thoughts. It seems we've reached an
consensus.
I'm going to start a formal vote thread and please cast your vote there.

Thanks,
Manu





On Wed, Sep 12, 2018 at 8:22 PM Karol Brejna  wrote:

> Manu,
>
> Thanks for bringing this difficult topic.
>
> I was struggling with it myself.
>
> Here are my thoughts:
>
> Our main objectives were to build the community and gain more adoption.
>
> Although there was some considerable interest, I think we were not able to
> build a stable and sizable community around our project.
>
> We have identified some "technical" goals to achieve as the next steps.
> Without a broader community, I think we won't be able to keep a decent
> development activity and release pace.
>
> It doesn't look that the situation (community) would change any time soon,
> so - with a heavy heart - I must agree that it would be only fair to the
> Apache community to retire Gearpump.
>
> I am hoping we'll continue working on Gearpump in some other "formula" in
> the future, as it has some strengths and is cool to use and develop ;-)
>
> Regards,
> Karol
>
> On Sun, Sep 9, 2018 at 9:38 AM Manu Zhang  wrote:
>
> > Hi all,
> >
> > Gearpump has been an Apache incubator since 2016-03-08. Thank you all for
> > help to  incubate Gearpump and keep it move forward.
> >
> > The activity around Gearpump has, however, slowed down and the last
> release
> > was more than one year ago. There is no sign of a growing community,
> which
> > is a requirement to be a Apache TLP. The long period of release process
> has
> > made things even harder for such a slim community.
> >
> > I don't see a future for Gearpump within Apache so it's better off to
> > leave.
> >
> > What do you think ?
> >
> > Thanks,
> > Manu Zhang
> >
>

[DISCUSS] Retire Gearpump

[Manu Zhang]

Hi all,

Gearpump has been an Apache incubator since 2016-03-08. Thank you all for
help to  incubate Gearpump and keep it move forward.

The activity around Gearpump has, however, slowed down and the last release
was more than one year ago. There is no sign of a growing community, which
is a requirement to be a Apache TLP. The long period of release process has
made things even harder for such a slim community.

I don't see a future for Gearpump within Apache so it's better off to
leave.

What do you think ?

Thanks,
Manu Zhang

Re: Late podling report

[Manu Zhang]

Hi Justin,

Thanks for asking. Our mentor JB Onofre has been supportive but I'm
thinking about retiring Gearpump.
I will send out a mail to dev list to discuss

Thanks,
Manu

On Fri, Sep 7, 2018 at 4:36 PM Justin Mclean  wrote:

> Hi,
>
> I'm curious is there any particular reason why? Do yo have an inactive
> PPMC / mentors or need help from your mentors?
>
> If you don't report this month you are required to report next month.
>
> Thanks,
> Justin
>

Re: Late podling report

[Manu Zhang]

Sorry but we are unable to submit a report this time.

Thanks,
Manu Zhang

On Thu, Sep 6, 2018 at 8:16 PM Justin Mclean  wrote:

> Hi,
>
> Your report is late. It would be appreciated it if you can submit it ASAP
> or if you are unable to submit a report please tell us (and report next
> month instead) so the incubator report for this month can be finalised.
>
> Thanks,
> Justin
>

[jira] [Resolved] (GEARPUMP-326) Upgrade to Akka 2.5.x

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-326.
-
Resolution: Fixed

> Upgrade to Akka 2.5.x
> -
>
> Key: GEARPUMP-326
> URL: https://issues.apache.org/jira/browse/GEARPUMP-326
> Project: Apache Gearpump
>  Issue Type: Improvement
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
>Priority: Major
> Fix For: 0.8.5
>
>
> such that we can try out the new materializer for Akka Streams integration



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-379) Client doesn't exit when the application is terminated

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-379.
-
   Resolution: Fixed
Fix Version/s: 0.8.5

Issue resolved by pull request 249
[https://github.com/apache/incubator-gearpump/pull/249]

> Client doesn't exit when the application is terminated
> --
>
> Key: GEARPUMP-379
> URL: https://issues.apache.org/jira/browse/GEARPUMP-379
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: client
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>Assignee: Manu Zhang
>Priority: Major
> Fix For: 0.8.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEARPUMP-379) Client doesn't exit when the application is terminated

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-379:
---

 Summary: Client doesn't exit when the application is terminated
 Key: GEARPUMP-379
 URL: https://issues.apache.org/jira/browse/GEARPUMP-379
 Project: Apache Gearpump
  Issue Type: Bug
  Components: client
Affects Versions: 0.8.4
Reporter: Manu Zhang






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (GEARPUMP-379) Client doesn't exit when the application is terminated

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang reassigned GEARPUMP-379:
---

Assignee: Manu Zhang

> Client doesn't exit when the application is terminated
> --
>
> Key: GEARPUMP-379
> URL: https://issues.apache.org/jira/browse/GEARPUMP-379
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: client
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>Assignee: Manu Zhang
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-195) Single node DAG's should not show node as stalling

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-195.
-
   Resolution: Fixed
Fix Version/s: Not applicable

> Single node DAG's should not show node as stalling
> --
>
> Key: GEARPUMP-195
> URL: https://issues.apache.org/jira/browse/GEARPUMP-195
> Project: Apache Gearpump
>  Issue Type: Bug
>Affects Versions: 0.8.1
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
>Priority: Major
> Fix For: Not applicable
>
>
> DAG's with only one node should not show stalled. If a sink node is missing 
> we should either prevent the DAG from being run or not show the upstream node 
> status as stalled



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-308) window process result do not match it's semantic

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-308.
-
   Resolution: Fixed
 Assignee: Manu Zhang
Fix Version/s: 0.8.4

> window process result do not match it's semantic 
> -
>
> Key: GEARPUMP-308
> URL: https://issues.apache.org/jira/browse/GEARPUMP-308
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: streaming
>Reporter: vinoyang
>    Assignee: Manu Zhang
>Priority: Major
> Fix For: 0.8.4
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Podling Report Reminder - June 2018

[Manu Zhang]

Great！Thanks a lot

Manu

On Wed, Jun 6, 2018 at 2:00 PM Jean-Baptiste Onofré  wrote:

> Hi,
>
> I added the report on the incubator wiki and I also signed it off.
>
> Thanks !
> Regards
> JB
>
> On 05/06/2018 15:58, Manu Zhang wrote:
> > Hi all,
> >
> > This is the Gearpump podling report. Please review.
> >
> > Gearpump
> >
> >  Gearpump is a reactive real-time streaming engine based on the
> > micro-service Actor model.
> >  Gearpump has been incubating since 2016-03-08.
> >
> >  Most important issues to address in the move towards graduation:
> >
> >  1. Have frequent release cycles.
> >  2. Continue to evolve community interest and support.
> >
> >
> >  - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >  - None.
> >
> >
> >  - How has the community developed since the last report?
> >  - A contributor added Apache Kudu integration to Gearpump.
> >
> >  - How has the project developed since the last report?
> >  - 13 issues created and 17 issues resolved.
> >
> >
> >  Date of last release:
> >  2017-07-17
> >
> >
> >  When were the last committers or PMC members elected?
> >  No new committers or PMC members elected yet.
> >
> >  Signed-off-by:
> >
> >  [ ](gearpump) Jean-Baptiste Onofré
> >  [ ](gearpump) Andrew Purtell
> >  [ ](gearpump) Jarek Jarcec Cecho
> >  [ ](gearpump) Reynold Xin
> >  [ ](gearpump) Todd Lipcon
> >  [ ](gearpump) Xuefu Zhang
> >
> > On Mon, Jun 4, 2018 at 8:06 AM  wrote:
> >
> >> Dear podling,
> >>
> >> This email was sent by an automated system on behalf of the Apache
> >> Incubator PMC. It is an initial reminder to give you plenty of time to
> >> prepare your quarterly board report.
> >>
> >> The board meeting is scheduled for Wed, 20 June 2018, 10:30 am PDT.
> >> The report for your podling will form a part of the Incubator PMC
> >> report. The Incubator PMC requires your report to be submitted 2 weeks
> >> before the board meeting, to allow sufficient time for review and
> >> submission (Wed, June 06).
> >>
> >> Please submit your report with sufficient time to allow the Incubator
> >> PMC, and subsequently board members to review and digest. Again, the
> >> very latest you should submit your report is 2 weeks prior to the board
> >> meeting.
> >>
> >> Candidate names should not be made public before people are actually
> >> elected, so please do not include the names of potential committers or
> >> PPMC members in your report.
> >>
> >> Thanks,
> >>
> >> The Apache Incubator PMC
> >>
> >> Submitting your Report
> >>
> >> --
> >>
> >> Your report should contain the following:
> >>
> >> *   Your project name
> >> *   A brief description of your project, which assumes no knowledge of
> >> the project or necessarily of its field
> >> *   A list of the three most important issues to address in the move
> >> towards graduation.
> >> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> >> aware of
> >> *   How has the community developed since the last report
> >> *   How has the project developed since the last report.
> >> *   How does the podling rate their own maturity.
> >>
> >> This should be appended to the Incubator Wiki page at:
> >>
> >> https://wiki.apache.org/incubator/June2018
> >>
> >> Note: This is manually populated. You may need to wait a little before
> >> this page is created from a template.
> >>
> >> Mentors
> >> ---
> >>
> >> Mentors should review reports for their project(s) and sign them off on
> >> the Incubator wiki page. Signing off reports shows that you are
> >> following the project - projects that are not signed may raise alarms
> >> for the Incubator PMC.
> >>
> >> Incubator PMC
> >>
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Podling Report Reminder - June 2018

[Manu Zhang]

Hi all,

This is the Gearpump podling report. Please review.

Gearpump

 Gearpump is a reactive real-time streaming engine based on the
micro-service Actor model.
 Gearpump has been incubating since 2016-03-08.

 Most important issues to address in the move towards graduation:

 1. Have frequent release cycles.
 2. Continue to evolve community interest and support.


 - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
 - None.


 - How has the community developed since the last report?
 - A contributor added Apache Kudu integration to Gearpump.

 - How has the project developed since the last report?
 - 13 issues created and 17 issues resolved.


 Date of last release:
 2017-07-17


 When were the last committers or PMC members elected?
 No new committers or PMC members elected yet.

 Signed-off-by:

 [ ](gearpump) Jean-Baptiste Onofré
 [ ](gearpump) Andrew Purtell
 [ ](gearpump) Jarek Jarcec Cecho
 [ ](gearpump) Reynold Xin
 [ ](gearpump) Todd Lipcon
 [ ](gearpump) Xuefu Zhang

On Mon, Jun 4, 2018 at 8:06 AM  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 20 June 2018, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, June 06).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/June2018
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

[jira] [Resolved] (GEARPUMP-310) Upickle Deprecation

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-310.
-
   Resolution: Not A Problem
Fix Version/s: Not applicable

> Upickle Deprecation
> ---
>
> Key: GEARPUMP-310
> URL: https://issues.apache.org/jira/browse/GEARPUMP-310
> Project: Apache Gearpump
>  Issue Type: Bug
>    Reporter: Manu Zhang
>Priority: Major
> Fix For: Not applicable
>
>
> https://github.com/lihaoyi/upickle-pprint/issues/209
> We need to find an alternative. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-125) Kafka New Consumer

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-125.
-
   Resolution: Duplicate
Fix Version/s: Not applicable

> Kafka New Consumer
> --
>
> Key: GEARPUMP-125
> URL: https://issues.apache.org/jira/browse/GEARPUMP-125
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: kafka
>Affects Versions: 0.8.0
>Reporter: darion yaphet
>Assignee: darion yaphet
>Priority: Major
> Fix For: Not applicable
>
>
> Kafka 0.9 have released about half a year . In this new version it's include 
> a new redesigned consumer which is don't dependency on ZooKeeper and support 
> security features (authenticate and permissions )  . 
> [Apache Kafka 0.9 is 
> Released|http://www.confluent.io/blog/apache-kafka-0.9-is-released]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-21) support Apache Beam(Incubating) Gearpump Runner

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-21.

   Resolution: Fixed
Fix Version/s: 0.8.4

> support Apache Beam(Incubating) Gearpump Runner
> ---
>
> Key: GEARPUMP-21
> URL: https://issues.apache.org/jira/browse/GEARPUMP-21
> Project: Apache Gearpump
>  Issue Type: New Feature
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
>Priority: Major
> Fix For: 0.8.4
>
> Attachments: GearpumpRunner-DesignDocument.pdf
>
>
> This is an umbrella jira for related issues to support Apache 
> Beam(incubating) Gearpump runner.  Some links,
> * [BEAM-79 | https://issues.apache.org/jira/browse/BEAM-79] 
> * [Beam Model | 
> https://docs.google.com/presentation/d/1SHie3nwe-pqmjGum_QDznPr-B_zXCjJ2VBDGdafZme8/edit#slide=id.g12846a6162_0_5]
> * [Gearpump Runner Design Document | 
> https://drive.google.com/open?id=1nw64QUWVfT8L7FUprPGLEeNjSBpDMkn1otfLt2rHM5g]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-351) Support executor number in submit

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-351.
-
Resolution: Not A Problem

> Support executor number in submit
> -
>
> Key: GEARPUMP-351
> URL: https://issues.apache.org/jira/browse/GEARPUMP-351
> Project: Apache Gearpump
>  Issue Type: New Feature
>  Components: core
>Affects Versions: 0.8.4
>Reporter: darion yaphet
>Assignee: darion yaphet
>Priority: Minor
>
> When ClientContext submit application to cluster and add a argument executors 
> to specifies the executor number use to running job ,otherwise it will 
> running in a JVM process. We should support executor number in program API .  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-369) "executor-num" is overridden by the default value for arg "executors"(1)

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-369.
-
   Resolution: Fixed
 Assignee: Manu Zhang
Fix Version/s: 0.8.5

> "executor-num" is overridden by the default value for arg "executors"(1) 
> -
>
> Key: GEARPUMP-369
> URL: https://issues.apache.org/jira/browse/GEARPUMP-369
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: core
>Affects Versions: 0.8.4, 0.8.5
>Reporter: Hashan Gayasri Udugahapattuwa
>Assignee: Manu Zhang
>Priority: Minor
> Fix For: 0.8.5
>
>
> org/apache/gearpump/cluster/main/AppSubmitter.scala:62
> System.setProperty(Constants.APPLICATION_EXECUTOR_NUMBER, 
> config.getInt("executors").toString)
>  
> replaces the value set by system properties (gear.conf) by the default 
> value(1) even when no value is passed at as an argument. The expected 
> behaviour is to only override the value when a value is given explicitly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-151) Allow JarStore to be configured per application

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-151.
-
Resolution: Not A Problem

> Allow JarStore to be configured per application
> ---
>
> Key: GEARPUMP-151
> URL: https://issues.apache.org/jira/browse/GEARPUMP-151
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: daemon
>Affects Versions: 0.8.0
>    Reporter: Manu Zhang
>Priority: Minor
>
> Currently, JarStore is configured for the cluster. If a cluster is launched 
> with local JarStore, user has to no way to configure a distributed JarStore 
> later without restarting the cluster.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-309) the time is error in executor log

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-309.
-
Resolution: Not A Problem

> the time is error in executor log
> -
>
> Key: GEARPUMP-309
> URL: https://issues.apache.org/jira/browse/GEARPUMP-309
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: Xuetong Zhu
>Priority: Trivial
>
> KafkaSource opened at start time -292275055-05-16T16:47:04.192Z



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-342) Don't run DataSourceTask with WindowRunner unless necessary

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-342.
-
Resolution: Duplicate

> Don't run DataSourceTask with WindowRunner unless necessary
> ---
>
> Key: GEARPUMP-342
> URL: https://issues.apache.org/jira/browse/GEARPUMP-342
> Project: Apache Gearpump
>  Issue Type: Improvement
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
>Priority: Major
> Fix For: 0.8.5
>
>
> Currently, a windowed wordcount pipeline like 
> {{source.flatMap.window.groupBy.count}} will actually be executed as 
> {{source.globalWindow.flatMap.groupBy.window.count}} and 
> {{globalWindow.flatMap}} run by a {{WindowRunner}}. 
> The {{globalWindow}} is unnecessary unless {{source}} is followed by an 
> aggregation. Further, the {{globalWindow}} requires {{Watermark.MAX}} to 
> trigger emits which is not obvious for users. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-217) Add SQL support

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-217.
-
Resolution: Fixed

> Add SQL support 
> 
>
> Key: GEARPUMP-217
> URL: https://issues.apache.org/jira/browse/GEARPUMP-217
> Project: Apache Gearpump
>  Issue Type: New Feature
>  Components: streaming
>Affects Versions: 0.8.1
>    Reporter: Manu Zhang
>Assignee: Buddhi Ayesha
>Priority: Major
>  Labels: gsoc2017, mentor
>
> SQL support will allow those unfamiliar with Scala/Java to use Gearpump. I 
> propose to build SQL layer with Apache Calcite because
> 1. It has done the hard job of parsing, translating logical plan to physical 
> plan and optimizing.
> 2. It is under active development and has a great community.
> 3. It's proved to be a good solution since Apache Storm, Apache Flink and 
> Apache Samza all build their Streaming SQL with Apache Calcite
> Note SQL here actually means Streaming SQL dialects supported by Calcite 
> (check reference 1 and 2). Please checkout reference 3 for an example 
> implementation. 
> The physical plan will be translated to Gearpump high level DSL.
> References:
> 1. http://www.slideshare.net/julianhyde/streaming-sql
> 2. https://calcite.apache.org/docs/stream.html
> 3. https://github.com/milinda/samza-sql



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEARPUMP-217) Add SQL support

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang updated GEARPUMP-217:

Fix Version/s: 0.8.5

> Add SQL support 
> 
>
> Key: GEARPUMP-217
> URL: https://issues.apache.org/jira/browse/GEARPUMP-217
> Project: Apache Gearpump
>  Issue Type: New Feature
>  Components: streaming
>Affects Versions: 0.8.1
>    Reporter: Manu Zhang
>Assignee: Buddhi Ayesha
>Priority: Major
>  Labels: gsoc2017, mentor
> Fix For: 0.8.5
>
>
> SQL support will allow those unfamiliar with Scala/Java to use Gearpump. I 
> propose to build SQL layer with Apache Calcite because
> 1. It has done the hard job of parsing, translating logical plan to physical 
> plan and optimizing.
> 2. It is under active development and has a great community.
> 3. It's proved to be a good solution since Apache Storm, Apache Flink and 
> Apache Samza all build their Streaming SQL with Apache Calcite
> Note SQL here actually means Streaming SQL dialects supported by Calcite 
> (check reference 1 and 2). Please checkout reference 3 for an example 
> implementation. 
> The physical plan will be translated to Gearpump high level DSL.
> References:
> 1. http://www.slideshare.net/julianhyde/streaming-sql
> 2. https://calcite.apache.org/docs/stream.html
> 3. https://github.com/milinda/samza-sql



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-377) Add TwitterSource and examples

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-377.
-
Resolution: Fixed

> Add TwitterSource and examples
> --
>
> Key: GEARPUMP-377
> URL: https://issues.apache.org/jira/browse/GEARPUMP-377
> Project: Apache Gearpump
>  Issue Type: New Feature
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
>Priority: Major
> Fix For: 0.8.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEARPUMP-377) Add TwitterSource and examples

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang updated GEARPUMP-377:

Fix Version/s: 0.8.5

> Add TwitterSource and examples
> --
>
> Key: GEARPUMP-377
> URL: https://issues.apache.org/jira/browse/GEARPUMP-377
> Project: Apache Gearpump
>  Issue Type: New Feature
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
>Priority: Major
> Fix For: 0.8.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-376) Apache Kudu Streaming Sink

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-376.
-
   Resolution: Fixed
Fix Version/s: 0.8.5

Issue resolved by pull request 246
[https://github.com/apache/incubator-gearpump/pull/246]

> Apache Kudu Streaming Sink
> --
>
> Key: GEARPUMP-376
> URL: https://issues.apache.org/jira/browse/GEARPUMP-376
> Project: Apache Gearpump
>  Issue Type: New Feature
>Reporter: Sandish Kumar HN
>Assignee: Sandish Kumar HN
>Priority: Major
> Fix For: 0.8.5
>
>
> Apache Kudu Streaming Sink



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEARPUMP-377) Add TwitterSource and examples

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-377:
---

 Summary: Add TwitterSource and examples
 Key: GEARPUMP-377
 URL: https://issues.apache.org/jira/browse/GEARPUMP-377
 Project: Apache Gearpump
  Issue Type: New Feature
Affects Versions: 0.8.4
Reporter: Manu Zhang
Assignee: Manu Zhang






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEARPUMP-375) Switch from Upickle to Json4s for json serialization library

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-375:
---

 Summary: Switch from Upickle to Json4s for json serialization 
library
 Key: GEARPUMP-375
 URL: https://issues.apache.org/jira/browse/GEARPUMP-375
 Project: Apache Gearpump
  Issue Type: Improvement
Reporter: Manu Zhang
Assignee: Manu Zhang


The current version of Upickle (0.3.4) has no scala 2.12 support while the 
latest version (0.6.5) needs users to define a serializer in a case class's 
companion object. It will a lot of effort to define those serializers given the 
number of case classes we have in Services module.

I propose we switch to Json4s, a facade for various scala json libraries, which 
supports scala 2.12 and can serialize case class out of box



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (GEARPUMP-374) Upgrade Scala to 2.12

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang reassigned GEARPUMP-374:
---

Assignee: Manu Zhang

> Upgrade Scala to 2.12
> -
>
> Key: GEARPUMP-374
> URL: https://issues.apache.org/jira/browse/GEARPUMP-374
> Project: Apache Gearpump
>  Issue Type: Improvement
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEARPUMP-373) Running HBaseConn examples throws NoClassDefFoundError

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang updated GEARPUMP-373:

Summary: Running HBaseConn examples throws NoClassDefFoundError  (was: 
Running HBaseConn examples throw NoClassDefFoundError error)

> Running HBaseConn examples throws NoClassDefFoundError
> --
>
> Key: GEARPUMP-373
> URL: https://issues.apache.org/jira/browse/GEARPUMP-373
> Project: Apache Gearpump
>  Issue Type: Bug
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (GEARPUMP-368) Application details page does not load

[Manu Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEARPUMP-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441685#comment-16441685
 ] 

Manu Zhang edited comment on GEARPUMP-368 at 4/17/18 11:58 PM:
---

It's a [JDK bug |https://bugs.openjdk.java.net/browse/JDK-8074032] if you see
{code:java}
java.lang.ArithmeticException: long overflow
{code}
in the executor log. I believe it has been solved in latest JDK 8. 

 

 


was (Author: mauzhang):
It's a [JDK bug |https://bugs.openjdk.java.net/browse/JDK-8074032] if you see 
{{java.lang.ArithmeticException: long overflow }}in the executor log. I believe 
it has been solved in latest JDK 8. 

 

 

> Application details page does not load
> --
>
> Key: GEARPUMP-368
> URL: https://issues.apache.org/jira/browse/GEARPUMP-368
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.5
>Reporter: Hashan Gayasri Udugahapattuwa
>Assignee: Karol Brejna
>Priority: Major
> Attachments: gearpump-master-47505.log, gearpump-ui-47572.log, 
> gearpump-worker-47538.log, logs.zip
>
>
> Application details page does not load in the 
> 0.8.5-SNAPSHOT(8aac07b86d4b90e4f5118f3204610d3510f93b02). This is recreatable 
> with the default examples. 
> This issue not present in the 0.8.4 release.
>  
> Request : [http://172.25.34.11:8090/api/v1.0/appmaster/1?detail=true]
> Status Code : 500 Internal Server Error
>  
> Response : 
> akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://app1-executor-1@10.10.1.20:33881/user/daemon/appdaemon1/$c#1247996686]]
>  after [15000 ms]. Sender[null] sent message of type 
> "org.apache.gearpump.cluster.MasterToAppMaster$AppMasterDataDetailRequest".
>  at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
>  at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>  at 
> scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
>  at 
> akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:329)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:280)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:284)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:236)
>  at java.lang.Thread.run(Unknown Source)
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEARPUMP-368) Application details page does not load

[Manu Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEARPUMP-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441685#comment-16441685
 ] 

Manu Zhang commented on GEARPUMP-368:
-

It's a [JDK bug |https://bugs.openjdk.java.net/browse/JDK-8074032] if you see 
{{java.lang.ArithmeticException: long overflow }}in the executor log. I believe 
it has been solved in latest JDK 8. 

 

 

> Application details page does not load
> --
>
> Key: GEARPUMP-368
> URL: https://issues.apache.org/jira/browse/GEARPUMP-368
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.5
>Reporter: Hashan Gayasri Udugahapattuwa
>Assignee: Karol Brejna
>Priority: Major
> Attachments: gearpump-master-47505.log, gearpump-ui-47572.log, 
> gearpump-worker-47538.log, logs.zip
>
>
> Application details page does not load in the 
> 0.8.5-SNAPSHOT(8aac07b86d4b90e4f5118f3204610d3510f93b02). This is recreatable 
> with the default examples. 
> This issue not present in the 0.8.4 release.
>  
> Request : [http://172.25.34.11:8090/api/v1.0/appmaster/1?detail=true]
> Status Code : 500 Internal Server Error
>  
> Response : 
> akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://app1-executor-1@10.10.1.20:33881/user/daemon/appdaemon1/$c#1247996686]]
>  after [15000 ms]. Sender[null] sent message of type 
> "org.apache.gearpump.cluster.MasterToAppMaster$AppMasterDataDetailRequest".
>  at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
>  at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>  at 
> scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
>  at 
> akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:329)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:280)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:284)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:236)
>  at java.lang.Thread.run(Unknown Source)
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEARPUMP-368) Application details page does not load

[Manu Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEARPUMP-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441675#comment-16441675
 ] 

Manu Zhang commented on GEARPUMP-368:
-

[~karol_brejna], [~hashan],

 

Sorry to have missed your replies. I can reproduce both of your issues now and 
will submit PRs to fix them soon. Thanks for looking into them

> Application details page does not load
> --
>
> Key: GEARPUMP-368
> URL: https://issues.apache.org/jira/browse/GEARPUMP-368
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.5
>Reporter: Hashan Gayasri Udugahapattuwa
>Assignee: Karol Brejna
>Priority: Major
> Attachments: gearpump-master-47505.log, gearpump-ui-47572.log, 
> gearpump-worker-47538.log, logs.zip
>
>
> Application details page does not load in the 
> 0.8.5-SNAPSHOT(8aac07b86d4b90e4f5118f3204610d3510f93b02). This is recreatable 
> with the default examples. 
> This issue not present in the 0.8.4 release.
>  
> Request : [http://172.25.34.11:8090/api/v1.0/appmaster/1?detail=true]
> Status Code : 500 Internal Server Error
>  
> Response : 
> akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://app1-executor-1@10.10.1.20:33881/user/daemon/appdaemon1/$c#1247996686]]
>  after [15000 ms]. Sender[null] sent message of type 
> "org.apache.gearpump.cluster.MasterToAppMaster$AppMasterDataDetailRequest".
>  at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
>  at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>  at 
> scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
>  at 
> akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:329)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:280)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:284)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:236)
>  at java.lang.Thread.run(Unknown Source)
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-367) Unnecessary use of window processing

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-367.
-
   Resolution: Fixed
Fix Version/s: 0.8.5

Issue resolved by pull request 226
[https://github.com/apache/incubator-gearpump/pull/226]

> Unnecessary use of window processing
> 
>
> Key: GEARPUMP-367
> URL: https://issues.apache.org/jira/browse/GEARPUMP-367
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: streaming
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>Assignee: Manu Zhang
>Priority: Major
> Fix For: 0.8.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEARPUMP-368) Application details page does not load

[Manu Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEARPUMP-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426498#comment-16426498
 ] 

Manu Zhang commented on GEARPUMP-368:
-

Hashan and Karol,

 

The default example of gearpump-examples-wordcount_2.11-0.8.5-SNAPSHOT.jar is 
to process a finite dataset and thus finishes in a short time. 

You may try {{bin/gear app -jar 
output/target/pack/examples/gearpump-examples-wordcount_2.11-0.8.5-SNAPSHOT.jar 
org.apache.gearpump.streaming.examples.wordcount.WordCount}} which will run the 
infinite version of word count.

 

I think it's a good point to change the default example to the infinite version 
since Gearpump has been designed to process infinite data

 

> Application details page does not load
> --
>
> Key: GEARPUMP-368
> URL: https://issues.apache.org/jira/browse/GEARPUMP-368
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.5
>Reporter: Hashan Gayasri Udugahapattuwa
>Assignee: Karol Brejna
>Priority: Major
> Attachments: gearpump-master-47505.log, gearpump-ui-47572.log, 
> gearpump-worker-47538.log
>
>
> Application details page does not load in the 
> 0.8.5-SNAPSHOT(8aac07b86d4b90e4f5118f3204610d3510f93b02). This is recreatable 
> with the default examples. 
> This issue not present in the 0.8.4 release.
>  
> Request : [http://172.25.34.11:8090/api/v1.0/appmaster/1?detail=true]
> Status Code : 500 Internal Server Error
>  
> Response : 
> akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://app1-executor-1@10.10.1.20:33881/user/daemon/appdaemon1/$c#1247996686]]
>  after [15000 ms]. Sender[null] sent message of type 
> "org.apache.gearpump.cluster.MasterToAppMaster$AppMasterDataDetailRequest".
>  at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
>  at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>  at 
> scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
>  at 
> akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:329)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:280)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:284)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:236)
>  at java.lang.Thread.run(Unknown Source)
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEARPUMP-367) Unnecessary use of window processing

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-367:
---

 Summary: Unnecessary use of window processing
 Key: GEARPUMP-367
 URL: https://issues.apache.org/jira/browse/GEARPUMP-367
 Project: Apache Gearpump
  Issue Type: Improvement
  Components: streaming
Affects Versions: 0.8.4
Reporter: Manu Zhang
Assignee: Manu Zhang






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-344) Broken link

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-344.
-
   Resolution: Fixed
Fix Version/s: 0.8.5

Issue resolved by pull request 240
[https://github.com/apache/incubator-gearpump/pull/240]

> Broken link
> ---
>
> Key: GEARPUMP-344
> URL: https://issues.apache.org/jira/browse/GEARPUMP-344
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: Ajith Joseph
>    Assignee: Manu Zhang
>Priority: Major
> Fix For: 0.8.5
>
>
> The following link (and a few more adjacent to it) are broken
> http://gearpump.apache.org/releases/latest/dev-write-1st-app.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-366) Fail to submit job when JarStore directory is removed

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-366.
-
   Resolution: Fixed
Fix Version/s: 0.8.5

Issue resolved by pull request 239
[https://github.com/apache/incubator-gearpump/pull/239]

> Fail to submit job when JarStore directory is removed
> -
>
> Key: GEARPUMP-366
> URL: https://issues.apache.org/jira/browse/GEARPUMP-366
> Project: Apache Gearpump
>  Issue Type: Bug
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
>Priority: Major
> Fix For: 0.8.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (GEARPUMP-344) Broken link

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang reassigned GEARPUMP-344:
---

Assignee: Manu Zhang  (was: Ajith Joseph)

> Broken link
> ---
>
> Key: GEARPUMP-344
> URL: https://issues.apache.org/jira/browse/GEARPUMP-344
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: Ajith Joseph
>    Assignee: Manu Zhang
>Priority: Major
>
> The following link (and a few more adjacent to it) are broken
> http://gearpump.apache.org/releases/latest/dev-write-1st-app.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-350) the app Clock is not started

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-350.
-
   Resolution: Fixed
 Assignee: Manu Zhang
Fix Version/s: 0.8.5

> the app Clock is not started
> 
>
> Key: GEARPUMP-350
> URL: https://issues.apache.org/jira/browse/GEARPUMP-350
> Project: Apache Gearpump
>  Issue Type: Bug
>Affects Versions: 0.8.4
>Reporter: Pan Xue
>    Assignee: Manu Zhang
>Priority: Major
> Fix For: 0.8.5
>
> Attachments: gearpump0.8.4.PNG
>
>
> When I submitted an app in the web,  in the DAG display page, I found that 
> the application clock has been not started, the source processor's color will 
> turn red, I use the example is 0.8.4 version of the example / wordcount
> !gearpump0.8.4.PNG|thumbnail!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEARPUMP-366) Fail to submit job when JarStore directory is removed

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-366:
---

 Summary: Fail to submit job when JarStore directory is removed
 Key: GEARPUMP-366
 URL: https://issues.apache.org/jira/browse/GEARPUMP-366
 Project: Apache Gearpump
  Issue Type: Bug
Affects Versions: 0.8.4
Reporter: Manu Zhang
Assignee: Manu Zhang






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Podling Report Reminder - March 2018

[Manu Zhang]

Yes, it's true that activity is lower. Don't know about others. I myself
was in a job transition in previous months but as things have settled down
I'd like to rejuvenate this project. The focus is to grow the community and
pull in more contributions.

On Wed, Mar 14, 2018 at 8:23 PM John D. Ament <johndam...@apache.org> wrote:

> That's fine, but overall how is the community doing?  It seems like
> activity is lower.
>
> On 2018/03/12 13:07:14, Manu Zhang <owenzhang1...@gmail.com> wrote:
> > (The previous reply is not well-formatted)
> >
> > Sorry that we missed the reminder and the deadline. Can we submit a
> report
> > next month ?
> >
> > Thanks,
> > Manu
> >
> > On Mon, Mar 12, 2018 at 9:05 PM Manu Zhang <owenzhang1...@gmail.com>
> wrote:
> >
> > > Sorry that we missed the reminder and the deadline. Can we submit a
> report
> > > next month ?
> > >
> > > Thanks,
> > > Manu
> > >
> > > On Sun, Mar 11, 2018 at 9:41 PM John D. Ament <johndam...@apache.org>
> > > wrote:
> > >
> > >> All,
> > >>
> > >> Please see below reminder.  No report has been filed, is one expected?
> > >> It seems like activity may have died out.
> > >>
> > >> John
> > >>
> > >> On 2018/03/07 01:32:29, johndam...@apache.org wrote:
> > >> > Dear podling,
> > >> >
> > >> > This email was sent by an automated system on behalf of the Apache
> > >> > Incubator PMC. It is an initial reminder to give you plenty of time
> to
> > >> > prepare your quarterly board report.
> > >> >
> > >> > The board meeting is scheduled for Wed, 21 March 2018, 10:30 am PDT.
> > >> > The report for your podling will form a part of the Incubator PMC
> > >> > report. The Incubator PMC requires your report to be submitted 2
> weeks
> > >> > before the board meeting, to allow sufficient time for review and
> > >> > submission (Wed, March 07).
> > >> >
> > >> > Please submit your report with sufficient time to allow the
> Incubator
> > >> > PMC, and subsequently board members to review and digest. Again, the
> > >> > very latest you should submit your report is 2 weeks prior to the
> board
> > >> > meeting.
> > >> >
> > >> > Thanks,
> > >> >
> > >> > The Apache Incubator PMC
> > >> >
> > >> > Submitting your Report
> > >> >
> > >> > --
> > >> >
> > >> > Your report should contain the following:
> > >> >
> > >> > *   Your project name
> > >> > *   A brief description of your project, which assumes no knowledge
> of
> > >> > the project or necessarily of its field
> > >> > *   A list of the three most important issues to address in the move
> > >> > towards graduation.
> > >> > *   Any issues that the Incubator PMC or ASF Board might wish/need
> to be
> > >> > aware of
> > >> > *   How has the community developed since the last report
> > >> > *   How has the project developed since the last report.
> > >> > *   How does the podling rate their own maturity.
> > >> >
> > >> > This should be appended to the Incubator Wiki page at:
> > >> >
> > >> > https://wiki.apache.org/incubator/March2018
> > >> >
> > >> > Note: This is manually populated. You may need to wait a little
> before
> > >> > this page is created from a template.
> > >> >
> > >> > Mentors
> > >> > ---
> > >> >
> > >> > Mentors should review reports for their project(s) and sign them
> off on
> > >> > the Incubator wiki page. Signing off reports shows that you are
> > >> > following the project - projects that are not signed may raise
> alarms
> > >> > for the Incubator PMC.
> > >> >
> > >> > Incubator PMC
> > >> >
> > >>
> > >
> >
>

Re: Podling Report Reminder - March 2018

[Manu Zhang]

(The previous reply is not well-formatted)

Sorry that we missed the reminder and the deadline. Can we submit a report
next month ?

Thanks,
Manu

On Mon, Mar 12, 2018 at 9:05 PM Manu Zhang <owenzhang1...@gmail.com> wrote:

> Sorry that we missed the reminder and the deadline. Can we submit a report
> next month ?
>
> Thanks,
> Manu
>
> On Sun, Mar 11, 2018 at 9:41 PM John D. Ament <johndam...@apache.org>
> wrote:
>
>> All,
>>
>> Please see below reminder.  No report has been filed, is one expected?
>> It seems like activity may have died out.
>>
>> John
>>
>> On 2018/03/07 01:32:29, johndam...@apache.org wrote:
>> > Dear podling,
>> >
>> > This email was sent by an automated system on behalf of the Apache
>> > Incubator PMC. It is an initial reminder to give you plenty of time to
>> > prepare your quarterly board report.
>> >
>> > The board meeting is scheduled for Wed, 21 March 2018, 10:30 am PDT.
>> > The report for your podling will form a part of the Incubator PMC
>> > report. The Incubator PMC requires your report to be submitted 2 weeks
>> > before the board meeting, to allow sufficient time for review and
>> > submission (Wed, March 07).
>> >
>> > Please submit your report with sufficient time to allow the Incubator
>> > PMC, and subsequently board members to review and digest. Again, the
>> > very latest you should submit your report is 2 weeks prior to the board
>> > meeting.
>> >
>> > Thanks,
>> >
>> > The Apache Incubator PMC
>> >
>> > Submitting your Report
>> >
>> > --
>> >
>> > Your report should contain the following:
>> >
>> > *   Your project name
>> > *   A brief description of your project, which assumes no knowledge of
>> > the project or necessarily of its field
>> > *   A list of the three most important issues to address in the move
>> > towards graduation.
>> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>> > aware of
>> > *   How has the community developed since the last report
>> > *   How has the project developed since the last report.
>> > *   How does the podling rate their own maturity.
>> >
>> > This should be appended to the Incubator Wiki page at:
>> >
>> > https://wiki.apache.org/incubator/March2018
>> >
>> > Note: This is manually populated. You may need to wait a little before
>> > this page is created from a template.
>> >
>> > Mentors
>> > ---
>> >
>> > Mentors should review reports for their project(s) and sign them off on
>> > the Incubator wiki page. Signing off reports shows that you are
>> > following the project - projects that are not signed may raise alarms
>> > for the Incubator PMC.
>> >
>> > Incubator PMC
>> >
>>
>

Re: Podling Report Reminder - March 2018

[Manu Zhang]

Sorry that we missed the reminder and the deadline. Can we submit a report
next month ?

Thanks,
Manu

On Sun, Mar 11, 2018 at 9:41 PM John D. Ament  wrote:

> All,
>
> Please see below reminder.  No report has been filed, is one expected?  It
> seems like activity may have died out.
>
> John
>
> On 2018/03/07 01:32:29, johndam...@apache.org wrote:
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 21 March 2018, 10:30 am PDT.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, March 07).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > *   Your project name
> > *   A brief description of your project, which assumes no knowledge of
> > the project or necessarily of its field
> > *   A list of the three most important issues to address in the move
> > towards graduation.
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> > aware of
> > *   How has the community developed since the last report
> > *   How has the project developed since the last report.
> > *   How does the podling rate their own maturity.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > https://wiki.apache.org/incubator/March2018
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
> >
>

[jira] [Resolved] (GEARPUMP-365) Upgrade SBT version to 0.13.16

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-365.
-
Resolution: Fixed

> Upgrade SBT version to 0.13.16
> --
>
> Key: GEARPUMP-365
> URL: https://issues.apache.org/jira/browse/GEARPUMP-365
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>Priority: Minor
> Fix For: 0.8.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEARPUMP-365) Upgrade SBT version to 0.13.16

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang updated GEARPUMP-365:

Fix Version/s: 0.8.5

> Upgrade SBT version to 0.13.16
> --
>
> Key: GEARPUMP-365
> URL: https://issues.apache.org/jira/browse/GEARPUMP-365
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>Priority: Minor
> Fix For: 0.8.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEARPUMP-365) Upgrade SBT version to 0.13.16

[Manu Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEARPUMP-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363673#comment-16363673
 ] 

Manu Zhang commented on GEARPUMP-365:
-

Fixed in https://github.com/apache/incubator-gearpump/pull/237

> Upgrade SBT version to 0.13.16
> --
>
> Key: GEARPUMP-365
> URL: https://issues.apache.org/jira/browse/GEARPUMP-365
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEARPUMP-365) Upgrade SBT version to 0.13.16

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-365:
---

 Summary: Upgrade SBT version to 0.13.16
 Key: GEARPUMP-365
 URL: https://issues.apache.org/jira/browse/GEARPUMP-365
 Project: Apache Gearpump
  Issue Type: Improvement
  Components: build
Affects Versions: 0.8.4
Reporter: Manu Zhang






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEARPUMP-361) Build Gearpump Docker Image locally for integration test

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-361.
-
Resolution: Fixed

Issue resolved by pull request 233
[https://github.com/apache/incubator-gearpump/pull/233]

> Build Gearpump Docker Image locally for integration test
> 
>
> Key: GEARPUMP-361
> URL: https://issues.apache.org/jira/browse/GEARPUMP-361
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: integrationtest
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>Assignee: Manu Zhang
> Fix For: 0.8.5
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Podling Report Reminder - December 2017

[Manu Zhang]

+1.

JB, could you help to post and sign it on wiki ?

Thanks,
Manu

On Wed, Nov 29, 2017 at 12:44 PM Jean-Baptiste Onofré 
wrote:

> Hi,
>
> it looks good to me.
>
> Regards
> JB
>
> On 11/29/2017 03:56 AM, Vincent Wang wrote:
> > Hi all,
> >
> > This is the Gearpump podling report. Please review.
> >
> > Gearpump
> >
> >   Gearpump is a reactive real-time streaming engine based on the
> > micro-service Actor model.
> >   Gearpump has been incubating since 2016-03-08.
> >
> >   Three most important issues to address in the move towards graduation:
> >
> >   1. Have frequent release cycles.
> >   2. Continue to evolve community interest and support.
> >   3. Keep up with Apache Beam's evolving API.
> >
> >
> >   - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >   - None.
> >
> >
> >   - How has the community developed since the last report?
> >   - There was a company managed to deploy Gearpump on their secured
> Hadoop
> > cluster. They reported some bugs occurred in their environment and
> > contributed the fixes back to Gearpump community.
> >
> >   - How has the project developed since the last report?
> >   - 15 issues created and 9 issues resolved.
> >   - An official Gearpump docker image was published.
> >   - Continuous improvements for Gearpump Runner in Apache Beam were made.
> >
> >   Date of last release:
> >   2017-07-17
> >
> >
> >   When were the last committers or PMC members elected?
> >   No new committers or PMC members elected yet.
> >
> >   Signed-off-by:
> >
> >   [ ](gearpump) Jean-Baptiste Onofré
> >   [ ](gearpump) Andrew Purtell
> >   [ ](gearpump) Jarek Jarcec Cecho
> >   [ ](gearpump) Reynold Xin
> >   [ ](gearpump) Todd Lipcon
> >   [ ](gearpump) Xuefu Zhang
> >
> >
> > 于2017年11月27日周一 上午11:48写道：
> >
> >> Dear podling,
> >>
> >> This email was sent by an automated system on behalf of the Apache
> >> Incubator PMC. It is an initial reminder to give you plenty of time to
> >> prepare your quarterly board report.
> >>
> >> The board meeting is scheduled for Wed, 20 December 2017, 10:30 am PDT.
> >> The report for your podling will form a part of the Incubator PMC
> >> report. The Incubator PMC requires your report to be submitted 2 weeks
> >> before the board meeting, to allow sufficient time for review and
> >> submission (Wed, December 06).
> >>
> >> Please submit your report with sufficient time to allow the Incubator
> >> PMC, and subsequently board members to review and digest. Again, the
> >> very latest you should submit your report is 2 weeks prior to the board
> >> meeting.
> >>
> >> Thanks,
> >>
> >> The Apache Incubator PMC
> >>
> >> Submitting your Report
> >>
> >> --
> >>
> >> Your report should contain the following:
> >>
> >> *   Your project name
> >> *   A brief description of your project, which assumes no knowledge of
> >>  the project or necessarily of its field
> >> *   A list of the three most important issues to address in the move
> >>  towards graduation.
> >> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> >>  aware of
> >> *   How has the community developed since the last report
> >> *   How has the project developed since the last report.
> >> *   How does the podling rate their own maturity.
> >>
> >> This should be appended to the Incubator Wiki page at:
> >>
> >> https://wiki.apache.org/incubator/December2017
> >>
> >> Note: This is manually populated. You may need to wait a little before
> >> this page is created from a template.
> >>
> >> Mentors
> >> ---
> >>
> >> Mentors should review reports for their project(s) and sign them off on
> >> the Incubator wiki page. Signing off reports shows that you are
> >> following the project - projects that are not signed may raise alarms
> >> for the Incubator PMC.
> >>
> >> Incubator PMC
> >>
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

[jira] [Resolved] (GEARPUMP-359) The premature OutputWatermark advancing logic in Subscription is not right

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-359.
-
   Resolution: Fixed
Fix Version/s: 0.8.5

Issue resolved by pull request 234
[https://github.com/apache/incubator-gearpump/pull/234]

> The premature OutputWatermark advancing logic in Subscription is not right
> --
>
> Key: GEARPUMP-359
> URL: https://issues.apache.org/jira/browse/GEARPUMP-359
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: Huafeng Wang
>Assignee: Huafeng Wang
> Fix For: 0.8.5
>
>
> {{Subscription}} will update processingWatermark when sending a message and 
> update outputWatermark when receiving an Ack message. It will cause 
> prematurely updating the outputWatermark in such scenario: the 
> {{Subscription}} already sent 200 messages to downstream and now the 
> processingWatermark is 200th message's watermark, then it receives the first 
> 100 messages' Ack and it will advance the outputWatermark to 200th message's 
> watermark, not the 100th one, which is wrong.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEARPUMP-361) Build Gearpump Docker Image locally for integration test

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-361:
---

 Summary: Build Gearpump Docker Image locally for integration test
 Key: GEARPUMP-361
 URL: https://issues.apache.org/jira/browse/GEARPUMP-361
 Project: Apache Gearpump
  Issue Type: Improvement
  Components: integrationtest
Affects Versions: 0.8.4
Reporter: Manu Zhang
Assignee: Manu Zhang
 Fix For: 0.8.5






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEARPUMP-360) gearpump-launcher image broken

[Manu Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEARPUMP-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220288#comment-16220288
 ] 

Manu Zhang commented on GEARPUMP-360:
-

Fixed in https://github.com/apache/incubator-gearpump/pull/235

> gearpump-launcher image broken
> --
>
> Key: GEARPUMP-360
> URL: https://issues.apache.org/jira/browse/GEARPUMP-360
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: integrationtest
>Affects Versions: 0.8.4
>Reporter: Karol Brejna
>Assignee: Karol Brejna
>
> Building docker image for integration tests fails:
> {code}
> > docker build --no-cache -t gearpump/gearpump-launcher 
> > integrationtest/docker/gearpump
> Sending build context to Docker daemon  8.192kB
> Step 1/7 : FROM grubykarol/jre:8u121b13_server
>  ---> f7e482e81614
> Step 2/7 : RUN opkg-install python
>  ---> Running in 0939e0c36efc
> Downloading 
> http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/base/Packages.gz.
> Inflating 
> http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/base/Packages.gz.
> Updated list of available packages in /var/opkg-lists/base.
> Downloading 
> http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/packages/Packages.gz.
> Inflating 
> http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/packages/Packages.gz.
> Updated list of available packages in /var/opkg-lists/packages.
> Unknown package 'python'.
> Collected errors:
>  *opkg_install_cmd: Cannot install package python.
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (GEARPUMP-360) gearpump-launcher image broken

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-360.
-
Resolution: Fixed

> gearpump-launcher image broken
> --
>
> Key: GEARPUMP-360
> URL: https://issues.apache.org/jira/browse/GEARPUMP-360
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: integrationtest
>Affects Versions: 0.8.4
>Reporter: Karol Brejna
>Assignee: Karol Brejna
>
> Building docker image for integration tests fails:
> {code}
> > docker build --no-cache -t gearpump/gearpump-launcher 
> > integrationtest/docker/gearpump
> Sending build context to Docker daemon  8.192kB
> Step 1/7 : FROM grubykarol/jre:8u121b13_server
>  ---> f7e482e81614
> Step 2/7 : RUN opkg-install python
>  ---> Running in 0939e0c36efc
> Downloading 
> http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/base/Packages.gz.
> Inflating 
> http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/base/Packages.gz.
> Updated list of available packages in /var/opkg-lists/base.
> Downloading 
> http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/packages/Packages.gz.
> Inflating 
> http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/packages/Packages.gz.
> Updated list of available packages in /var/opkg-lists/packages.
> Unknown package 'python'.
> Collected errors:
>  *opkg_install_cmd: Cannot install package python.
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (GEARPUMP-355) AppMasterResolver fails to run against a kerberized Hadoop cluster

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-355.
-
   Resolution: Fixed
Fix Version/s: (was: 0.8.4)
   0.8.5

Issue resolved by pull request 231
[https://github.com/apache/incubator-gearpump/pull/231]

> AppMasterResolver fails to run against a kerberized Hadoop cluster
> --
>
> Key: GEARPUMP-355
> URL: https://issues.apache.org/jira/browse/GEARPUMP-355
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: security, yarn
>Affects Versions: 0.8.4
>Reporter: Timea Magyar
>Assignee: Timea Magyar
> Fix For: 0.8.5
>
>
> When trying to launch a Gearpump cluster in a kerberized Hadoop/Yarn 
> environment, after the Application Master address has been resolved as a 
> prerequisite, the YarnAppMaster (responsible for starting GearPump masters, 
> workers, UI servers as Yarn containers) address (actor reference) must be 
> obtained via Kerberos/Spnego. (Kerberos over http)
> The current implementation for this resides in the AppMasterResolver class 
> and is using an apache http client (version 3.x) for establishing a 
> connection to the Application Master and obtain the above YarnAppMaster actor 
> reference. Since the apache http client does not support the negotiate 
> authentication scheme in version 3.x (required for a connection over 
> kerberos/spnego) this step will always fail in a kerberized Yarn/Hadoop 
> cluster set-up.
> I tested this in a secured/kerberized CDH 5.7.5 environment.  I would like to 
> provide a patch for this  by adapting the SPNEGO-enabled Hadoop web 
> connection code from WebHDFS.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (GEARPUMP-358) Performance regression due to costly watermark calculation

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang reassigned GEARPUMP-358:
---

Assignee: Huafeng Wang

> Performance regression due to costly watermark calculation
> --
>
> Key: GEARPUMP-358
> URL: https://issues.apache.org/jira/browse/GEARPUMP-358
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: Huafeng Wang
>Assignee: Huafeng Wang
> Fix For: 0.8.5
>
>
> For example, in streaming example SOL, everytime SOLStreamProducer output a 
> message to downstream, it will send a Watermark message to itself, which will 
> trigger watermark calculation. We should avoid flooding Watermark messages.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (GEARPUMP-358) Performance regression due to costly watermark calculation

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-358.
-
   Resolution: Fixed
Fix Version/s: 0.8.5

Issue resolved by pull request 232
[https://github.com/apache/incubator-gearpump/pull/232]

> Performance regression due to costly watermark calculation
> --
>
> Key: GEARPUMP-358
> URL: https://issues.apache.org/jira/browse/GEARPUMP-358
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: Huafeng Wang
> Fix For: 0.8.5
>
>
> For example, in streaming example SOL, everytime SOLStreamProducer output a 
> message to downstream, it will send a Watermark message to itself, which will 
> trigger watermark calculation. We should avoid flooding Watermark messages.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEARPUMP-358) Performance regression due to costly watermark calculation

[Manu Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEARPUMP-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207755#comment-16207755
 ] 

Manu Zhang commented on GEARPUMP-358:
-

I don't think it's the message that has caused regression since we previously 
sent message to self as well. Nonetheless, we should avoid watermark 
calculation on each message. Maybe an update interval like that between 
TaskActor and ClockService will do ?

> Performance regression due to costly watermark calculation
> --
>
> Key: GEARPUMP-358
> URL: https://issues.apache.org/jira/browse/GEARPUMP-358
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: Huafeng Wang
>
> For example, in streaming example SOL, everytime SOLStreamProducer output a 
> message to downstream, it will send a Watermark message to itself, which will 
> trigger watermark calculation. We should avoid flooding Watermark messages.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (GEARPUMP-349) Graph#topologicalOrderIterator is slow for large graph

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-349.
-
Resolution: Fixed

Issue resolved by pull request 223
[https://github.com/apache/incubator-gearpump/pull/223]

> Graph#topologicalOrderIterator is slow for large graph
> --
>
> Key: GEARPUMP-349
> URL: https://issues.apache.org/jira/browse/GEARPUMP-349
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>Assignee: Huafeng Wang
> Fix For: 0.8.5
>
>
> The algorithm is as follows
> 1. find zero in-degree nodes from a copied graph. 
> 2. remove nodes from the copied graph and add them to the output
> 3. repeat 1
> The issue is that step 1 traverses all remaining nodes each time, which costs 
> the algorithm {{O(n^2)}} time
> {{Graph#hasCycle}} has a similar issue



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Fwd: [Incubator Wiki] Update of "September2017" by jbonofre

[Manu Zhang]

It's manuzhang, thanks!

On Wed, Sep 13, 2017 at 7:44 PM John D. Ament <johndam...@apache.org> wrote:

> What is your wiki username?
>
> On 2017-09-10 07:04, Manu Zhang <owenzhang1...@gmail.com> wrote:
> > Sorry, I missed that part and your mail. We are in the "community
> building"
> > phase but I don't have the permission to update. Could you help to update
> > or grant me the permission ?
> >
> > Thanks,
> > Manu
> >
> > On Sat, Sep 9, 2017 at 2:33 AM John D. Ament <johndam...@apache.org>
> wrote:
> >
> > > Anyone?
> > >
> > > On 2017-09-06 07:51, "John D. Ament" <johndam...@apache.org> wrote:
> > > > I have applied fixes to your report.  I'm not sure why you removed
> the
> > > > mentor comments sections and the "How would you assess the podling's
> > > > maturity?" section.  I've readded them.  Please make sure you fill
> out
> > > the
> > > > missing pieces.
> > > >
> > > > John
> > > >
> > > > -- Forwarded message -
> > > > From: Apache Wiki <wikidi...@apache.org>
> > > > Date: Wed, Sep 6, 2017 at 3:41 AM
> > > > Subject: [Incubator Wiki] Update of "September2017" by jbonofre
> > > > To: Apache Wiki <wikidi...@apache.org>
> > > >
> > > >
> > > > Dear Wiki user,
> > > >
> > > > You have subscribed to a wiki page or wiki category on "Incubator
> Wiki"
> > > for
> > > > change notification.
> > > >
> > > > The "September2017" page has been changed by jbonofre:
> > > >
> > >
> https://wiki.apache.org/incubator/September2017?action=diff=18=19
> > > >
> > > >   
> > > >   Gearpump
> > > >
> > > > - Gearpump is a reactive real-time streaming engine based on the
> > > > micro-service
> > > > +  Gearpump is a reactive real-time streaming engine based on the
> > > > + micro-service Actor model.
> > > > - Actor model.
> > > > -
> > > > - Gearpump has been incubating since 2016-03-08.
> > > > +  Gearpump has been incubating since 2016-03-08.
> > > >
> > > > - Three most important issues to address in the move towards
> graduation:
> > > > +  Three most important issues to address in the move towards
> graduation:
> > > >
> > > > -   1.
> > > > -   2.
> > > > -   3.
> > > > +  1. Have frequent release cycles.
> > > > +  2. Continue to evolve community interest and support.
> > > > +  3. Increase user adoption.
> > > >
> > > > +
> > > > - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
> be
> > > > +  - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need
> to
> > > be
> > > > - aware of?
> > > > + aware
> > > > +  of?
> > > > +  - None.
> > > >
> > > >
> > > > -
> > > > - How has the community developed since the last report?
> > > > +  - How has the community developed since the last report?
> > > > +  - Gearpump took part in Google Summer of Code 2017 project and it
> has
> > > > been
> > > > + succeffully accompolished by student, Buddhi Ayesha, who is
> interested
> > > in
> > > > + making more contributions beyond the project.
> > > >
> > > > -
> > > > -
> > > > - How has the project developed since the last report?
> > > > +  - How has the project developed since the last report?
> > > > +  - 32 issues created and 20 issues resolved.
> > > > +  - Gearpump Runner has been merged into Apache Beam trunk.
> > > > +  - An experimental SQL support has been added and state management
> is
> > > > under
> > > > + development.
> > > >
> > > > -
> > > > - How would you assess the podling's maturity?
> > > > - Please feel free to add your own commentary.
> > > > -
> > > > -   [ ] Initial setup
> > > > -   [ ] Working towards first release
> > > > -   [ ] Community building
> > > > -   [ ] Nearing graduation
> > > > -   [ ] Other:
> > > > -
> > > > - Date of last release:
> > > > +  Date of last release:
> &

[jira] [Assigned] (GEARPUMP-345) LogUtil does not contain getLogger(Class) type implementation for class level logging in Java.

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang reassigned GEARPUMP-345:
---

Assignee: Buddhi Ayesha

> LogUtil does not contain getLogger(Class) type implementation for class 
> level logging in Java.
> -
>
> Key: GEARPUMP-345
> URL: https://issues.apache.org/jira/browse/GEARPUMP-345
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: core
> Environment: Java
>Reporter: Buddhi Ayesha
>Assignee: Buddhi Ayesha
>Priority: Minor
> Fix For: 0.8.5
>
>
> _org.apache.gearpump.util.LogUtil_ in gearpump-core module does not contain 
> _getLogger(Class)_ for class level logging in Java.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (GEARPUMP-349) Graph#topologicalOrderIterator is slow for large graph

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang updated GEARPUMP-349:

Description: 
The algorithm is as follows

1. find zero in-degree nodes from a copied graph. 
2. remove nodes from the copied graph and add them to the output
3. repeat 1

The issue is that step 1 traverses all remaining nodes each time, which costs 
the algorithm {{O(n^2)}} time

{{Graph#hasCycle}} has a similar issue

  was:
The algorithm is as follows

1. find zero in-degree nodes from a copied graph. 
2. remove nodes from the copied graph and add them to the output
3. repeat 1

The issue is that step 1 traverses all remaining nodes each time, which costs 
the algorithm {{O(n^2)}} time

The same applies for {{Graph#hasCycle}}


> Graph#topologicalOrderIterator is slow for large graph
> --
>
> Key: GEARPUMP-349
> URL: https://issues.apache.org/jira/browse/GEARPUMP-349
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
> Fix For: 0.8.5
>
>
> The algorithm is as follows
> 1. find zero in-degree nodes from a copied graph. 
> 2. remove nodes from the copied graph and add them to the output
> 3. repeat 1
> The issue is that step 1 traverses all remaining nodes each time, which costs 
> the algorithm {{O(n^2)}} time
> {{Graph#hasCycle}} has a similar issue



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (GEARPUMP-349) Graph#topologicalOrderIterator is slow for large graph

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang reassigned GEARPUMP-349:
---

Assignee: Huafeng Wang

> Graph#topologicalOrderIterator is slow for large graph
> --
>
> Key: GEARPUMP-349
> URL: https://issues.apache.org/jira/browse/GEARPUMP-349
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>Assignee: Huafeng Wang
> Fix For: 0.8.5
>
>
> The algorithm is as follows
> 1. find zero in-degree nodes from a copied graph. 
> 2. remove nodes from the copied graph and add them to the output
> 3. repeat 1
> The issue is that step 1 traverses all remaining nodes each time, which costs 
> the algorithm {{O(n^2)}} time
> {{Graph#hasCycle}} has a similar issue



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (GEARPUMP-349) Graph#topologicalOrderIterator is slow for large graph

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang updated GEARPUMP-349:

Description: 
The algorithm is as follows

1. find zero in-degree nodes from a copied graph. 
2. remove nodes from the copied graph and add them to the output
3. repeat 1

The issue is that step 1 traverses all remaining nodes each time, which costs 
the algorithm {{O(n^2)}} time

The same applies for {{Graph#hasCycle}}

  was:
The algorithm is as follows

1. find zero in-degree nodes from a copied graph. 
2. remove nodes from the copied graph and add them to the output
3. repeat 1

The issue is that step 1 traverses all remaining nodes each time, which costs 
the algorithm {{O(n^2)}} time


> Graph#topologicalOrderIterator is slow for large graph
> --
>
> Key: GEARPUMP-349
> URL: https://issues.apache.org/jira/browse/GEARPUMP-349
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
> Fix For: 0.8.5
>
>
> The algorithm is as follows
> 1. find zero in-degree nodes from a copied graph. 
> 2. remove nodes from the copied graph and add them to the output
> 3. repeat 1
> The issue is that step 1 traverses all remaining nodes each time, which costs 
> the algorithm {{O(n^2)}} time
> The same applies for {{Graph#hasCycle}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEARPUMP-349) Graph#topologicalOrderIterator is slow for large graph

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-349:
---

 Summary: Graph#topologicalOrderIterator is slow for large graph
 Key: GEARPUMP-349
 URL: https://issues.apache.org/jira/browse/GEARPUMP-349
 Project: Apache Gearpump
  Issue Type: Improvement
  Components: core
Affects Versions: 0.8.4
Reporter: Manu Zhang
 Fix For: 0.8.5


The algorithm is as follows

1. find zero in-degree nodes from a copied graph. 
2. remove nodes from the copied graph and add them to the output
3. repeat 1

The issue is that step 1 traverses all remaining nodes each time, which costs 
the algorithm {{O(n^2)}} time



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Podling Report Reminder - September 2017

[Manu Zhang]

Hi all,

This is the Gearpump podling report. Please review.

Gearpump

 Gearpump is a reactive real-time streaming engine based on the
micro-service Actor model.
 Gearpump has been incubating since 2016-03-08.

 Three most important issues to address in the move towards graduation:

 1. Have frequent release cycles.
 2. Continue to evolve community interest and support.
 3. Increase user adoption.


 - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware
 of?
 - None.


 - How has the community developed since the last report?
 - Gearpump took part in Google Summer of Code 2017 project and it has been
succeffully accompolished by student, Buddhi Ayesha, who is interested in
making more contributions beyond the project.

 - How has the project developed since the last report?
 - 32 issues created and 20 issues resolved.
 - Gearpump Runner has been merged into Apache Beam trunk.
 - An experimental SQL support has been added and state management is under
development.

 Date of last release:
 2017-07-17


 When were the last committers or PMC members elected?
 No new committers or PMC members elected yet.

 Signed-off-by:

 [ ](gearpump) Jean-Baptiste Onofré
 [ ](gearpump) Andrew Purtell
 [ ](gearpump) Jarek Jarcec Cecho
 [ ](gearpump) Reynold Xin
 [ ](gearpump) Todd Lipcon
 [ ](gearpump) Xuefu Zhang

On Sun, Sep 3, 2017 at 2:13 AM  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 20 September 2017, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, September 06).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/September2017
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

[jira] [Resolved] (GEARPUMP-348) Allow application total number of retries to be configurable

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-348.
-
   Resolution: Fixed
Fix Version/s: 0.8.5

Issue resolved by pull request 222
[https://github.com/apache/incubator-gearpump/pull/222]

> Allow application total number of retries to be configurable
> 
>
> Key: GEARPUMP-348
> URL: https://issues.apache.org/jira/browse/GEARPUMP-348
> Project: Apache Gearpump
>  Issue Type: Bug
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>Assignee: Huafeng Wang
>Priority: Minor
> Fix For: 0.8.5
>
>
> Currently, total number of retries for an application is hardcoded to 5. 
> There are cases we want it to fail as soon as possible (e.g. tests)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEARPUMP-347) ClassNotFoundException when running services in Intellij

[Manu Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEARPUMP-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144716#comment-16144716
 ] 

Manu Zhang commented on GEARPUMP-347:
-

[~HuafengWang], do you have any idea ? 

> ClassNotFoundException when running services  in Intellij
> -
>
> Key: GEARPUMP-347
> URL: https://issues.apache.org/jira/browse/GEARPUMP-347
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Reporter: Xuetong Zhu
>
> This is because mostly dependencies are marked as "provided"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEARPUMP-348) Allow application total number of retries to be configurable

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-348:
---

 Summary: Allow application total number of retries to be 
configurable
 Key: GEARPUMP-348
 URL: https://issues.apache.org/jira/browse/GEARPUMP-348
 Project: Apache Gearpump
  Issue Type: Bug
Affects Versions: 0.8.4
Reporter: Manu Zhang
Assignee: Huafeng Wang
Priority: Minor


Currently, total number of retries for an application is hardcoded to 5. There 
are cases we want it to fail as soon as possible (e.g. tests)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEARPUMP-347) ClassNotFoundException when running services in Intellij

[Manu Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEARPUMP-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141418#comment-16141418
 ] 

Manu Zhang commented on GEARPUMP-347:
-

Which services do you want to run in IDE ? Why ?

> ClassNotFoundException when running services  in Intellij
> -
>
> Key: GEARPUMP-347
> URL: https://issues.apache.org/jira/browse/GEARPUMP-347
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Reporter: Xuetong Zhu
>
> This is because mostly dependencies are marked as "provided"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (GEARPUMP-346) No script to start new worker or new master to join in the cluster

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang updated GEARPUMP-346:

Summary: No script to start new worker or new master to join in the cluster 
 (was: Not script to start new worker or new master to join in the cluster)

> No script to start new worker or new master to join in the cluster
> --
>
> Key: GEARPUMP-346
> URL: https://issues.apache.org/jira/browse/GEARPUMP-346
> Project: Apache Gearpump
>  Issue Type: Wish
>Reporter: Xuetong Zhu
>Priority: Minor
>
> First,start a cluster by start-cluster.sh,then I want start a new worker join 
> in the cluster, but not found appropriate script. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (GEARPUMP-344) Broken link

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang reassigned GEARPUMP-344:
---

Assignee: Ajith Joseph

> Broken link
> ---
>
> Key: GEARPUMP-344
> URL: https://issues.apache.org/jira/browse/GEARPUMP-344
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: Ajith Joseph
>Assignee: Ajith Joseph
>
> The following link (and a few more adjacent to it) are broken
> http://gearpump.apache.org/releases/latest/dev-write-1st-app.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEARPUMP-344) Broken link

[Manu Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEARPUMP-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134031#comment-16134031
 ] 

Manu Zhang commented on GEARPUMP-344:
-

Oh, indeed. Could you help to fix it with a PR ?

> Broken link
> ---
>
> Key: GEARPUMP-344
> URL: https://issues.apache.org/jira/browse/GEARPUMP-344
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: Ajith Joseph
>
> The following link (and a few more adjacent to it) are broken
> http://gearpump.apache.org/releases/latest/dev-write-1st-app.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEARPUMP-344) Broken link

[Manu Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEARPUMP-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133864#comment-16133864
 ] 

Manu Zhang commented on GEARPUMP-344:
-

Thanks for reporting. Where did you see the link ? It's 
http://gearpump.apache.org/releases/latest/dev/dev-write-1st-app/index.html and 
you can go there from http://gearpump.apache.org/releases/latest/index.html

> Broken link
> ---
>
> Key: GEARPUMP-344
> URL: https://issues.apache.org/jira/browse/GEARPUMP-344
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: Ajith Joseph
>
> The following link (and a few more adjacent to it) are broken
> http://gearpump.apache.org/releases/latest/dev-write-1st-app.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (GEARPUMP-343) Typos in "EmbeddedRuntimeEnvironemnt"

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-343.
-
Resolution: Fixed

Issue resolved by pull request 215
[https://github.com/apache/incubator-gearpump/pull/215]

> Typos in "EmbeddedRuntimeEnvironemnt"
> -
>
> Key: GEARPUMP-343
> URL: https://issues.apache.org/jira/browse/GEARPUMP-343
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: Manu Zhang
>Assignee: Huafeng Wang
>Priority: Minor
> Fix For: 0.8.5
>
>
> "EmbeddedEnvironemnt" => "EmbeddedEnvironment"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEARPUMP-342) Don't run DataSourceTask with WindowRunner unless necessary

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-342:
---

 Summary: Don't run DataSourceTask with WindowRunner unless 
necessary
 Key: GEARPUMP-342
 URL: https://issues.apache.org/jira/browse/GEARPUMP-342
 Project: Apache Gearpump
  Issue Type: Improvement
Affects Versions: 0.8.4
Reporter: Manu Zhang
 Fix For: 0.8.5


Currently, a windowed wordcount pipeline like 
{{source.flatMap.window.groupBy.count}} will actually be executed as 
{{source.globalWindow.flatMap.groupBy.window.count}} and 
{{globalWindow.flatMap}} run by a {{WindowRunner}}. 

The {{globalWindow}} is unnecessary unless {{source}} is followed by an 
aggregation. Further, the {{globalWindow}} requires {{Watermark.MAX}} to 
trigger emits which is not obvious for users. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (GEARPUMP-342) Don't run DataSourceTask with WindowRunner unless necessary

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang reassigned GEARPUMP-342:
---

Assignee: Manu Zhang

> Don't run DataSourceTask with WindowRunner unless necessary
> ---
>
> Key: GEARPUMP-342
> URL: https://issues.apache.org/jira/browse/GEARPUMP-342
> Project: Apache Gearpump
>  Issue Type: Improvement
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
> Fix For: 0.8.5
>
>
> Currently, a windowed wordcount pipeline like 
> {{source.flatMap.window.groupBy.count}} will actually be executed as 
> {{source.globalWindow.flatMap.groupBy.window.count}} and 
> {{globalWindow.flatMap}} run by a {{WindowRunner}}. 
> The {{globalWindow}} is unnecessary unless {{source}} is followed by an 
> aggregation. Further, the {{globalWindow}} requires {{Watermark.MAX}} to 
> trigger emits which is not obvious for users. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (GEARPUMP-341) DataSinkTask doesn't update processing watermark

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-341.
-
Resolution: Fixed

Issue resolved by pull request 214
[https://github.com/apache/incubator-gearpump/pull/214]

> DataSinkTask doesn't update processing watermark
> 
>
> Key: GEARPUMP-341
> URL: https://issues.apache.org/jira/browse/GEARPUMP-341
> Project: Apache Gearpump
>  Issue Type: Bug
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
> Fix For: 0.8.5
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEARPUMP-341) DataSinkTask doesn't update processing watermark

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-341:
---

 Summary: DataSinkTask doesn't update processing watermark
 Key: GEARPUMP-341
 URL: https://issues.apache.org/jira/browse/GEARPUMP-341
 Project: Apache Gearpump
  Issue Type: Bug
Affects Versions: 0.8.4
Reporter: Manu Zhang
Assignee: Manu Zhang
 Fix For: 0.8.5






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEARPUMP-339) Improve ScalaDoc for all public classes

[Manu Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEARPUMP-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16115360#comment-16115360
 ] 

Manu Zhang commented on GEARPUMP-339:
-

[genjavadoc doesn't support translating tparam 
tag|https://github.com/typesafehub/genjavadoc/issues/65] so we have to put up 
with Intellij complaining "Unknown Tag Parameter" or disable the inspection.

> Improve ScalaDoc for all public classes
> ---
>
> Key: GEARPUMP-339
> URL: https://issues.apache.org/jira/browse/GEARPUMP-339
> Project: Apache Gearpump
>  Issue Type: Improvement
>Affects Versions: 0.8.4
>Reporter: Manu Zhang
>Assignee: Manu Zhang
>
> All public classes should have ScalaDoc and any warnings should be fixed. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEARPUMP-339) Improve ScalaDoc for all public classes

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-339:
---

 Summary: Improve ScalaDoc for all public classes
 Key: GEARPUMP-339
 URL: https://issues.apache.org/jira/browse/GEARPUMP-339
 Project: Apache Gearpump
  Issue Type: Improvement
Affects Versions: 0.8.4
Reporter: Manu Zhang
Assignee: Manu Zhang


All public classes should have ScalaDoc and any warnings should be fixed. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (GEARPUMP-338) Improve time related types and constants

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-338.
-
Resolution: Fixed

Issue resolved by pull request 208
[https://github.com/apache/incubator-gearpump/pull/208]

> Improve time related types and constants
> 
>
> Key: GEARPUMP-338
> URL: https://issues.apache.org/jira/browse/GEARPUMP-338
> Project: Apache Gearpump
>  Issue Type: Improvement
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
> Fix For: 0.8.5
>
>
> Currently, there is a type {{TimeStamp}} in package object {{gearpump}}. It's 
> unclear what the time unit is, seconds or milliseconds. There are also 
> constants {{MAX_TIME_MILLIS}} and {{MIN_TIME_MILLIS}} for maximum and minimum 
> valid timestamps in milliseconds. All of them are not easy to find out and 
> import from the package object.
> Propose to move them into a new object singleton {{Time}} and rename type 
> {{TimeStamp}} to {{MilliSeconds}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (GEARPUMP-338) refactor time related types and constants

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang reassigned GEARPUMP-338:
---

Assignee: Manu Zhang

> refactor time related types and constants
> -
>
> Key: GEARPUMP-338
> URL: https://issues.apache.org/jira/browse/GEARPUMP-338
> Project: Apache Gearpump
>  Issue Type: Improvement
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
> Fix For: 0.8.5
>
>
> Currently, there is a type {{TimeStamp}} in package object {{gearpump}}. It's 
> unclear what the time unit is, seconds or milliseconds. There are also 
> constants {{MAX_TIME_MILLIS}} and {{MIN_TIME_MILLIS}} for maximum and minimum 
> valid timestamps in milliseconds. All of them are not easy to find out and 
> import from the package object.
> Propose to move them into a new object singleton {{Time}} and rename type 
> {{TimeStamp}} to {{MilliSeconds}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (GEARPUMP-338) Improve time related types and constants

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang updated GEARPUMP-338:

Summary: Improve time related types and constants  (was: refactor time 
related types and constants)

> Improve time related types and constants
> 
>
> Key: GEARPUMP-338
> URL: https://issues.apache.org/jira/browse/GEARPUMP-338
> Project: Apache Gearpump
>  Issue Type: Improvement
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
> Fix For: 0.8.5
>
>
> Currently, there is a type {{TimeStamp}} in package object {{gearpump}}. It's 
> unclear what the time unit is, seconds or milliseconds. There are also 
> constants {{MAX_TIME_MILLIS}} and {{MIN_TIME_MILLIS}} for maximum and minimum 
> valid timestamps in milliseconds. All of them are not easy to find out and 
> import from the package object.
> Propose to move them into a new object singleton {{Time}} and rename type 
> {{TimeStamp}} to {{MilliSeconds}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (GEARPUMP-338) refactor time related types and constants

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang updated GEARPUMP-338:

Fix Version/s: 0.8.5

> refactor time related types and constants
> -
>
> Key: GEARPUMP-338
> URL: https://issues.apache.org/jira/browse/GEARPUMP-338
> Project: Apache Gearpump
>  Issue Type: Improvement
>Affects Versions: 0.8.4
>    Reporter: Manu Zhang
> Fix For: 0.8.5
>
>
> Currently, there is a type {{TimeStamp}} in package object {{gearpump}}. It's 
> unclear what the time unit is, seconds or milliseconds. There are also 
> constants {{MAX_TIME_MILLIS}} and {{MIN_TIME_MILLIS}} for maximum and minimum 
> valid timestamps in milliseconds. All of them are not easy to find out and 
> import from the package object.
> Propose to move them into a new object singleton {{Time}} and rename type 
> {{TimeStamp}} to {{MilliSeconds}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEARPUMP-338) refactor time related types and constants

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-338:
---

 Summary: refactor time related types and constants
 Key: GEARPUMP-338
 URL: https://issues.apache.org/jira/browse/GEARPUMP-338
 Project: Apache Gearpump
  Issue Type: Improvement
Reporter: Manu Zhang


Currently, there is a type {{TimeStamp}} in package object {{gearpump}}. It's 
unclear what the time unit is, seconds or milliseconds. There are also 
constants {{MAX_TIME_MILLIS}} and {{MIN_TIME_MILLIS}} for maximum and minimum 
valid timestamps in milliseconds. All of them are not easy to find out and 
import from the package object.

Propose to move them into a new object singleton {{Time}} and rename type 
{{TimeStamp}} to {{MilliSeconds}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEARPUMP-337) Error to fetch nonexistent hbase-1.0.0.jar

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-337:
---

 Summary: Error to fetch nonexistent hbase-1.0.0.jar
 Key: GEARPUMP-337
 URL: https://issues.apache.org/jira/browse/GEARPUMP-337
 Project: Apache Gearpump
  Issue Type: Bug
Reporter: Manu Zhang


The following happens from time to time although it doesn't fail compilation.

{code}
[error] Server access Error: Connection refused (Connection refused) 
url=http://repo1.maven.org/maven2/org/apache/hbase/hbase/1.0.0/hbase-1.0.0.jar
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEARPUMP-336) Fix code styles and warnings

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-336:
---

 Summary: Fix code styles and warnings
 Key: GEARPUMP-336
 URL: https://issues.apache.org/jira/browse/GEARPUMP-336
 Project: Apache Gearpump
  Issue Type: Bug
Affects Versions: 0.8.4
Reporter: Manu Zhang
Assignee: Manu Zhang


As follow up to GEARPUMP-11. We may add more {{scalacOptions}} to discover 
potential issues



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (GEARPUMP-334) Java WordCount DSL example hangs

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-334.
-
   Resolution: Fixed
Fix Version/s: 0.8.5

Issue resolved by pull request 204
[https://github.com/apache/incubator-gearpump/pull/204]

> Java WordCount DSL example hangs
> 
>
> Key: GEARPUMP-334
> URL: https://issues.apache.org/jira/browse/GEARPUMP-334
> Project: Apache Gearpump
>  Issue Type: Bug
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
> Fix For: 0.8.5
>
>
> word count is computed in a implicit global window which requires  the 
> maximum watermark to make progress



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEARPUMP-335) Reduce test log outputs

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-335:
---

 Summary: Reduce test log outputs
 Key: GEARPUMP-335
 URL: https://issues.apache.org/jira/browse/GEARPUMP-335
 Project: Apache Gearpump
  Issue Type: Improvement
Affects Versions: 0.8.4
Reporter: Manu Zhang
Assignee: Manu Zhang
 Fix For: 0.8.5






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (GEARPUMP-334) Java WordCount DSL example hangs

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang reassigned GEARPUMP-334:
---

Assignee: Manu Zhang

> Java WordCount DSL example hangs
> 
>
> Key: GEARPUMP-334
> URL: https://issues.apache.org/jira/browse/GEARPUMP-334
> Project: Apache Gearpump
>  Issue Type: Bug
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
>
> word count is computed in a implicit global window which requires  the 
> maximum watermark to make progress



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEARPUMP-334) Java WordCount DSL example hangs

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-334:
---

 Summary: Java WordCount DSL example hangs
 Key: GEARPUMP-334
 URL: https://issues.apache.org/jira/browse/GEARPUMP-334
 Project: Apache Gearpump
  Issue Type: Bug
Reporter: Manu Zhang


word count is computed in a implicit global window which requires  the maximum 
watermark to make progress



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (GEARPUMP-333) Required external dependencies are not assembled in some examples

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang reassigned GEARPUMP-333:
---

Assignee: Manu Zhang

> Required external dependencies are not assembled in some examples
> -
>
> Key: GEARPUMP-333
> URL: https://issues.apache.org/jira/browse/GEARPUMP-333
> Project: Apache Gearpump
>  Issue Type: Bug
>    Reporter: Manu Zhang
>    Assignee: Manu Zhang
> Fix For: 0.8.5
>
>
> This is a regression brought in by 
> [GEARPUMP-311|https://issues.apache.org/jira/browse/GEARPUMP-331](Allow 
> examples to be run in IDE), which only assembles the example class itself and 
> breaks all examples that require external dependencies. 
> It's possible to include those dependencies one by one but a quick solution 
> is to revert changes to the broken examples and make it clear they can only 
> be run on a gearpump cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (GEARPUMP-333) Required external dependencies are not assembled in some examples

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-333.
-
Resolution: Fixed

Issue resolved by pull request 203
[https://github.com/apache/incubator-gearpump/pull/203]

> Required external dependencies are not assembled in some examples
> -
>
> Key: GEARPUMP-333
> URL: https://issues.apache.org/jira/browse/GEARPUMP-333
> Project: Apache Gearpump
>  Issue Type: Bug
>    Reporter: Manu Zhang
> Fix For: 0.8.5
>
>
> This is a regression brought in by 
> [GEARPUMP-311|https://issues.apache.org/jira/browse/GEARPUMP-331](Allow 
> examples to be run in IDE), which only assembles the example class itself and 
> breaks all examples that require external dependencies. 
> It's possible to include those dependencies one by one but a quick solution 
> is to revert changes to the broken examples and make it clear they can only 
> be run on a gearpump cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEARPUMP-333) Required external dependencies are not assembled in some examples

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-333:
---

 Summary: Required external dependencies are not assembled in some 
examples
 Key: GEARPUMP-333
 URL: https://issues.apache.org/jira/browse/GEARPUMP-333
 Project: Apache Gearpump
  Issue Type: Bug
Reporter: Manu Zhang
 Fix For: 0.8.5


This is a regression brought in by 
[GEARPUMP-311|https://issues.apache.org/jira/browse/GEARPUMP-331](Allow 
examples to be run in IDE), which only assembles the example class itself and 
breaks all examples that require external dependencies. 

It's possible to include those dependencies one by one but a quick solution is 
to revert changes to the broken examples and make it clear they can only be run 
on a gearpump cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (GEARPUMP-331) Allow examples to be ran in IDE

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-331.
-
   Resolution: Fixed
Fix Version/s: 0.8.5

Issue resolved by pull request 202
[https://github.com/apache/incubator-gearpump/pull/202]

> Allow examples to be ran in IDE
> ---
>
> Key: GEARPUMP-331
> URL: https://issues.apache.org/jira/browse/GEARPUMP-331
> Project: Apache Gearpump
>  Issue Type: Improvement
>Reporter: Huafeng Wang
>Assignee: Huafeng Wang
> Fix For: 0.8.5
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (GEARPUMP-162) the way to run examples should be documented

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang resolved GEARPUMP-162.
-
Resolution: Fixed

> the way to run examples should be documented
> 
>
> Key: GEARPUMP-162
> URL: https://issues.apache.org/jira/browse/GEARPUMP-162
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: streaming
>Affects Versions: 0.8.1
> Environment: linux mint 18 beta
>Reporter: HYG
>Assignee: Manu Zhang
>
> in sbt, to run the wordcount example using the command 
> "gearpump-examples-wordcount/run" will cause the classnotfound exception:
> error] (run-main-0) java.lang.NoClassDefFoundError: com/typesafe/config/Config
> java.lang.NoClassDefFoundError: com/typesafe/config/Config
>   at java.lang.Class.getDeclaredMethods0(Native Method)
>   at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>   at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
>   at java.lang.Class.getMethod0(Class.java:3018)
>   at java.lang.Class.getMethod(Class.java:1784)
> Caused by: java.lang.ClassNotFoundException: com.typesafe.config.Config
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at java.lang.Class.getDeclaredMethods0(Native Method)
>   at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>   at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
>   at java.lang.Class.getMethod0(Class.java:3018)
>   at java.lang.Class.getMethod(Class.java:1784)
> it seems to lack the main method's augument akkaConf: Config in the command, 
> however, no doc was found how to construct this augument to the  "main" 
> method.
> in addition, in previous version, like 
> b5f11040b775062eb4b3143144d0316b45766054, to run this example without  
> akkaConf argument will work. 
> so, i believe this should be illustrated, and i still couldn't work it out 
> now, can anyone help?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (GEARPUMP-162) the way to run examples should be documented

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang updated GEARPUMP-162:

Fix Version/s: 0.8.5

> the way to run examples should be documented
> 
>
> Key: GEARPUMP-162
> URL: https://issues.apache.org/jira/browse/GEARPUMP-162
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: streaming
>Affects Versions: 0.8.1
> Environment: linux mint 18 beta
>Reporter: HYG
>Assignee: Manu Zhang
> Fix For: 0.8.5
>
>
> in sbt, to run the wordcount example using the command 
> "gearpump-examples-wordcount/run" will cause the classnotfound exception:
> error] (run-main-0) java.lang.NoClassDefFoundError: com/typesafe/config/Config
> java.lang.NoClassDefFoundError: com/typesafe/config/Config
>   at java.lang.Class.getDeclaredMethods0(Native Method)
>   at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>   at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
>   at java.lang.Class.getMethod0(Class.java:3018)
>   at java.lang.Class.getMethod(Class.java:1784)
> Caused by: java.lang.ClassNotFoundException: com.typesafe.config.Config
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at java.lang.Class.getDeclaredMethods0(Native Method)
>   at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>   at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
>   at java.lang.Class.getMethod0(Class.java:3018)
>   at java.lang.Class.getMethod(Class.java:1784)
> it seems to lack the main method's augument akkaConf: Config in the command, 
> however, no doc was found how to construct this augument to the  "main" 
> method.
> in addition, in previous version, like 
> b5f11040b775062eb4b3143144d0316b45766054, to run this example without  
> akkaConf argument will work. 
> so, i believe this should be illustrated, and i still couldn't work it out 
> now, can anyone help?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (GEARPUMP-162) the way to run examples should be documented

[Manu Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEARPUMP-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manu Zhang reassigned GEARPUMP-162:
---

Assignee: Manu Zhang

> the way to run examples should be documented
> 
>
> Key: GEARPUMP-162
> URL: https://issues.apache.org/jira/browse/GEARPUMP-162
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: streaming
>Affects Versions: 0.8.1
> Environment: linux mint 18 beta
>Reporter: HYG
>Assignee: Manu Zhang
> Fix For: 0.8.5
>
>
> in sbt, to run the wordcount example using the command 
> "gearpump-examples-wordcount/run" will cause the classnotfound exception:
> error] (run-main-0) java.lang.NoClassDefFoundError: com/typesafe/config/Config
> java.lang.NoClassDefFoundError: com/typesafe/config/Config
>   at java.lang.Class.getDeclaredMethods0(Native Method)
>   at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>   at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
>   at java.lang.Class.getMethod0(Class.java:3018)
>   at java.lang.Class.getMethod(Class.java:1784)
> Caused by: java.lang.ClassNotFoundException: com.typesafe.config.Config
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at java.lang.Class.getDeclaredMethods0(Native Method)
>   at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>   at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
>   at java.lang.Class.getMethod0(Class.java:3018)
>   at java.lang.Class.getMethod(Class.java:1784)
> it seems to lack the main method's augument akkaConf: Config in the command, 
> however, no doc was found how to construct this augument to the  "main" 
> method.
> in addition, in previous version, like 
> b5f11040b775062eb4b3143144d0316b45766054, to run this example without  
> akkaConf argument will work. 
> so, i believe this should be illustrated, and i still couldn't work it out 
> now, can anyone help?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)