[jira] [Created] (GEARPUMP-321) Prepare 0.8.4 release

[Manu Zhang (JIRA)]

Manu Zhang created GEARPUMP-321:
---

 Summary: Prepare 0.8.4 release
 Key: GEARPUMP-321
 URL: https://issues.apache.org/jira/browse/GEARPUMP-321
 Project: Apache Gearpump
  Issue Type: Task
Reporter: Manu Zhang






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

[jira] [Assigned] (GEARPUMP-321) Prepare 0.8.4 release

[Manu Zhang (JIRA)]

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

Manu Zhang reassigned GEARPUMP-321:
---

Assignee: Manu Zhang

> Prepare 0.8.4 release
> -
>
> Key: GEARPUMP-321
> URL: https://issues.apache.org/jira/browse/GEARPUMP-321
> Project: Apache Gearpump
>  Issue Type: Task
>Reporter: Manu Zhang
>Assignee: Manu Zhang
>




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

[jira] [Commented] (GEARPUMP-319) Support Sorted Set in Redis

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEARPUMP-319:
-

Github user darionyaphet commented on the issue:

https://github.com/apache/incubator-gearpump/pull/191
  
@manuzhang fixed the silly bug


> Support Sorted Set in Redis
> ---
>
> Key: GEARPUMP-319
> URL: https://issues.apache.org/jira/browse/GEARPUMP-319
> Project: Apache Gearpump
>  Issue Type: New Feature
>  Components: core
>Reporter: darion yaphet
>Assignee: darion yaphet
>
> *Sorted Set* is similar with *Set* in Redis with unique values . Each element 
> storage in Sorted Set is associated with a score that is use to sort the 
> element in order .



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

[jira] [Commented] (GEARPUMP-319) Support Sorted Set in Redis

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEARPUMP-319:
-

Github user manuzhang commented on the issue:

https://github.com/apache/incubator-gearpump/pull/191
  
LGTM, +1


> Support Sorted Set in Redis
> ---
>
> Key: GEARPUMP-319
> URL: https://issues.apache.org/jira/browse/GEARPUMP-319
> Project: Apache Gearpump
>  Issue Type: New Feature
>  Components: core
>Reporter: darion yaphet
>Assignee: darion yaphet
>
> *Sorted Set* is similar with *Set* in Redis with unique values . Each element 
> storage in Sorted Set is associated with a score that is use to sort the 
> element in order .



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

[GitHub] incubator-gearpump issue #191: [GEARPUMP-319] Support Sorted Set in Redis

[codecov-io]

Github user codecov-io commented on the issue:

https://github.com/apache/incubator-gearpump/pull/191
  
