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

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

Re: Removing the old Authenticator/AccessControl interfaces

Yep. That's the normal path. -- Mike Stolz Principal Engineer, GemFire Product Lead Mobile: +1-631-835-4771 On Mon, Oct 30, 2017 at 7:19 PM, Mark Bretl wrote: > If we are talking about the following: > https://github.com/apache/geode/blob/develop/geode-core/ > src/main/java/org/apache/geode/sec

Re: [ANNOUNCE] Apache Geode 1.3.0

Congrats! On Tue, Oct 31, 2017 at 10:22 AM, Swapnil Bawaskar wrote: > The Apache Geode community is pleased to announce the availability > of Apache Geode 1.3.0. > > Apache Geode is a data management platform that provides a database-like > consistency model, reliable transaction processing and

[ANNOUNCE] Apache Geode 1.3.0

The Apache Geode community is pleased to announce the availability of Apache Geode 1.3.0. Apache Geode is a data management platform that provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance with high

Broken: apache/geode#4597 (develop - 19e5f8c)

Build Update for apache/geode - Build: #4597 Status: Broken Duration: 15 minutes and 1 second Commit: 19e5f8c (develop) Author: jinmeiliao Message: GEODE-3539: Consolidate CliUtil and DataCommandUtils, DataCommandsUtil (#992) * GEODE-3539: Consolidate CliUtil

Re: Geode Nightly issue

I pushed a fix to restore the releaseType. > On Oct 31, 2017, at 9:45 AM, Dick Cavender wrote: > > It appears that Swap's merge of release/1.3 branch to develop yesterday > introduced the problem seen in last night's nightly build. We have a fix to > commit shortly. > > -Dick

Geode Nightly issue

It appears that Swap's merge of release/1.3 branch to develop yesterday introduced the problem seen in last night's nightly build. We have a fix to commit shortly. -Dick

Re: Consistent results from gfsh commands

+1 for consistency. I'm just curious how this would be displayed a cluster has many nodes. On Tue, Oct 31, 2017 at 7:59 AM, Jens Deppe wrote: > Hi, > > I've noticed that various commands, that execute on multiple members, > return either tabulated results (one line per member - for example >

Re: Consistent results from gfsh commands

+1, we should provide the user with the full details about what happened when there was at least one failure. Following this line of thought, and considering the cluster configuration service, what should the commands do when the operation fails on at least one member?. Persist the changes no matte

Re: Consistent results from gfsh commands

+1 for consistency. There is one caveat: destroy region command, e.g. is executing the function on all members that have the region, but the function is calling a distributed method (region.destroy()) which will be propagated to other members. So if the "destroy" is successful on one member, the c

Re: Consistent results from gfsh commands

+1 for consistency! Sarge > On 31 Oct, 2017, at 07:59, Jens Deppe wrote: > > Hi, > > I've noticed that various commands, that execute on multiple members, > return either tabulated results (one line per member - for example > CreateRegionCommand) or a single pass/fail line. In the latter case

Consistent results from gfsh commands

Hi, I've noticed that various commands, that execute on multiple members, return either tabulated results (one line per member - for example CreateRegionCommand) or a single pass/fail line. In the latter case it’s possible that information would get lost. For example if a command fails on multiple