Re: Geode - release 1.3 sourcing an artifact from AWS S3

Hi Brian, Good catch! It's not something deliberately nefarious - I added java pathfinder as a dependency for writing concurrency tests, but unfortunately jpf itself doesn't have a good maven artifact to use. We could make a maven artifact with the jpf binary as part of the jpf plugin from plugin

Failed: jinmeiliao/geode#53 (getPut - a96a970)

Build Update for jinmeiliao/geode - Build: #53 Status: Failed Duration: 18 minutes and 54 seconds Commit: a96a970 (getPut) Author: Jinmei Liao Message: GEODE-3539: add tests for GetCommand and PutCommand View the changeset: https://github.com/jinmeiliao/geode

Failed: apache/geode#4505 (sgo - 7c344c0)

Build Update for apache/geode - Build: #4505 Status: Failed Duration: 17 minutes and 50 seconds Commit: 7c344c0 (sgo) Author: Dave Barnes Message: Merge branch 'feature/disk-store-doc' into develop * feature/disk-store-doc: User Guide: Data Storage correctio

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #718 was SUCCESSFUL (with 2187 tests). Change made by John Blum.

--- Spring Data GemFire > Nightly-ApacheGeode > #718 was successful. --- Scheduled with changes by John Blum. 2189 tests in total. https://build.spring.io/browse

Failed: apache/geode#4495 (whitelist_wip - c12ad36)

Build Update for apache/geode - Build: #4495 Status: Failed Duration: 15 minutes and 0 seconds Commit: c12ad36 (whitelist_wip) Author: Bruce Schuchardt Message: work-in-progress branch for whitelisting classes that can be deserialized. Still needs: Distribu

Re: Native client examples

For geode-examples I think it makes sense that they are on released with geode (which they are, see https://cwiki.apache.org/confluence/display/GEODE/Release+Steps). We are currently adding examples for features that will be available in geode 1.4, so we want those to be released in sync with geode

Re: [Discussion] Native - Dropping exceptions from Region::getAll

+1 for dropping the exceptions map. > On Oct 23, 2017, at 10:36 AM, Ernest Burghardt wrote: > > +1 drop exceptions map > > On Mon, Oct 23, 2017 at 10:53 AM, Michael William Dodge > wrote: > >> +1 for dropping the exceptions map for symmetry with the Java API >> >> Sarge >> >>> On 23 Oct, 201

Re: Native client examples

In line with geode-core and geode-examples any thoughts about having geode-native-examples (on its own repo)... -Anil. On Mon, Oct 23, 2017 at 9:18 AM, Jacob Barrett wrote: > On Fri, Oct 20, 2017 at 6:02 PM Dan Smith wrote: > > > However I do think we should be compiling (and hopefully runnin

Re: Native client examples

The thread I referenced discussed the topic of different release cycles for our repos. The ASF viewpoint is that if you have separate release cycles for different repos you have an independent subproject. And a subproject implies a different community and PMC. Anthony > On Oct 23, 2017, at

Re: [Discussion] Native Region::registerAllKeys

+1 for aligning APIs On Mon, Oct 23, 2017 at 11:35 AM, Jacob Barrett wrote: > This function has an optional out variable to capture the list of keys that > get registered in this function. There are no tests that test the behavior > of the function where the out variable is provided. The API dev

Re: [Discussion] Native - Dropping exceptions from Region::getAll

+1 drop exceptions map On Mon, Oct 23, 2017 at 10:53 AM, Michael William Dodge wrote: > +1 for dropping the exceptions map for symmetry with the Java API > > Sarge > > > On 23 Oct, 2017, at 09:32, Jacob Barrett wrote: > > > > As part of our decision to replace all function out variables with re

[Discussion] Native Region::registerAllKeys

This function has an optional out variable to capture the list of keys that get registered in this function. There are no tests that test the behavior of the function where the out variable is provided. The API deviates from the Java API which does not return the list of keys. Converting to return

Re: Native client examples

Anthony, I don't see the relevance of the thread you mention. Can you please explain how a discussion on tagging releases in JIRA relates to this discussion? On Mon, Oct 23, 2017 at 10:06 AM Anthony Baker wrote: > Before we start this thread again, please read [1]. > > Anthony > > [1] > http://m

Re: Native client examples

Before we start this thread again, please read [1]. Anthony [1] http://mail-archives.apache.org/mod_mbox/geode-dev/201701.mbox/%3cdb3f0e86-1d8f-4acc-8323-fe8c135b3...@pivotal.io%3e

Re: [Discussion] Native - Dropping exceptions from Region::getAll

+1 for dropping the exceptions map for symmetry with the Java API Sarge > On 23 Oct, 2017, at 09:32, Jacob Barrett wrote: > > As part of our decision to replace all function out variables with return > values we ran into an interesting function with Region::getAll. That > function had two out v

Re: Native client examples

I agree with Jake that the examples directory should not be part of our official releases. They should be a light-weight entry point to our community, meaning they should be easy to create, modify, and use. While counter-intuitive, in this case, a less official approach to our examples will yield

[Discussion] Native - Dropping exceptions from Region::getAll

As part of our decision to replace all function out variables with return values we ran into an interesting function with Region::getAll. That function had two out variables, one the map of key/value pairs and another map for key/exception pairs. There are no tests that actually test the key/except

Re: Native client examples

On Fri, Oct 20, 2017 at 6:02 PM Dan Smith wrote: > However I do think we should be compiling (and hopefully running!) > these examples so that they don't rot over time. Especially since I > believe we are still evolving the native API with breaking changes and > have not actually managed a releas

Re: [jira] [Commented] (GEODE-3843) gfsh shutdown error message suggests non-existent option

...(continued) And perhaps the real point of the ticket was missed: there's no such option as "--shutdown-locators", so the message definitely needs a rewrite. On Mon, Oct 23, 2017 at 8:51 AM, Dave Barnes wrote: > Swapnil, > Are you suggesting that the gfsh shutdown command should shut down > l

Re: [jira] [Commented] (GEODE-3843) gfsh shutdown error message suggests non-existent option

Hi Dave, I got the same code review comment as your second point (—include-locators to be defaulted to true when the option is provided without value) and I am incorporating that comment. Thanks, Srikanth > On Oct 23, 2017, at 11:51 AM, Dave Barnes wrote: > > Swapnil, > Are you suggesting t

Re: [jira] [Commented] (GEODE-3843) gfsh shutdown error message suggests non-existent option

Swapnil, Are you suggesting that the gfsh shutdown command should shut down locators by default, not just data members? Sounds to me like a breaking change. If you area suggesting that the --include=locators option, when specified, should be accepted without the "=true" bit, which is now mandatory,

Build failed in Jenkins: Geode-nightly-flaky #157

See -- [...truncated 110.50 KB...] Download https://repo1.maven.org/maven2/com/fasterxml/jackson/module/jackson-module-paranamer/2.8.6/jackson-module-paranamer-2.8.6.jar Download http

Build failed in Jenkins: Geode-nightly #993

See Changes: [github] GEODE-3245: Flattening LuceneSerializer should support PDX values (#965) -- [...truncated 23.00 MB...] at io.netty.channel.AbstractChannelHandl