[jira] [Updated] (GEODE-2324) If AcceptorImpl is interrupted during shutdown, it does not clean up properly.

[ https://issues.apache.org/jira/browse/GEODE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Galen O'Sullivan updated GEODE-2324: Description: In {{AcceptorImpl.close()}}, the call to {{this.pool.awaitTermination(PoolImpl

Review Request 55738: GEODE-2329: Refactor JSONFormatter.fromJSON method to reduce duplication

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55738/ --- Review request for geode, Bruce Schuchardt, Galen O'Sullivan, and Hitesh Khamesr

[jira] [Commented] (GEODE-2329) JSONFormatter.fromJSON method has duplicate behavior

[ https://issues.apache.org/jira/browse/GEODE-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830860#comment-15830860 ] ASF subversion and git services commented on GEODE-2329: Commit 30

Review Request 55736: GEODE-2328: Refactor add Field methods to reduce the duplicates

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55736/ --- Review request for geode, Bruce Schuchardt, Galen O'Sullivan, and Hitesh Khamesr

[jira] [Commented] (GEODE-2328) Refactor add*Field methods to reduce the duplicates

[ https://issues.apache.org/jira/browse/GEODE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830847#comment-15830847 ] ASF subversion and git services commented on GEODE-2328: Commit b7

[jira] [Created] (GEODE-2329) JSONFormatter.fromJSON method has duplicate behavior

Udo Kohlmeyer created GEODE-2329: Summary: JSONFormatter.fromJSON method has duplicate behavior Key: GEODE-2329 URL: https://issues.apache.org/jira/browse/GEODE-2329 Project: Geode Issue Type

[jira] [Created] (GEODE-2328) Refactor add*Field methods to reduce the duplicates

Udo Kohlmeyer created GEODE-2328: Summary: Refactor add*Field methods to reduce the duplicates Key: GEODE-2328 URL: https://issues.apache.org/jira/browse/GEODE-2328 Project: Geode Issue Type:

[jira] [Resolved] (GEODE-2260) Move geode examples to new repo home

[ https://issues.apache.org/jira/browse/GEODE-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2260. Resolution: Fixed > Move geode examples to new repo home > -

[jira] [Updated] (GEODE-2260) Move geode examples to new repo home

[ https://issues.apache.org/jira/browse/GEODE-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-2260: --- Fix Version/s: 1.1.0 > Move geode examples to new repo home >

Re: JIRA versions and multiple repos

Why are we trying to use separate repos for examples and native client? Is the main driver for this simply to use a different build tool than Gradle (at least for native client)? I would think a submodule could be ignored by Gradle and that submodule could have its own unrelated build too (cmake o

Re: Is Dunit separable?

Dan and I have discussed moving dunit from geode-core/src/test to its own submodule geode-dunit. This way the framework would be usable by Geode users for their own apps. Right now dunit refers to DistributedSystem and Locator which are in geode-core/src/main. We'd have to alter dunit to use a mor

Re: JIRA versions and multiple repos

Btw, I've just confirmed that NiFi considers those subprojects (AKA separate communities). In fact ASF board asked them for that very clarification recently Thanks, Roman. On Thu, Jan 19, 2017 at 2:27 PM, Roman Shaposhnik wrote: > On Thu, Jan 19, 2017 at 2:23 PM, Anthony Baker wrote: >> >>> On

Re: Is Dunit separable?

Looking at the current code a little more I see that the base class JUnit4DistributedTestCase is tied to Geode. You would need to create an equivalent to it that doesn't refer to Geode and then base your test case on that. There is a little documentation here: https://cwiki.apache.org/conflu

[jira] [Comment Edited] (GEODE-2321) Pulse application works incorrectly in some locales

[ https://issues.apache.org/jira/browse/GEODE-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830756#comment-15830756 ] Jared Stewart edited comment on GEODE-2321 at 1/19/17 10:53 PM:

[jira] [Commented] (GEODE-2321) Pulse application works incorrectly in some locales

[ https://issues.apache.org/jira/browse/GEODE-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830756#comment-15830756 ] Jared Stewart commented on GEODE-2321: -- Here is the stack trace: ``` serviceExcepti

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #444 has FAILED (11 tests failed, no failures were new)

--- Spring Data GemFire > Nightly-ApacheGeode > #444 failed. --- Scheduled 11/1614 tests failed, no failures were new. https://build.spring.io/browse/SGF-NAG-444

Re: Is Dunit separable?

On Thu, Jan 19, 2017 at 2:30 PM, Bruce Schuchardt wrote: > Hi Roman, > > DUnit is an RMI-based system. The only ties it has to Geode are that it > creates a Locator before running tests. Is there a separate doc for it? Suppose I wanted to use DUnit to test, lets say, Zookeeper -- where would I s

Re: Is Dunit separable?

Hi Roman, DUnit is an RMI-based system. The only ties it has to Geode are that it creates a Locator before running tests. Le 1/19/2017 à 2:07 PM, Roman Shaposhnik a écrit : This is very interesting and it reminds me to ask this: how separable do you think DUnit could be from Geode? I'm thin

Re: JIRA versions and multiple repos

On Thu, Jan 19, 2017 at 2:23 PM, Anthony Baker wrote: > >> On Jan 19, 2017, at 1:01 PM, Roman Shaposhnik wrote: >> >> On Thu, Jan 19, 2017 at 12:54 PM, Anthony Baker > > wrote: >>> On Jan 19, 2017, at 11:53 AM, Roman Shaposhnik wrote: On Thu, Jan 19

Re: JIRA versions and multiple repos

> On Jan 19, 2017, at 1:01 PM, Roman Shaposhnik wrote: > > On Thu, Jan 19, 2017 at 12:54 PM, Anthony Baker > wrote: >> >>> On Jan 19, 2017, at 11:53 AM, Roman Shaposhnik wrote: >>> >>> On Thu, Jan 19, 2017 at 11:21 AM, Dan Smith wrote: I wonder if we're trying

Re: backward-compatibility testing

It would be nice to know if a test is going to use an old version. Then we could boot the appropriate locator for it. I don't have anything like that implemented yet - there is still only one locator prestarted by the DUnit launcher. Le 1/19/2017 à 1:30 PM, Dan Smith a écrit : Does this mean

Re: New committers added to Geode Site Community page

Congrats indeed! Great to have you onboard! Roman. On Thu, Jan 19, 2017 at 10:39 AM, Jared Stewart wrote: > Congrats guys!! >> On Jan 19, 2017, at 10:24 AM, Dave Barnes wrote: >> >> Ken Howe and Kevin Duling have been added to the website's Committers list. >> Welcome, Ken and Kevin! >

Re: backward-compatibility testing

This is very interesting and it reminds me to ask this: how separable do you think DUnit could be from Geode? I'm thinking that it could be very useful in other Java-based distributed projects around ASF. Thanks, Roman. On Wed, Jan 18, 2017 at 3:11 PM, Bruce Schuchardt wrote: > I've extended th

[jira] [Commented] (GEODE-2327) Query engine doesn't handle bigInteger

[ https://issues.apache.org/jira/browse/GEODE-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830687#comment-15830687 ] Hitesh Khamesra commented on GEODE-2327: With bind parameter it works... > Query

[jira] [Commented] (GEODE-2327) Query engine doesn't handle bigInteger

[ https://issues.apache.org/jira/browse/GEODE-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830689#comment-15830689 ] Jason Huynh commented on GEODE-2327: As a temporary work around, passing in the BigInt

[jira] [Commented] (GEODE-2327) Query engine doesn't handle bigInteger

[ https://issues.apache.org/jira/browse/GEODE-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830668#comment-15830668 ] Hitesh Khamesra commented on GEODE-2327: Now even parse long org.apache.geode.cac

[jira] [Commented] (GEODE-2327) Query engine doesn't handle bigInteger

[ https://issues.apache.org/jira/browse/GEODE-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830664#comment-15830664 ] Hitesh Khamesra commented on GEODE-2327: Here is test @Test public void testJS

[jira] [Commented] (GEODE-1409) Pulse view does not display cluster and members when in France

[ https://issues.apache.org/jira/browse/GEODE-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830657#comment-15830657 ] Eitan Suez commented on GEODE-1409: --- hello, i reported this issue back in May. can we g

[jira] [Created] (GEODE-2327) Query engine doesn't handle bigInteger

Hitesh Khamesra created GEODE-2327: -- Summary: Query engine doesn't handle bigInteger Key: GEODE-2327 URL: https://issues.apache.org/jira/browse/GEODE-2327 Project: Geode Issue Type: Bug

Re: backward-compatibility testing

> > The restriction on letting old-version members join is for rolling upgrade > and has been in Geode & GemFire for a long time. It gives us some > assurance that we can enable new distributed algorithms and stop using old > algorithms. We ran into that requirement when we altered distributed > l

Re: JIRA versions and multiple repos

+1 to all the (excellent) points Udo made... Also to address this concern... > were not mentioning the versioning hell one does go through to get all projects on the same version This is exactly the reason for having a Maven BOM file. And, is exactly the reason the Spring IO Platform (http://pl

Re: JIRA versions and multiple repos

I don't know if I necessarily agree with this "lock-step" simplicity, every repo/project has the same version. That would become WAY too hard to vote on all the time... I can see scenarios where geode-server might add functionality and which clients don't need. Yes, we could version all the cl

Re: JIRA versions and multiple repos

I agree with @Dan on the geode-examples bit, but not for a modular Geode. So... It depends on whether you are releasing and publishing separate artifacts to Maven Central (or Bintray and the like) as features are developed/bugs are fixed (i.e. CI/CD), then it is necessary to distinguish by version

Re: JIRA versions and multiple repos

On Thu, Jan 19, 2017 at 12:54 PM, Anthony Baker wrote: > >> On Jan 19, 2017, at 11:53 AM, Roman Shaposhnik wrote: >> >> On Thu, Jan 19, 2017 at 11:21 AM, Dan Smith wrote: >>> I wonder if we're trying to overcomplicate things there. I don't see why >>> the geode-examples wouldn't use the same rel

Re: JIRA versions and multiple repos

> On Jan 19, 2017, at 11:53 AM, Roman Shaposhnik wrote: > > On Thu, Jan 19, 2017 at 11:21 AM, Dan Smith wrote: >> I wonder if we're trying to overcomplicate things there. I don't see why >> the geode-examples wouldn't use the same release schedule and version >> number as geode. >> >> The C++

Re: backward-compatibility testing

Right, we don't allow it. That's what this email thread is about, Anil. Le 1/19/2017 à 12:16 PM, Anilkumar Gingade a écrit : any test starting a peer cache using an old version of Geode must create its own old-version Locator Bruce, we don't allow/recommend starting old versions of locator or

Re: JIRA versions and multiple repos

+1 for keeping it Simple On Thu, Jan 19, 2017 at 11:59 AM, Swapnil Bawaskar wrote: > +1 > > On Thu, Jan 19, 2017 at 11:58 AM, Jacob Barrett > wrote: > > > I think I agree. We should try the same release cycle for all components > > until we find we can't. > > > > -Jake > > > > On Thu, Jan 19, 2

Re: JIRA versions and multiple repos

Do any of the users of what we call the C++ and .NET clients view them as libraries that provide an API? (As opposed to standalone applications.) If so, it would seem that they would expect the API libraries to move in step with the server releases. If the majority of the functionality in the C+

Re: backward-compatibility testing

>> any test starting a peer cache using an old version of Geode must create its own old-version Locator Bruce, we don't allow/recommend starting old versions of locator or peers when the rolling upgrade is started, right? -Anil. On Thu, Jan 19, 2017 at 11:06 AM, Bruce Schuchardt wrote: > One wa

Fixed: apache/geode#1816 (develop - de070b5)

Build Update for apache/geode - Build: #1816 Status: Fixed Duration: 8 minutes and 6 seconds Commit: de070b5 (develop) Author: Hitesh Khamesra Message: GEODE-2282 Added license info View the changeset: https://github.com/apache/geode/compare/8b303e43bce0...de

Re: JIRA versions and multiple repos

+1 On Thu, Jan 19, 2017 at 11:58 AM, Jacob Barrett wrote: > I think I agree. We should try the same release cycle for all components > until we find we can't. > > -Jake > > On Thu, Jan 19, 2017 at 11:21 AM Dan Smith wrote: > > > I wonder if we're trying to overcomplicate things there. I don't s

Re: JIRA versions and multiple repos

I think I agree. We should try the same release cycle for all components until we find we can't. -Jake On Thu, Jan 19, 2017 at 11:21 AM Dan Smith wrote: > I wonder if we're trying to overcomplicate things there. I don't see why > the geode-examples wouldn't use the same release schedule and ver

Re: JIRA versions and multiple repos

On Thu, Jan 19, 2017 at 11:21 AM, Dan Smith wrote: > I wonder if we're trying to overcomplicate things there. I don't see why > the geode-examples wouldn't use the same release schedule and version > number as geode. > > The C++ and .NET clients are also somewhat tied to the version of geode > tha

[jira] [Commented] (GEODE-2282) Provide ability to sort field while creating pdxType for jSON document

[ https://issues.apache.org/jira/browse/GEODE-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830480#comment-15830480 ] Hitesh Khamesra commented on GEODE-2282: Need to add this sys property in doc /**

[jira] [Updated] (GEODE-2282) Provide ability to sort field while creating pdxType for jSON document

[ https://issues.apache.org/jira/browse/GEODE-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Khamesra updated GEODE-2282: --- Fix Version/s: 1.1.0 > Provide ability to sort field while creating pdxType for jSON document

[jira] [Updated] (GEODE-2282) Provide ability to sort field while creating pdxType for jSON document

[ https://issues.apache.org/jira/browse/GEODE-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Khamesra updated GEODE-2282: --- Assignee: Joey McAllister (was: Hitesh Khamesra) > Provide ability to sort field while creati

[jira] [Updated] (GEODE-2282) Provide ability to sort field while creating pdxType for jSON document

[ https://issues.apache.org/jira/browse/GEODE-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Khamesra updated GEODE-2282: --- Component/s: (was: serialization) docs > Provide ability to sort field wh

Re: Build failing the rat check

Just fixed it . Thanks. From: Dan Smith To: dev@geode.apache.org; Hitesh Khamesra Sent: Thursday, January 19, 2017 11:31 AM Subject: Build failing the rat check Unapproved licenses: geode-core/src/main/java/org/apache/geode/pdx/internal/json/JSONToPdxMapper.java -Dan

[jira] [Commented] (GEODE-2282) Provide ability to sort field while creating pdxType for jSON document

[ https://issues.apache.org/jira/browse/GEODE-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830468#comment-15830468 ] ASF subversion and git services commented on GEODE-2282: Commit de

Build failing the rat check

Unapproved licenses: geode-core/src/main/java/org/apache/geode/pdx/internal/json/JSONToPdxMapper.java -Dan

Re: JIRA versions and multiple repos

I wonder if we're trying to overcomplicate things there. I don't see why the geode-examples wouldn't use the same release schedule and version number as geode. The C++ and .NET clients are also somewhat tied to the version of geode that they support. As long as we can stick to a regular release ca

Broken: apache/geode#1815 (develop - 8b303e4)

Build Update for apache/geode - Build: #1815 Status: Broken Duration: 8 minutes and 45 seconds Commit: 8b303e4 (develop) Author: Hitesh Khamesra Message: GEODE-2282 Added ability to sort JSON fields while creating pdxtype. One can enable this feature by settin

Failed: apache/geode-examples#1 (develop - 6f5d21c)

Build Update for apache/geode-examples - Build: #1 Status: Failed Duration: 1 minute and 41 seconds Commit: 6f5d21c (develop) Author: Anthony Baker Message: GEODE-2318 Add travis-ci badge to README.md View the changeset: https://github.com/apache/geode-exampl

Fixed: apache/geode-examples#2 (develop - 22c2470)

Build Update for apache/geode-examples - Build: #2 Status: Fixed Duration: 2 minutes and 4 seconds Commit: 22c2470 (develop) Author: Anthony Baker Message: GEODE-2318 Add ASF header View the changeset: https://github.com/apache/geode-examples/compare/6f5d21c5

Re: Review Request 55687: GEODE-2199: be able to deploy jars without running servers

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55687/#review162332 --- Ship it! Ship It! - Jared Stewart On Jan. 19, 2017, 1:35 a.m

[jira] [Commented] (GEODE-2282) Provide ability to sort field while creating pdxType for jSON document

[ https://issues.apache.org/jira/browse/GEODE-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830423#comment-15830423 ] ASF subversion and git services commented on GEODE-2282: Commit 8b

Re: backward-compatibility testing

One way to do this would be to have the DUnit Locator run the oldest version of Geode that we want to test with. For now that would be 1.0.0-incubating. Any test that needs to exercise newer algorithms involving a Locator would need to launch one of its own. Does that sound acceptable? Le 1

Re: Review Request 55532: GEODE-2198: close and re-create the cache on a server when importing new cluster configuration

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55532/#review162331 --- Ship it! Ship It! - Jared Stewart On Jan. 17, 2017, 11:27 p.

[jira] [Assigned] (GEODE-2196) Write more tests to cover the current behavior of cluster config

[ https://issues.apache.org/jira/browse/GEODE-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-2196: -- Assignee: Jinmei Liao > Write more tests to cover the current behavior of cluster config >

[jira] [Resolved] (GEODE-2199) deploy/undeploy should continue even if there is no running servers in the cluster

[ https://issues.apache.org/jira/browse/GEODE-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-2199. Resolution: Fixed Assignee: Jinmei Liao (was: Kirk Lund) Fix Version/s: 1.1.0 > dep

[jira] [Commented] (GEODE-2313) PulseDataExportTest.dataBrowserExportWorksAsExpected fails with ConditionTimeoutException

[ https://issues.apache.org/jira/browse/GEODE-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830396#comment-15830396 ] ASF GitHub Bot commented on GEODE-2313: --- Github user jaredjstewart commented on the

[jira] [Resolved] (GEODE-2198) import cluster-config should continue if the running servers have no data in their application regions

[ https://issues.apache.org/jira/browse/GEODE-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-2198. Resolution: Fixed Fix Version/s: 1.1.0 > import cluster-config should continue if the running

[jira] [Commented] (GEODE-2313) PulseDataExportTest.dataBrowserExportWorksAsExpected fails with ConditionTimeoutException

[ https://issues.apache.org/jira/browse/GEODE-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830395#comment-15830395 ] ASF GitHub Bot commented on GEODE-2313: --- GitHub user jaredjstewart opened a pull req

[jira] [Assigned] (GEODE-2195) Hot Deploy of cluster configuration without bouncing the servers

[ https://issues.apache.org/jira/browse/GEODE-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-2195: -- Assignee: Jinmei Liao (was: Kirk Lund) > Hot Deploy of cluster configuration without bouncing

[GitHub] geode pull request #347: GEODE-2313: Fix PulseDataExportTest

GitHub user jaredjstewart opened a pull request: https://github.com/apache/geode/pull/347 GEODE-2313: Fix PulseDataExportTest You can merge this pull request into a Git repository by running: $ git pull https://github.com/jaredjstewart/geode GEODE-2313 Alternatively you can r

[GitHub] geode issue #347: GEODE-2313: Fix PulseDataExportTest

Github user jaredjstewart commented on the issue: https://github.com/apache/geode/pull/347 Precheckin passed --- 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 s

[jira] [Assigned] (GEODE-2198) import cluster-config should continue if the running servers have no data in their application regions

[ https://issues.apache.org/jira/browse/GEODE-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-2198: -- Assignee: Jinmei Liao (was: Kirk Lund) > import cluster-config should continue if the running

[jira] [Reopened] (GEODE-2195) Hot Deploy of cluster configuration without bouncing the servers

[ https://issues.apache.org/jira/browse/GEODE-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reopened GEODE-2195: closed by accident. > Hot Deploy of cluster configuration without bouncing the servers > --

[jira] [Resolved] (GEODE-2195) Hot Deploy of cluster configuration without bouncing the servers

[ https://issues.apache.org/jira/browse/GEODE-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-2195. Resolution: Fixed Fix Version/s: 1.1.0 > Hot Deploy of cluster configuration without bouncing

[jira] [Commented] (GEODE-2199) deploy/undeploy should continue even if there is no running servers in the cluster

[ https://issues.apache.org/jira/browse/GEODE-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830392#comment-15830392 ] ASF subversion and git services commented on GEODE-2199: Commit e0

Re: New committers added to Geode Site Community page

Congrats guys!! > On Jan 19, 2017, at 10:24 AM, Dave Barnes wrote: > > Ken Howe and Kevin Duling have been added to the website's Committers list. > Welcome, Ken and Kevin!

[jira] [Commented] (GEODE-2198) import cluster-config should continue if the running servers have no data in their application regions

[ https://issues.apache.org/jira/browse/GEODE-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830378#comment-15830378 ] ASF subversion and git services commented on GEODE-2198: Commit 6f

New committers added to Geode Site Community page

Ken Howe and Kevin Duling have been added to the website's Committers list. Welcome, Ken and Kevin!

Re: Review Request 55603: GEODE-2261: fix the dunit test in nightly build

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55603/#review162320 --- Ship it! Ship It! - Kevin Duling On Jan. 16, 2017, 9:03 p.m.

[jira] [Commented] (GEODE-2326) Fix broken integration test testLogger

[ https://issues.apache.org/jira/browse/GEODE-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830310#comment-15830310 ] ASF GitHub Bot commented on GEODE-2326: --- GitHub user dgkimura opened a pull request:

[GitHub] geode pull request #346: GEODE-2326: Adjust testLogger hardcoded value

GitHub user dgkimura opened a pull request: https://github.com/apache/geode/pull/346 GEODE-2326: Adjust testLogger hardcoded value Fixes the failing logger integration test. This was caused when we changed the log header to the Apache License. You can merge this pull request into

Re: Review Request 55532: GEODE-2198: close and re-create the cache on a server when importing new cluster configuration

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55532/#review162318 --- Ship it! Ship It! - Kevin Duling On Jan. 17, 2017, 3:27 p.m.

Re: Review Request 55687: GEODE-2199: be able to deploy jars without running servers

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55687/#review162317 --- Ship it! Ship It! - Kevin Duling On Jan. 18, 2017, 5:35 p.m.

Re: backward-compatibility testing

Thanks Dan. I'm not sure we want to keep the change I made to the Locator. The restriction on letting old-version members join is for rolling upgrade and has been in Geode & GemFire for a long time. It gives us some assurance that we can enable new distributed algorithms and stop using old a

Re: JIRA versions and multiple repos

What you're talking about makes sense -- but it is mechanics. What I'm talking about is a community composition. E.g. if we truly believe that communities of developers around, lets say core Java Geode and Native Client are non-overlapping (or there's very little overlap) we need to recognize this

Re: JIRA versions and multiple repos

Not sure if ASF has, or uses the same concept, but this could easily be handled with a GitHub "organization" encompassing 1 or more repos (for example... https://github.com/reactor). Of course, you could organize the source, and in particular, the Geode "modules" anyway you like, for example, as 1

Re: JIRA versions and multiple repos

On Thu, Jan 19, 2017 at 7:55 AM, Anthony Baker wrote: > Currently our JIRA versions look like this: > > 1.0.0-incubating.M1 > 1.0.0-incubating.M2 > 1.0.0-incubating.M3 > 1.1.0 > > That works great for the geode repo. However, what about the geode-examples > repo? I would like to set a ‘Fix vers

Re: JIRA versions and multiple repos

+1 sounds good On 1/19/17 09:02, John Blum wrote: On a slightly separate, but related note... One way of handling differing versions between potentially independently releasable artifacts/modules is to create a Maven BOM file. geode-examples are one thing, but when Geode becomes truly modular

Re: backward-compatibility testing

+1 This is great Bruce! I really like this approach of being able to write tests and have them run with some members with a different version. I think with this framework we should be able to just extend existing tests with subclasses that override the version of some of the VMs which I think is a

Re: JIRA versions and multiple repos

On a slightly separate, but related note... One way of handling differing versions between potentially independently releasable artifacts/modules is to create a Maven BOM file. geode-examples are one thing, but when Geode becomes truly modular (in a sense that naturally bounded modules... Core, Q

Re: backward-compatibility testing

> On Jan 18, 2017, at 3:11 PM, Bruce Schuchardt wrote: > > I've extended the distributedTest framework to let us do > backward-compatibility testing. Once it is reviewed and committed people > will be needed to modify existing tests to run against multiple versions of > Geode. > > Here is t

JIRA versions and multiple repos

Currently our JIRA versions look like this: 1.0.0-incubating.M1 1.0.0-incubating.M2 1.0.0-incubating.M3 1.1.0 That works great for the geode repo. However, what about the geode-examples repo? I would like to set a ‘Fix version’ that matches the version in [1]. Since the repos can release ind

[jira] [Resolved] (GEODE-2318) Improve geode-examples build

[ https://issues.apache.org/jira/browse/GEODE-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-2318. -- Resolution: Fixed > Improve geode-examples build > > >

[GitHub] geode-examples pull request #2: Build updates for examples

Github user asfgit closed the pull request at: https://github.com/apache/geode-examples/pull/2 --- 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 i

Re: New PMC Member: Ken Howe

Welcome Ken. Thanks for joining us. -- Mike Stolz Principal Engineer - Gemfire Product Manager Mobile: 631-835-4771 On Jan 18, 2017 9:52 PM, "Mark Bretl" wrote: > The Apache Geode Project Management Committee has invited Ken Howe to join > the Geode PMC. We are pleased to announce he has accepte

[GitHub] geode issue #344: Fix the Native Client Build on Ubuntu

Github user davinash commented on the issue: https://github.com/apache/geode/pull/344 Thanks @pivotal-jbarrett , I have handled review comments, tested on Ubuntu and CentOS. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well