Geode unit tests completed in 'release-1.5.0/DistributedTest' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0/jobs/DistributedTest/builds/4

Re: Starter tickets

Hi all, I consolidated all labels mentioned above under "starter" and "starter++" and updated the how to contribute page accordingly. At this point we have 21 and 3 tickets for those labels. Especially the number of "starter" t

Geode unit tests completed in 'develop/DistributedTest' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/183

Re: FunctionService Proposal

I did not know that! And then, yes, onRegion is much better. On Wed, Mar 7, 2018 at 2:43 PM, Dan Smith wrote: > > If we're not opposed to descriptive verbosity, I might prefer > "onServersHostingRegion" more than "onRegion". > > onRegion does not really mean "on the servers hosting region XXX".

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

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

Re: FunctionService Proposal

> If we're not opposed to descriptive verbosity, I might prefer "onServersHostingRegion" more than "onRegion". onRegion does not really mean "on the servers hosting region XXX". It only executes on a subset of the servers, potentially with retries, until it has covered that entire dataset once. So

Re: FunctionService Proposal

+1 for iteration towards better single responsibility design and more easily-digestible classes. Regarding method names, I think that there would be some good utility in having "onGroup" methods, as well. If we're not opposed to descriptive verbosity, I might prefer "onServersHostingRegion" more t

Re: FunctionService Proposal

I agree with Dan here. The C++ client took a stab at making ExecutionService less static but didn't go this far. Rather than pull Cache out of the either it is passed into each of the static factory methods, wither as a Region, Pool or Cache itself. I like propose to add Cache::getFunctionService t

Re: FunctionService Proposal

Hi Udo, +1 for making the function service not static and spitting it into client and server FunctionService objects! We do have Cache and ClientCache right now. So I would recommend this API rather than putting two methods on Cache. Cache is already the the server side API. Cache { ServerFunc

Geode unit tests completed in 'develop/FlakyTest' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/290

Re: Simple serialize/deserialize test using DataSerializers

BlobHelper ends up calling DataSerializer.writeObject. The nice thing about BlobHelper is can call org.apache.geode.internal.util.BlobHelper.serializeToBlob(Object) and org.apache.geode.internal.util.BlobHelper.deserializeBlob(byte[]) without needing to write any of your own code the create the inp

Broken: jinmeiliao/geode#249 (clusterConfig - b18bf0d)

Build Update for jinmeiliao/geode - Build: #249 Status: Broken Duration: 20 minutes and 49 seconds Commit: b18bf0d (clusterConfig) Author: Jinmei Liao Message: add tests View the changeset: https://github.com/jinmeiliao/geode/compare/4255afe11efe^...b18bf0dbf

Re: [PROPOSAL]: configure pdx command mandatory flags

I think the configure pdx command also lets you configure persistence or read-serialized for pdx, right? So some people might not be using either of those auto-serializable-classes options. -Dan On Wed, Mar 7, 2018 at 4:13 AM, Ju@N wrote: > Hello all, > > While working on a fix for GEODE-4771

Re: Simple serialize/deserialize test using DataSerializers

DataSerializer.writeObject, if you want a public API. -Dan On Wed, Mar 7, 2018 at 11:20 AM, Anthony Baker wrote: > BlobHelper? > > > On Mar 7, 2018, at 10:13 AM, Kirk Lund wrote: > > > > Does anyone know what Geode API(s) I should use instead of Apache Geode > > SerializationUtils to change th

Re: Simple serialize/deserialize test using DataSerializers

BlobHelper? > On Mar 7, 2018, at 10:13 AM, Kirk Lund wrote: > > Does anyone know what Geode API(s) I should use instead of Apache Geode > SerializationUtils to change the following test to use Geode > DataSerializers? > > @Test > public void serializesAndDeserializes() throws Exception { > Par

FunctionService Proposal

Hi there Apache Dev's, Please look at the proposal to improve the FunctionService and remove the static invocation of it from within the Cache. https://cwiki.apache.org/confluence/display/GEODE/Function+Service+Refactor+-+Removal+of+static-ness+and+splitting+of+client+and+server-side+FunctionS

Simple serialize/deserialize test using DataSerializers

Does anyone know what Geode API(s) I should use instead of Apache Geode SerializationUtils to change the following test to use Geode DataSerializers? @Test public void serializesAndDeserializes() throws Exception { PartitionRegionConfig config = new PartitionRegionConfig(prId, path, partitionAtt

Re: jdbc schema is missing on apache

You need to add it to the geode-site repo on the asf-site branch: ~/code/geode-site (asf-site)$ find . -name *.xsd ./schema/lucene/lucene-1.0.xsd ./schema/cache/cache-1.0.xsd Anthony > On Mar 7, 2018, at 10:08 AM, Kirk Lund wrote: > > Yep, I believe it should exist. Any ideas where and how t

Re: jdbc schema is missing on apache

Yep, I believe it should exist. Any ideas where and how to copy it from Geode src so that it appears at http://geode.apache.org/schema/jdbc? On Wed, Mar 7, 2018 at 9:59 AM, Jinmei Liao wrote: > I am looking at some xml that specifies jdbc connector, the namespace is > pointing to " > > http://ge

jdbc schema is missing on apache

I am looking at some xml that specifies jdbc connector, the namespace is pointing to " http://geode.apache.org/schema/jdbc";, but that url is missing on apache website. Is it supposed to be there? http://geode.apache.org/schema/cache"; xmlns:jdbc="http://geode.apache.org/schema/jdbc"; xmlns:

Re: Next release: 1.5.0

Thanks, John. I did a round of updates for this release and expect we can continue do this in subsequent releases. Bundled dependencies: Commons Lang is at *3.7;* Geode is at 2.6 Log4j is at *2.10.0*; Geode is at 2.8.2 Netty is at *4.1.22.Final*; Geode is at 4.1.21.Final

[PROPOSAL]: configure pdx command mandatory flags

Hello all, While working on a fix for GEODE-4771 I've came across a non-reported bug: the configure pdx command fails when no parameters are specified, even when we state in the User Guide