’ve extracted open issues to excel file. Maybe we could put them on google
docs (sheet) and do „marking” of which should „survive” the migration there
(collaboratively, maybe each reporter could decide on his own request,
whatever).
I also see “import issues” in apache jira. If we are brave enoug
I think we should register ApacheGesrpump anyway. Even if we are not going
to switch to this account, let's reserve it.
Besides, I feel that 'ApacheGearpump' sounds "strong"
W dniu śr., 6.04.2016 o 09:09 Manu Zhang
napisał(a):
> We have 92 followers.
>
> Another question is that the current accou
I've checked
https://oss.sonatype.org/content/repositories/releases/com/github/intel-hadoop
.
No jars there (gearpump-core_2.11, etc.) for 0.8.0
Regards,
Karol
t; Please check again:
>
> https://oss.sonatype.org/content/repositories/releases/com/github/intel-hadoop
>
> Sean
>
> On Thu, Apr 7, 2016 at 5:32 PM, Karol Brejna
> wrote:
>
> > I've checked
> >
> >
> https://oss.sonatype.org/content/repositories/relea
Sounds good!
śr., 13.04.2016 o 09:36 użytkownik Sean Zhong napisał:
> Cool! This sounds great!
>
> On Wed, Apr 13, 2016 at 3:16 PM, Manu Zhang
> wrote:
>
> > Twitter allows for team account at https://tweetdeck.twitter.com/.
> > After joining the team, team members can take action on behalf of
itter Account
> > > > >
> > > > > https://twitter.com/ApacheGearpump is on. Kam and Tomasz, I've
> added
> > > > both
> > > > > of you as admins.
> > > > >
> > > > > On Thu, Apr 14, 2016 at
I am particularly interested in these:
GEARPUMP-5, Add additional authorization check like checking
GEARPUMP-2, Define REST API to submit job jar
fix #1981, Support OAuth2 Social login
What's more, all of them were discussed and up-voted already.
I think we could have them all included in Apache'
+1
We have a series of jira tickets regarding Gearpump sinks/sources:
https://issues.apache.org/jira/browse/GEARPUMP-116 - Compatibility
layer/adapter for Apache Storm
https://issues.apache.org/jira/browse/GEARPUMP-115 - Create MQTT source/sink
https://issues.apache.org/jira/browse/GEARPUMP-106 - Gea
What are the criteria that decide which Executor/Tasks goes to which
Workers right now?
I am considering the following scenario.
Let's assume that we have a cluster with some "specialized" nodes (for
example a worker on IoT device that is responsible for controlling some
actuators, dedicated work
there are lots of nodes
> in
> > a DAG because user have no idea what each Task's task ID is.
> >
> > Thanks,
> > Huafeng
> >
> > 2016-05-11 15:49 GMT+08:00 Karol Brejna :
> >
> > > What are the criteria that decide which Executor/Tasks go
In our project I used maven licence plugin. I see there is something
similar for sbt: https://github.com/sbt/sbt-license-report
I never used it but it probably do fine for us.
I opened a Jira ticket (https://issues.apache.org/jira/browse/GEARPUMP-157)
to validate/update
https://github.com/apache/
There is a problem running the code built from source on my machine (ubuntu):
GER\kbrejna@duhr:~/apache-gearpump/gearpump-0.8.1-RC0-incubating/output/target/pack$
bin/local
[ClusterConfig$] loading config file null...
Help: Start a local cluster
-sameprocess (required:false, default:false)
-worke
I am able to build and run RC1 without any problems (dowloaded source tarball).
I ran some examples - also OK.
Dashboard looks fine (there were some problems with RC0).
+1
On Tue, Jul 5, 2016 at 3:26 AM, Kam Kasravi wrote:
> Hi Gearpump Community
>
> This is a call for a discussion releasing Ap
I am able to build and run RC1 without any problems (dowloaded source tarball).
I ran some examples - also OK.
Dashboard looks fine (there were some problems with RC0).
+1
On Tue, Jul 5, 2016 at 3:26 AM, Kam Kasravi wrote:
> Hi Gearpump Community
>
> This is a call for a discussion releasing Apa
building from source - OK
running test case - OK
deploy on YARN - OK
Bump into some issues when trying to generate the docs (api docs). See
results at the end of the email.
I've never done it before. Am I doing it right? Do we have a problem here?
Regards,
Karol
~/apache-gearpump/gearpump-lice
+1
On Mon, Jul 11, 2016 at 6:21 AM, Darion Yaphet wrote:
> building from source code , running test case and deploy in local machine
> SUCC . +1
>
> 2016-07-11 10:11 GMT+08:00 Manu Zhang :
>
>> The files are good now.
>>
>> I can build, run unit tests and integration tests successfully.
>> +1
>>
+1
On Tue, Jul 19, 2016 at 12:56 PM, Kam Kasravi wrote:
> Hi Gearpump Community
>
> This is an abbreviated call for a discussion releasing Apache Gearpump
> 0.8.1-incubating, release candidate 4. This is the first release of
> Gearpump and the fourth release candidate. RC4 provides specific
> upd
+1 (binding)
On Wed, Aug 3, 2016 at 11:18 AM, Jiang Weihua wrote:
> +1.
>
> 在 16/8/2 下午9:30，“Kam Kasravi” 写入:
>
> Gearpump community:
>
> The voting window policy is a minimum of 72 hours rather than 36 hours. We
> will extend the voting window for another 36 hours.
> Therefore th
I've just browsed through a book "Fast Data Architectures For
Streaming Applications" by Dean Wampler and was pleased to notice they
reference to Gearpump!
We are in a good company (Flink, Kafka Streams, Akka Streams).
They mention Gearpump in context of integration with Beam and Akka Streams.
Re
+1
I think moving EmbeddedCluster capabilities to gearpump-core makes
sense and simplifies things.
On Tue, Oct 11, 2016 at 7:04 AM, Manu Zhang wrote:
> +1. Integration tests for Beam Gearpump runner heavily depends on
> EmbeddedCluster. It's quite weird to add `gearpump-daemon` dependency to
> r
+1
0.8.2 builds just fine
ran in local mode
successfully ran some examples
On Fri, Nov 18, 2016 at 5:56 AM, Manu Zhang wrote:
> +1
>
> - verified KEYS and checksums
> - successfully built from source and ran SOL example locally
> - successfully deployed the binary on a 4-node cluster and run SOL
+1 from me :)
On Fri, Dec 9, 2016 at 8:40 PM, Kam Kasravi wrote:
> +1
>
> On Friday, December 9, 2016 8:17 AM, Jean-Baptiste Onofré
> wrote:
>
>
> I can add myself for the sign-off ;)
>
> Up to you guys.
>
> Regards
> JB
>
> On 12/09/2016 05:14 PM, Kam Kasravi wrote:
>> Should we add Jean-
... I've been browsing through our jira.
I spotted these tickets that probably need update:
https://issues.apache.org/jira/browse/GEARPUMP-282
pull request merged (https://github.com/apache/incubator-gearpump/pull/160)
@huafang: should we close this?
https://issues.apache.
I am preparing next release of Apache Gearpump (incubating).
I try to commit source tarballs to SVN
(https://dist.apache.org/repos/dist/dev/incubator/gearpump')
When I do 'svn commit' I am asked for credentials that I do not know.
I've never done this before, probabably I have no account there.
password will be your Apache LDAP
> password. These credentials are managed by id.apache.org.
>
>
>
> On Thu, Mar 23, 2017 at 9:37 AM, Karol Brejna
> wrote:
>>
>> I am preparing next release of Apache Gearpump (incubating).
>>
>> I try to commit source tarb
Hi Gearpump Community,
This is a call for a discussion releasing Apache Gearpump
0.8.3-incubating, release candidate #1.
The source and binary tarballs, including signatures, digests, etc.
can be found at:
https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.3-incubating/RC1/
Release ar
anu
Jean-Baptiste Onofré 于2017年4月7日 周五下午2:51写道：
> +1 (binding)
>
> Checked license, DISCLAIMER, headers.
>
> Regards
> JB
>
> On 04/07/2017 08:44 AM, Vincent Wang wrote:
> > Signatures verified and binary artifacts works well.
Hi IPMC Community,
The PPMC vote to release Apache Gearpump (incubating) 0.8.3-RC1 has passed.
We would like to now submit this release candidate to the IPMC.
The PPMC vote thread is here:
https://lists.apache.org/thread.html/0e1022d2f3b5b2a2b879e4c278d7fc44d094058550d47ae7e07702ec@%3Cdev.gearpum
Dear IPMC Community,
Here is a kindly reminder that Apache Gearpump (incubating) 0.8.3-RC1
release vote is on.
We already have one +1 vote (thanks Gary!) and still need just a few ;-)
Regards,
Karol
On Tue, Apr 11, 2017 at 11:33 AM, Karol Brejna wrote:
> Hi IPMC Community,
>
> The
Dear IPMC Community,
I am pleased to announce that the Incubator PMC has approved 0.8.3-RC1
of Apache Gearpump (Incubating) for release as version 0.8.3 (Incubating).
The vote has passed with:
- three binding "+1" votes
- no "0" votes
- no "-1" votes
The votes were
(https://www.mail-archive.com
The Apache Gearpump team would like to announce the release of Apache
Gearpump 0.8.3-incubating.
Apache Gearpump (incubating) is a reactive real-time streaming engine based
on the micro-service Actor model. It provides extremely high performance
stream processing while maintaining millisecond late
Buddhi,
Congrats and good luck!
I'll keep my fingers crossed ;-)
Regards,
Karol
On Fri, May 5, 2017 at 7:43 AM, Buddhi Ayesha Rathnayaka
wrote:
> I am thrilled to have this great opportunity. First, I want to thank Manu
> Zhang for helping me throughout the GSoC proposal submission process. It
Ramin,
Is there a chance for you to share the code?
What is your datasource?
Regards,
Karol
W dniu pt., 5.05.2017 o 18:06 Ramin Etemaadi
napisał(a):
> Hi team,
>
> Thanks for your great job on Gearpump project.
>
> After upgrading from 0.8.1 to 0.8.3 (and adjusting changing interfaces), I
> go
I've just noticed, that our IntelliJ license for Gearpump has expired.
My license details:
Licensed to: GearPump
License restriction: For non-commercial open source development only
Valid through: April 21, 2017
Do you remember how to renew the license with JetBrains?
Regards,
Karol
che
> membership （email account).
>
> Karol Brejna 于2017年5月9日周二 下午4:43写道：
>
> > I've just noticed, that our IntelliJ license for Gearpump has expired.
> >
> > My license details:
> >
> > Licensed to: GearPump
> > License restriction: For non-comm
Manu,
Do we mention the effort on akka-streams integration?
Otherwise, looks good.
Karol
On Mon, Jun 5, 2017 at 3:13 AM, Manu Zhang wrote:
> Hi all,
>
> Here is the Gearpump Podling Report. Please review.
>
> Gearpump
>
> Gearpump is a reactive real-time streaming engine based on the
> micro
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-incu
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
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/incubato
The time is up. It looks like we have the quorum.
The voting passes with clean 3 times +1 votes (no "0", no "-1") from
* Jean-Baptiste Onofré
* Vincent Wang
* Manu Zhang
Thank You for participating.
Let me continue with the release process.
(Process the voting on IPMC Community list.)
Regards,
IPMC Community,
The PPMC vote to release Apache Gearpump (incubating) 0.8.4-RC1 has passed.
We would like to now submit this release candidate to the IPMC.
The PPMC vote thread is here:
https://lists.apache.org/thread.html/d04e30eec251c8f33f319e98d24a5cd2d3cc62455276d49719057c3f@%3Cdev.gearpump.a
Dear IPMC Community,
I am pleased to announce that the Incubator PMC has approved 0.8.4-RC1
of Apache Gearpump (Incubating) for release as version 0.8.4 (Incubating).
The vote has passed with:
- three binding "+1" votes
- no "0" votes
- no "-1" votes
The votes were
(https://www.mail-archive.com
The Apache Gearpump team would like to announce the release of Apache
Gearpump 0.8.4-incubating.
Apache Gearpump (incubating) is a reactive real-time streaming engine based
on the micro-service Actor model. It provides extremely high performance
stream processing while maintaining millisecond late
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
+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/77946cfff4557cf10c13c2d35fc165223583e58c2f7705319acabcf4@%3Cdev.gearpump.apache.org%3E
> >,
> we agree that it would be better for Gearpump to retire from
[
https://issues.apache.org/jira/browse/GEARPUMP-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225724#comment-15225724
]
Karol Brejna commented on GEARPUMP-5:
-
Tested with latest version of Tru
Github user karol-brejna-i commented on the pull request:
https://github.com/apache/incubator-gearpump/pull/1#issuecomment-210462411
Small thing:
IDE setup link (beginning of the page) doesn't work. It points to:
https://github.com/whjiang/incubator-gearpump/blob/gea
Github user karol-brejna-i commented on a diff in the pull request:
https://github.com/apache/incubator-gearpump/pull/1#discussion_r59873136
--- Diff: CONTRIBUTING.md ---
@@ -1,41 +1,125 @@
-This documents are for committers which have direct write permission to
intel-hadoop
Github user karol-brejna-i commented on a diff in the pull request:
https://github.com/apache/incubator-gearpump/pull/1#discussion_r59875167
--- Diff: CONTRIBUTING.md ---
@@ -1,41 +1,125 @@
-This documents are for committers which have direct write permission to
intel-hadoop
Github user karol-brejna-i commented on a diff in the pull request:
https://github.com/apache/incubator-gearpump/pull/1#discussion_r59873253
--- Diff: CONTRIBUTING.md ---
@@ -53,40 +137,242 @@ No work should ever be done in the forked master.
Another way to do this is to
Github user karol-brejna-i commented on a diff in the pull request:
https://github.com/apache/incubator-gearpump/pull/1#discussion_r59873927
--- Diff: CONTRIBUTING.md ---
@@ -53,40 +137,242 @@ No work should ever be done in the forked master.
Another way to do this is to
Github user karol-brejna-i commented on a diff in the pull request:
https://github.com/apache/incubator-gearpump/pull/1#discussion_r59879526
--- Diff: CONTRIBUTING.md ---
@@ -53,40 +137,242 @@ No work should ever be done in the forked master.
Another way to do this is to
Github user karol-brejna-i commented on a diff in the pull request:
https://github.com/apache/incubator-gearpump/pull/1#discussion_r59879821
--- Diff: CONTRIBUTING.md ---
@@ -53,40 +137,242 @@ No work should ever be done in the forked master.
Another way to do this is to
Github user karol-brejna-i commented on a diff in the pull request:
https://github.com/apache/incubator-gearpump/pull/1#discussion_r59880173
--- Diff: CONTRIBUTING.md ---
@@ -53,40 +137,242 @@ No work should ever be done in the forked master.
Another way to do this is to
[
https://issues.apache.org/jira/browse/GEARPUMP-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250240#comment-15250240
]
Karol Brejna commented on GEARPUMP-20:
--
[~mauzhang] could you explain more on
[
https://issues.apache.org/jira/browse/GEARPUMP-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258027#comment-15258027
]
Karol Brejna commented on GEARPUMP-106:
---
[~darion], you mean integrating
[
https://issues.apache.org/jira/browse/GEARPUMP-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261789#comment-15261789
]
Karol Brejna commented on GEARPUMP-112:
---
Piotr, what environment are you run
Karol Brejna created GEARPUMP-115:
-
Summary: Create MQTT source/sink
Key: GEARPUMP-115
URL: https://issues.apache.org/jira/browse/GEARPUMP-115
Project: Apache Gearpump
Issue Type: New
[
https://issues.apache.org/jira/browse/GEARPUMP-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karol Brejna updated GEARPUMP-115:
--
Description:
MQTT is a machine-to-machine (M2M)/Internet of Things connectivity protocol
Karol Brejna created GEARPUMP-116:
-
Summary: Compatibility layer/adapter for Apache Storm
Key: GEARPUMP-116
URL: https://issues.apache.org/jira/browse/GEARPUMP-116
Project: Apache Gearpump
Karol Brejna created GEARPUMP-120:
-
Summary: gearpump.apache.org -> fork me on github goes to "old"
github repo
Key: GEARPUMP-120
URL: https://issues.apache.org/jira/browse/GEARPUMP-120
Karol Brejna created GEARPUMP-143:
-
Summary: Document `worker.executor-share-same-jvm-as-worker`
config parameter
Key: GEARPUMP-143
URL: https://issues.apache.org/jira/browse/GEARPUMP-143
Project
Karol Brejna created GEARPUMP-144:
-
Summary: Modify Gearpump's yarnclient so it can use provided user
for HDFS and YARN
Key: GEARPUMP-144
URL: https://issues.apache.org/jira/browse/GEARPUM
Karol Brejna created GEARPUMP-146:
-
Summary: Gearpump on Raspi - "experiment" plan
Key: GEARPUMP-146
URL: https://issues.apache.org/jira/browse/GEARPUMP-146
Project: Apache Gearpump
Karol Brejna created GEARPUMP-147:
-
Summary: java.lang.ClassNotFoundException when running on worker
with worker.executor-share-same-jvm-as-worker = true
Key: GEARPUMP-147
URL: https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/GEARPUMP-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karol Brejna updated GEARPUMP-147:
--
Attachment: logs.slimworker.zip
> java.lang.ClassNotFoundException when running on wor
[
https://issues.apache.org/jira/browse/GEARPUMP-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karol Brejna updated GEARPUMP-147:
--
Description:
Doing GEARPUMP-146 I hit a problem: I was able to run a master on pc and a
[
https://issues.apache.org/jira/browse/GEARPUMP-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karol Brejna updated GEARPUMP-147:
--
Attachment: prepare.sh
gear.pc.slimworker.conf
gear.pc.conf
[
https://issues.apache.org/jira/browse/GEARPUMP-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karol Brejna updated GEARPUMP-146:
--
Description:
The plan for the experiment is to have a master and one (or more) workers on
[
https://issues.apache.org/jira/browse/GEARPUMP-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291422#comment-15291422
]
Karol Brejna commented on GEARPUMP-146:
---
I am doing "zip fitness" t
[
https://issues.apache.org/jira/browse/GEARPUMP-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293123#comment-15293123
]
Karol Brejna commented on GEARPUMP-147:
---
[~HuafengWang] Adding the DAG ja
[
https://issues.apache.org/jira/browse/GEARPUMP-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karol Brejna updated GEARPUMP-147:
--
Description:
Doing GEARPUMP-146 I hit a problem: I was able to run a master on pc and a
Karol Brejna created GEARPUMP-149:
-
Summary: Binding tasks to workers
Key: GEARPUMP-149
URL: https://issues.apache.org/jira/browse/GEARPUMP-149
Project: Apache Gearpump
Issue Type
[
https://issues.apache.org/jira/browse/GEARPUMP-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karol Brejna updated GEARPUMP-149:
--
Description:
Let's assume that we have a cluster with some "specialized" nod
[
https://issues.apache.org/jira/browse/GEARPUMP-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294986#comment-15294986
]
Karol Brejna commented on GEARPUMP-149:
---
Another rationale:
I've
Github user karol-brejna-i commented on a diff in the pull request:
https://github.com/apache/incubator-gearpump/pull/22#discussion_r64182841
--- Diff: docs/deployment-ha.md ---
@@ -38,6 +38,11 @@ In `conf/gear.conf`, For entry
`gearpump.jarstore.rootpath`, please choose the s
[
https://issues.apache.org/jira/browse/GEARPUMP-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karol Brejna updated GEARPUMP-147:
--
Assignee: Sean Zhong (was: Huafeng Wang)
> java.lang.ClassNotFoundException when running
[
https://issues.apache.org/jira/browse/GEARPUMP-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299707#comment-15299707
]
Karol Brejna commented on GEARPUMP-147:
---
[~clockfly] Could you comment on
Github user karol-brejna-i commented on the pull request:
https://github.com/apache/incubator-gearpump/pull/30
âµâ thanks for the patch!
---
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
[
https://issues.apache.org/jira/browse/GEARPUMP-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313616#comment-15313616
]
Karol Brejna commented on GEARPUMP-40:
--
[~mauzhang] Do you think https://github
Karol Brejna created GEARPUMP-154:
-
Summary: Ambiguous response when submitting a dag (with error in
main() )
Key: GEARPUMP-154
URL: https://issues.apache.org/jira/browse/GEARPUMP-154
Project: Apache
Karol Brejna created GEARPUMP-157:
-
Summary: Verify/update licences of included libraries
Key: GEARPUMP-157
URL: https://issues.apache.org/jira/browse/GEARPUMP-157
Project: Apache Gearpump
[
https://issues.apache.org/jira/browse/GEARPUMP-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karol Brejna updated GEARPUMP-157:
--
Description:
1. List all dependencies of the project (libraries) and their licences - update
[
https://issues.apache.org/jira/browse/GEARPUMP-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318005#comment-15318005
]
Karol Brejna commented on GEARPUMP-157:
---
It's not clear for me what libr
Karol Brejna created GEARPUMP-158:
-
Summary: Docker/kubernetes deployment PoC
Key: GEARPUMP-158
URL: https://issues.apache.org/jira/browse/GEARPUMP-158
Project: Apache Gearpump
Issue Type
[
https://issues.apache.org/jira/browse/GEARPUMP-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329305#comment-15329305
]
Karol Brejna commented on GEARPUMP-157:
---
I've installed ilcence plugi
Github user karol-brejna-i commented on the issue:
https://github.com/apache/incubator-gearpump/pull/11
I think I see the idea behind RedisSink and RedisStorage.
Redis is advertised as "data structure store". It supports structures (like
strings, lists, sets, h
Github user karol-brejna-i commented on the issue:
https://github.com/apache/incubator-gearpump/pull/11
We are developing under 'experiments' here. I'd be happy to have something
decent here. Maybe not full-blown, but functional.
Can we sum up what we still need
Karol Brejna created GEARPUMP-161:
-
Summary: Application logs are not created on Yarn
Key: GEARPUMP-161
URL: https://issues.apache.org/jira/browse/GEARPUMP-161
Project: Apache Gearpump
Karol Brejna created GEARPUMP-163:
-
Summary: CONTRIBUTING.md should be more "visible"
Key: GEARPUMP-163
URL: https://issues.apache.org/jira/browse/GEARPUMP-163
Project: Apache Gearpump
Karol Brejna created GEARPUMP-164:
-
Summary: Let the user that connects to HBase (HBaseSink) be
configurable
Key: GEARPUMP-164
URL: https://issues.apache.org/jira/browse/GEARPUMP-164
Project: Apache
[
https://issues.apache.org/jira/browse/GEARPUMP-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karol Brejna reassigned GEARPUMP-164:
-
Assignee: Karol Brejna
> Let the user that connects to HBase (HBaseSink)
GitHub user karol-brejna-i opened a pull request:
https://github.com/apache/incubator-gearpump/pull/44
GEARPUMP-164 configurable hbase user
Simple change that allows configuring the user for connection to HBase.
Tested on YARN deployment.
You can merge this pull request into a
Github user karol-brejna-i commented on the issue:
https://github.com/apache/incubator-gearpump/pull/11
@darionyaphet
> Support more command such as : time to live , exist and delete .
This is the reason I tend to agree @manuzhang. Let's have the "basic&
[
https://issues.apache.org/jira/browse/GEARPUMP-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15345769#comment-15345769
]
Karol Brejna commented on GEARPUMP-164:
---
I will clean up the commits and
Github user karol-brejna-i commented on the issue:
https://github.com/apache/incubator-gearpump/pull/44
I will clean up the commits and make sure scalastyle is ok with the PR. I
will reissue new PR.
---
If your project is set up for it, you can reply to this email and have your
Github user karol-brejna-i closed the pull request at:
https://github.com/apache/incubator-gearpump/pull/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
GitHub user karol-brejna-i opened a pull request:
https://github.com/apache/incubator-gearpump/pull/49
GEARPUMP-164 configurable hbase user
Simple change that allows configuring the user for connection to HBase.
Tested on YARN deployment.
(PR replacing messy https
[
https://issues.apache.org/jira/browse/GEARPUMP-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347974#comment-15347974
]
Karol Brejna commented on GEARPUMP-161:
---
I'll try to validate i
1 - 100 of 243 matches
Mail list logo
