Re: Want to contribute but do not know where to start

William thank you for your feedback! I think I'll dive into the WAN connection between clusters. There are a lot of considerations to make like fragmentation, intermittent connectivity, maybe leverage the circuit breaker pattern. A reasonable amount of discussion and research is needed, but I'll t

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #18 was SUCCESSFUL (with 965 tests)

--- Spring Data GemFire > Nightly-ApacheGeode > #18 was successful. --- Scheduled 969 tests in total. https://build.spring.io/browse/SGF-NAG-18/ -- This mes

Re: Review Request 36866: GEODE-127: Improve reliability and increase execution speed of some tests

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36866/#review93383 --- Ship it! Ship It! - William Markito On July 28, 2015, 9:27 p.m.,

Re: Review Request 36866: GEODE-127: Improve reliability and increase execution speed of some tests

> On July 29, 2015, 12:47 a.m., William Markito wrote: > > Why some tests are using System.out.println and some uses LogWriter ? Since > > it looks like you did a nice refactoring around that I'm just asking if we > > could have some consensus around what should be used within our tests as a >

Re: Review Request 36866: GEODE-127: Improve reliability and increase execution speed of some tests

> On July 29, 2015, 12:47 a.m., William Markito wrote: > > Why some tests are using System.out.println and some uses LogWriter ? Since > > it looks like you did a nice refactoring around that I'm just asking if we > > could have some consensus around what should be used within our tests as a >

Re: Review Request 36866: GEODE-127: Improve reliability and increase execution speed of some tests

> On July 29, 2015, 12:47 a.m., William Markito wrote: > > Why some tests are using System.out.println and some uses LogWriter ? Since > > it looks like you did a nice refactoring around that I'm just asking if we > > could have some consensus around what should be used within our tests as a >

Re: Review Request 36866: GEODE-127: Improve reliability and increase execution speed of some tests

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36866/#review93375 --- Why some tests are using System.out.println and some uses LogWriter

[GitHub] incubator-geode pull request: Added UnclosableInputStream for SAX ...

Github user markito commented on the pull request: https://github.com/apache/incubator-geode/pull/12#issuecomment-125783106 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 ena

Re: [GitHub] incubator-geode pull request: Added UnclosableInputStream for SAX ...

This PR looks good to me. Someone want to give me a +1 and I'll merge it in? -Dan On Tue, Jul 28, 2015 at 10:54 AM, levivic wrote: > GitHub user levivic opened a pull request: > > https://github.com/apache/incubator-geode/pull/12 > > Added UnclosableInputStream for SAX parser > > Th

Following onto @Repeat annotation is the @ConditionalIgnore...

All- There is hardly a time when you want to completely comment out or disable test case(s) using something like *JUnit's* @Ignore annotation [0]. This is not a practice that should be encouraged since tests in a suite is money in the bank

Re: About "repeating" tests (and other things)...

Cool! The build does now support rerunning a test, but this looks like a much faster way since it will run the test repeatedly in the same JVM. -Dan On Tue, Jul 28, 2015 at 2:42 PM, John Blum wrote: > Recently, the conversation > < > http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/

Re: Review Request 36662: GEODE-124: Auto Rebalancer

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36662/#review93362 --- Ship it! It might be better to check each individual region for bal

Re: Want to contribute but do not know where to start

+1 On Tue, Jul 28, 2015 at 2:59 PM, Dan Smith wrote: > I think Williams ideas and those listed on "How to Contribute" page are a > good place to start. > > I'd also like to suggest that we start tagging bugs with "starter" that > might be good bugs for someone relatively new to the geode code ba

Re: Want to contribute but do not know where to start

I think Williams ideas and those listed on "How to Contribute" page are a good place to start. I'd also like to suggest that we start tagging bugs with "starter" that might be good bugs for someone relatively new to the geode code base. I see several other apache projects doing something similar.

About "repeating" tests (and other things)...

Recently, the conversation [0] came up about how do I "repeat" a test in the Geode test suite. Invariably, the answer always centers around build-focused features. While it is unlikely that the build (i.e. *Gradle*

Re: Want to contribute but do not know where to start

Hi William, Unfortunately I have no knowledge of apache mesos/marathon ,but I am interested to know about it and to spend time on that. Thanks, Arghya On Jul 28, 2015 10:42 PM, "William Markito" wrote: > Replying the last 3 messages: > > @Arghya: That's great. Are you already familiar with me

[GitHub] incubator-geode pull request: Added UnclosableInputStream for SAX ...

GitHub user levivic opened a pull request: https://github.com/apache/incubator-geode/pull/12 Added UnclosableInputStream for SAX parser This fix is to solve the issue 135 regarding using IBM JAVA. The API doc http://java.sun.com/javase/6/docs/api/org/xml/sax/InputSource.ht

Re: Want to contribute but do not know where to start

Replying the last 3 messages: @Arghya: That's great. Are you already familiar with mesos/marathon, etc? If not that would be a good starting point before moving fwd with implementation for Geode. @Eric: That's right. Although please see my notes on this thread... @Christian: Thanks for creat

Re: Review Request 36866: GEODE-127: Improve reliability and increase execution speed of some tests

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36866/ --- (Updated July 28, 2015, 4:14 p.m.) Review request for geode, Darrel Schneider a

Re: Review Request 36857: Remove rerunTest task from gemfire-core/build.gradle

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36857/#review93301 --- Ship it! Ship It! - Kirk Lund On July 27, 2015, 8:27 p.m., Mark

Re: Want to contribute but do not know where to start

Glad i came across this discussion because i've oppened a ticket to add Geode OQL Interpreter for Zeppelin: https://issues.apache.org/jira/browse/ZEPPELIN-189 I'm working on PostgreSQL/HAWQ/GPDB Interpreter [ZEPPELIN-70] and i have been exploring a Geode Interpreter support as well. Any ideas fo

Re: Want to contribute but do not know where to start

Hi William - on the Zeppelin thing, do you mean a OQL runner/visualizer a la Databrowser? That would be cool. -- Eric On Tue, Jul 28, 2015 at 1:08 AM, William Markito wrote: > Hello João, > > Let me try to shed some light here... > > On Mon, Jul 27, 2015 at 8:42 PM, João Peixoto > wrote: >

Re: Want to contribute but do not know where to start

Hi William, I would like to work on Thanks, Arghya On Tue, Jul 28, 2015 at 10:38 AM, William Markito wrote: > Hello João, > > Let me try to shed some light here... > > On Mon, Jul 27, 2015 at 8:42 PM, João Peixoto > wrote: > > > Dear Geode de