# 
[Codecov](https://codecov.io/gh/apache/incubator-gearpump/pull/191?src=pr&el=h1)
 Report
> Merging 
[#191](https://codecov.io/gh/apache/incubator-gearpump/pull/191?src=pr&el=desc) 
into 
[master](https://codecov.io/gh/apache/incubator-gearpump/commit/080bdca62d56d4d798f1cf6b4b12c75d8f93bcdd?src=pr&el=desc)
 will **increase** coverage by `0.72%`.
> The diff coverage is `n/a`.



```diff
@@Coverage Diff @@
##   master #191  +/-   ##
==
+ Coverage   70.83%   71.55%   +0.72% 
==
  Files 189  189  
  Lines6106 6106  
  Branches  537  537  
==
+ Hits 4325 4369  +44 
+ Misses   1781 1737  -44
```




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-gearpump issue #191: [GEARPUMP-319] Support Sorted Set in Redis

[darionyaphet]

Github user darionyaphet commented on the issue:

https://github.com/apache/incubator-gearpump/pull/191
  
@manuzhang fixed the silly bug


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-gearpump issue #191: [GEARPUMP-319] Support Sorted Set in Redis

[manuzhang]

Github user manuzhang commented on the issue:

https://github.com/apache/incubator-gearpump/pull/191
  
LGTM, +1


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

svn dev repo cleanups

[Karol Brejna]

I am preparing artifacts for 0.8.4 release.

On of the steps is to publish them to svn.
In order to publish, you need to check out svn repo (which in turn
pull all files stored there).

The files got quite sizeble:

575180  gearpump/.svn
185280  gearpump/0.8.2-incubating
245708  gearpump/0.8.3-incubating


So it's about 1GB worth of files which transfer takes quite a long time.

I am proposing enriching our release procedure with a step of cleaning
release artifacts after the release.

After release we move

Re: svn dev repo cleanups

[Karol Brejna]

(continued)

... the artifacts from
https://dist.apache.org/repos/dist/dev/incubator/gearpump'  to
https://dist.apache.org/repos/dist/release/incubator/gearpump/ repo,
so we don't loose any historical data.

The situation is worse when we have multiple release
candidates.Erasing the old artifacts would quicken the release
procedure.

Please, tell me what you think.

Karol

On Fri, Jun 23, 2017 at 6:59 PM, Karol Brejna  wrote:
> I am preparing artifacts for 0.8.4 release.
>
> On of the steps is to publish them to svn.
> In order to publish, you need to check out svn repo (which in turn
> pull all files stored there).
>
> The files got quite sizeble:
>
> 575180  gearpump/.svn
> 185280  gearpump/0.8.2-incubating
> 245708  gearpump/0.8.3-incubating
>
>
> So it's about 1GB worth of files which transfer takes quite a long time.
>
> I am proposing enriching our release procedure with a step of cleaning
> release artifacts after the release.
>
> After release we move

[jira] [Updated] (GEARPUMP-191) add ability to control rate to TaskActor

[Karol Brejna (JIRA)]

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

Karol Brejna updated GEARPUMP-191:
--
Fix Version/s: (was: 0.8.4)
   0.8.5

> add ability to control rate to TaskActor
> 
>
> Key: GEARPUMP-191
> URL: https://issues.apache.org/jira/browse/GEARPUMP-191
> Project: Apache Gearpump
>  Issue Type: Sub-task
>Affects Versions: 0.8.1
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
> Fix For: 0.8.5
>
>
> akka-streams requires an ability to control the rate of input and output of 
> messages within a task. See Throttle 
> (http://doc.akka.io/docs/akka/current/scala/stream/stream-quickstart.html#Time-Based_Processing)



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

[jira] [Updated] (GEARPUMP-190) Add logo with text to site

[Karol Brejna (JIRA)]

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

Karol Brejna updated GEARPUMP-190:
--
Fix Version/s: (was: 0.8.4)
   0.8.5

> Add logo with text to site
> --
>
> Key: GEARPUMP-190
> URL: https://issues.apache.org/jira/browse/GEARPUMP-190
> Project: Apache Gearpump
>  Issue Type: Task
>Affects Versions: 0.8.1
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
>Priority: Minor
> Fix For: 0.8.5
>
>




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

[jira] [Updated] (GEARPUMP-22) Support akka-streams Gearpump Materializer

[Karol Brejna (JIRA)]

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

Karol Brejna updated GEARPUMP-22:
-
Fix Version/s: (was: 0.8.4)
   0.8.5

> Support akka-streams Gearpump Materializer
> --
>
> Key: GEARPUMP-22
> URL: https://issues.apache.org/jira/browse/GEARPUMP-22
> Project: Apache Gearpump
>  Issue Type: New Feature
>  Components: akkastream
>Affects Versions: 0.8.0
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
> Fix For: 0.8.5
>
>
> Reenable experiments/akkastream to work with akka 2.4.3 (latest on master)
> Create PR's for akka team related to changes required for Gearpump 
> Materializer



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

[jira] [Updated] (GEARPUMP-206) access to upstream and downstream processors

[Karol Brejna (JIRA)]

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

Karol Brejna updated GEARPUMP-206:
--
Fix Version/s: (was: 0.8.4)
   0.8.5

> access to upstream and downstream processors
> 
>
> Key: GEARPUMP-206
> URL: https://issues.apache.org/jira/browse/GEARPUMP-206
> Project: Apache Gearpump
>  Issue Type: Sub-task
>Affects Versions: 0.8.1
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
> Fix For: 0.8.5
>
>
> akka-streams requires the ability to access both upstream and downstream 
> processors. For upstream akka-streams will pull - we need to emulate 
> something similar



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

[jira] [Updated] (GEARPUMP-193) Need ability to request upstream messages (pull)

[Karol Brejna (JIRA)]

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

Karol Brejna updated GEARPUMP-193:
--
Fix Version/s: (was: 0.8.4)
   0.8.5

> Need ability to request upstream messages (pull)
> 
>
> Key: GEARPUMP-193
> URL: https://issues.apache.org/jira/browse/GEARPUMP-193
> Project: Apache Gearpump
>  Issue Type: Sub-task
>Affects Versions: 0.8.1
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
> Fix For: 0.8.5
>
>
> akka-streams Interleave GraphStage will iterate through upstream processors 
> pulling a certain number of messages for each. We do not have this ability.



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

[jira] [Updated] (GEARPUMP-211) Look at merging or unifying akka-stream DSL and Gearpump DSL

[Karol Brejna (JIRA)]

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

Karol Brejna updated GEARPUMP-211:
--
Fix Version/s: (was: 0.8.4)
   0.8.5

> Look at merging or unifying akka-stream DSL and Gearpump DSL
> 
>
> Key: GEARPUMP-211
> URL: https://issues.apache.org/jira/browse/GEARPUMP-211
> Project: Apache Gearpump
>  Issue Type: Bug
>Affects Versions: 0.8.1
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
> Fix For: 0.8.5
>
>
> akka-streams expands on the functionality currently available within the 
> Gearpump DSL significantly bringing in many new concepts and operations. We 
> should either completely embrace this DSL or integrate the akka-stream 
> related tasks into Gearpump's DSL 



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

[jira] [Updated] (GEARPUMP-250) add DSL integration, functional tests

[Karol Brejna (JIRA)]

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

Karol Brejna updated GEARPUMP-250:
--
Fix Version/s: (was: 0.8.4)
   0.8.5

> add DSL integration, functional tests 
> --
>
> Key: GEARPUMP-250
> URL: https://issues.apache.org/jira/browse/GEARPUMP-250
> Project: Apache Gearpump
>  Issue Type: Bug
>Affects Versions: 0.8.2
>Reporter: Kam Kasravi
> Fix For: 0.8.5
>
>
> akka-streams has a great testkit - perhaps we should borrow from that



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

[VOTE] Release of Apache Gearpump 0.8.3-incubating, release candidate #1

[Karol Brejna]

Hi Gearpump Community,

This is a call for a discussion releasing Apache Gearpump
0.8.4-incubating, release candidate #1, which leitmotiv is Apache Beam
integration.

The source and binary tarballs, including signatures, digests, etc.
can be found at:
https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.4-incubating/RC1/

Release artifacts are signed with the key with fingerprint:
3F12 81A2 DB58 0842 5ABA  6962 D8A8 4FBC 0A83 B291

The KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS

The tag to be voted upon is:
https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=shortlog;h=refs/tags/0.8.4-RC1

The release hash is:
https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=commit;h=71132b256b8edbd734839386d8de2731813bd290

For information about the contents of this release see:
https://issues.apache.org/jira/projects/GEARPUMP/versions/12340225

This vote will be open for 72 hours (Monday, April 27, 2017 at 4:00PM PST).

Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, run the
binary artifacts in the binary release and test.
Please vote:

[ ] +1 Release this package as gearpump-0.8.4
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

Thanks,
Karol

Re: svn dev repo cleanups

[Manu Zhang]

That's good idea. I've checked other project and it seems they don't keep
release candidates.

@JB(+j...@nanthrax.net ), any guideline or convention for
this ?

On Sat, Jun 24, 2017 at 1:05 AM Karol Brejna  wrote:

> (continued)
>
> ... the artifacts from
> https://dist.apache.org/repos/dist/dev/incubator/gearpump'  to
> https://dist.apache.org/repos/dist/release/incubator/gearpump/ repo,
> so we don't loose any historical data.
>
> The situation is worse when we have multiple release
> candidates.Erasing the old artifacts would quicken the release
> procedure.
>
> Please, tell me what you think.
>
> Karol
>
> On Fri, Jun 23, 2017 at 6:59 PM, Karol Brejna 
> wrote:
> > I am preparing artifacts for 0.8.4 release.
> >
> > On of the steps is to publish them to svn.
> > In order to publish, you need to check out svn repo (which in turn
> > pull all files stored there).
> >
> > The files got quite sizeble:
> >
> > 575180  gearpump/.svn
> > 185280  gearpump/0.8.2-incubating
> > 245708  gearpump/0.8.3-incubating
> >
> >
> > So it's about 1GB worth of files which transfer takes quite a long time.
> >
> > I am proposing enriching our release procedure with a step of cleaning
> > release artifacts after the release.
> >
> > After release we move
>

Re: [VOTE] Release of Apache Gearpump 0.8.3-incubating, release candidate #1

[Manu Zhang]

+1

[*] Checked binary tar signature and checksums
[*] Launched a local cluster and ran a wordcount dsl example
[*] Checked source tar signature and checksum
[*] Builded successfully from source
[*] Launched a local cluster and ran a wordcount dsl example

Thanks,
Manu

On Sat, Jun 24, 2017 at 2:20 AM Karol Brejna  wrote:

> Hi Gearpump Community,
>
> This is a call for a discussion releasing Apache Gearpump
> 0.8.4-incubating, release candidate #1, which leitmotiv is Apache Beam
> integration.
>
> The source and binary tarballs, including signatures, digests, etc.
> can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.4-incubating/RC1/
>
> Release artifacts are signed with the key with fingerprint:
> 3F12 81A2 DB58 0842 5ABA  6962 D8A8 4FBC 0A83 B291
>
> The KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS
>
> The tag to be voted upon is:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=shortlog;h=refs/tags/0.8.4-RC1
>
> The release hash is:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=commit;h=71132b256b8edbd734839386d8de2731813bd290
>
> For information about the contents of this release see:
> https://issues.apache.org/jira/projects/GEARPUMP/versions/12340225
>
> This vote will be open for 72 hours (Monday, April 27, 2017 at 4:00PM PST).
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, run the
> binary artifacts in the binary release and test.
> Please vote:
>
> [ ] +1 Release this package as gearpump-0.8.4
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>
> Thanks,
> Karol
>

Re: [VOTE] Release of Apache Gearpump 0.8.3-incubating, release candidate #1

[Jean-Baptiste Onofré]

+1 (binding)

I checked the signatures & checksums, build locally, checked the ASF header.

Regards
JB

On 06/23/2017 08:20 PM, Karol Brejna wrote:

Hi Gearpump Community,

This is a call for a discussion releasing Apache Gearpump
0.8.4-incubating, release candidate #1, which leitmotiv is Apache Beam
integration.

The source and binary tarballs, including signatures, digests, etc.
can be found at:
https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.4-incubating/RC1/

Release artifacts are signed with the key with fingerprint:
3F12 81A2 DB58 0842 5ABA  6962 D8A8 4FBC 0A83 B291

The KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS

The tag to be voted upon is:
https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=shortlog;h=refs/tags/0.8.4-RC1

The release hash is:
https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=commit;h=71132b256b8edbd734839386d8de2731813bd290

For information about the contents of this release see:
https://issues.apache.org/jira/projects/GEARPUMP/versions/12340225

This vote will be open for 72 hours (Monday, April 27, 2017 at 4:00PM PST).

Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, run the
binary artifacts in the binary release and test.
Please vote:

[ ] +1 Release this package as gearpump-0.8.4
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

Thanks,
Karol



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: svn dev repo cleanups

[Jean-Baptiste Onofré]

Hi guys,

dist.apache.org should contain only the latest release.

It's automatically backup on archive.apache.org, it's where you can find 
previous releases.


For instance:

https://dist.apache.org/repos/dist/release/karaf/4.1.1/

is the latest Karaf release and:

http://archive.apache.org/dist/karaf/

contains previous releases that happened on dist.apache.org.

Regards
JB

On 06/24/2017 04:33 AM, Manu Zhang wrote:
That's good idea. I've checked other project and it seems they don't keep 
release candidates.


@JB(+j...@nanthrax.net ), any guideline or convention for 
this ?


On Sat, Jun 24, 2017 at 1:05 AM Karol Brejna > wrote:


(continued)

... the artifacts from
https://dist.apache.org/repos/dist/dev/incubator/gearpump'  to
https://dist.apache.org/repos/dist/release/incubator/gearpump/ repo,
so we don't loose any historical data.

The situation is worse when we have multiple release
candidates.Erasing the old artifacts would quicken the release
procedure.

Please, tell me what you think.

Karol

On Fri, Jun 23, 2017 at 6:59 PM, Karol Brejna mailto:karolbre...@apache.org>> wrote:
 > I am preparing artifacts for 0.8.4 release.
 >
 > On of the steps is to publish them to svn.
 > In order to publish, you need to check out svn repo (which in turn
 > pull all files stored there).
 >
 > The files got quite sizeble:
 >
 > 575180  gearpump/.svn
 > 185280  gearpump/0.8.2-incubating
 > 245708  gearpump/0.8.3-incubating
 >
 >
 > So it's about 1GB worth of files which transfer takes quite a long time.
 >
 > I am proposing enriching our release procedure with a step of cleaning
 > release artifacts after the release.
 >
 > After release we move



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com