Re: GEODE-327: Rename gemfire-junit to gemfire-common

-1 Reserve common for things common to geode development not related to unit testing. Like utilities classes. Jacob Barrett  Manager  GemFire Advanced Customer Engineering (ACE)  Pivotal jbarr...@pivotal.io  503-533-3763 For immediate support please contact Pivotal Support at  http://sup

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

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

Re: GEODE-327: Rename gemfire-junit to gemfire-common

+1 ~/William > On Sep 11, 2015, at 8:07 PM, Sai Boorlagadda wrote: > > +1 > >> On Sep 11, 2015, at 7:52 PM, Anthony Baker wrote: >> >> +1 >> >>> On Sep 11, 2015, at 12:04 PM, Kirk Lund wrote: >>> >>> I filed ticket GEODE-327 to propose renaming gemfire-junit to >>> gemfire-common. >>> >

Re: GEODE-327: Rename gemfire-junit to gemfire-common

+1 > On Sep 11, 2015, at 7:52 PM, Anthony Baker wrote: > > +1 > >> On Sep 11, 2015, at 12:04 PM, Kirk Lund wrote: >> >> I filed ticket GEODE-327 to propose renaming gemfire-junit to >> gemfire-common. >> >> We'd like to be able to define common annotations in this gemfire-common >> and not b

Re: GEODE-327: Rename gemfire-junit to gemfire-common

+1 > On Sep 11, 2015, at 12:04 PM, Kirk Lund wrote: > > I filed ticket GEODE-327 to propose renaming gemfire-junit to > gemfire-common. > > We'd like to be able to define common annotations in this gemfire-common > and not be limited to code that is specific to junit or testing. The first > ann

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

Glad it helped! If you combine the two remaining RUNs into one and do similar optimization in the .sh file, you may reduce it even further! ;) Best, Nitin From: jun aoki Sent: Friday, September 11, 2015 6:53 PM To: Nitin Lamba Cc: Dan Smith; geode Subject: R

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35541/ --- (Updated Sept. 12, 2015, 1:54 a.m.) Review request for geode. Bugs: GEODE-60

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

This is cool Nitin, I could indeed reduce the image size. will reattach the patch. Thank you for leting me know! Previous REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE geode/build-jaokilatest c8ca6d841cbb24 hours ago

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

Hi Jun, You may also want to consider RUN command chaining within Dockerfile (like William did in docker/Dockerfile). It creates relatively smaller images: https://labs.ctl.io/optimizing-docker-images/ My $0.02, Nitin From: jun aoki on behalf of jun aok

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

> On Sept. 11, 2015, 6:43 p.m., Dan Smith wrote: > > Looks good! One very minor comment - we might want to put this is a > > directory with a different name than "build" The gradle output directories > > are called build, so for example our .gitignore file will exclude > > everything in there.

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35541/ --- (Updated Sept. 11, 2015, 10:46 p.m.) Review request for geode. Bugs: GEODE-60

Review Request 38320: Search Function ResultCollector

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/38320/ --- Review request for geode and Dan Smith. Repository: geode Description ---

Re: Releasing Geode (was Re: September 2015 Report)

Seems I'm having trouble creating Scrum Board for the project. Thought I was given the right JIRA permissions. Is there a way to check if the project is 'allowed' to use the Agile plugin? Thanks, Nitin From: Kirk Lund Sent: Friday, September 11, 2015 11

GEODE-327: Rename gemfire-junit to gemfire-common

I filed ticket GEODE-327 to propose renaming gemfire-junit to gemfire-common. We'd like to be able to define common annotations in this gemfire-common and not be limited to code that is specific to junit or testing. The first annotation would be Experimental (see GEODE-328). Please vote on making

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35541/#review98660 --- Ship it! Looks good! One very minor comment - we might want to put

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

> On June 16, 2015, 11:32 p.m., Mark Bretl wrote: > > dev-tools/build/Dockerfile, line 10 > > > > > > Should that be 'default'? thank you for catching. my mistake. - jun

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

> On June 16, 2015, 11:26 p.m., Dan Smith wrote: > > dev-tools/build/Dockerfile, line 7 > > > > > > This probably should be jdk-7u79. I think there were some issues with > > some of the middle versions of jdk-7, and I k

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35541/ --- (Updated Sept. 11, 2015, 6:38 p.m.) Review request for geode. Changes ---

Re: Releasing Geode (was Re: September 2015 Report)

I'll file the ticket to rename gemfire-junit to gemfire-common and create the annotation. -Kirk On Friday, September 11, 2015, Anthony Baker wrote: > @Experimental seems to be more common (spark, rxjava, jgroups, ). > > I would rename the gemfire-junit module to gemfire-common and put the > ann

Re: Releasing Geode (was Re: September 2015 Report)

+1 to @Experimental There are some open bugs related to HdfsStore API. HdfsStore APIs could be categorized as @Experimental for Alpha-1 release. On Fri, Sep 11, 2015 at 9:35 AM, Anthony Baker wrote: > @Experimental seems to be more common (spark, rxjava, jgroups, ). > > I would rename the gemfi

Re: Releasing Geode (was Re: September 2015 Report)

On Thu, Sep 10, 2015 at 10:14 PM, Nitin Lamba wrote: > Great suggestions Anthony! > > For starters, can I get PM rights in Geode JIRA? I'll take care of the JIRA karma for you shortly. What's your JIRA ID, btw? > I should then be able to make these changes fairly quickly. > Also, it may make sen

Re: Releasing Geode (was Re: September 2015 Report)

@Experimental seems to be more common (spark, rxjava, jgroups, ). I would rename the gemfire-junit module to gemfire-common and put the annotation there. Anthony > On Sep 11, 2015, at 9:26 AM, Dan Smith wrote: > > +1 for having Nitin as release manager > > I also really like Kirks suggestio

Re: Releasing Geode (was Re: September 2015 Report)

+1 for having Nitin as release manager I also really like Kirks suggestion of marking some new APIs as experimental. How about using an @Incubating annotation that shows up in the javadocs? -Dan On Thu, Sep 10, 2015 at 10:14 PM, Nitin Lamba wrote: > Great suggestions Anthony! > > For starters,

Re: Fixing bucketids to specific nodes in gemfire

I think even using the FixedPartitionResolver the buckets will move between the nodes in case of a node crash or restart (given sufficient redundancy level). I

Re: Fixing bucketids to specific nodes in gemfire

Rajiv, You could do something like that with Fixed Patitioning but that doesn't give you exact control over buckets only the knowledge that buckets won't move from host to host. However it is much more restrictive as it makes adding additional nodes more restrictive. Regardless, the first questio

Build failed in Jenkins: Geode-nightly #212

See Changes: [vgavrilov] GEODE-313 Improve redis adpater region exception handling [nthanvi] GEODE-322: Added following parameters while creating the HDFSStore -- [...truncated 2633 lines...] Downl