Re: Using partition resolver via gfsh command vs XML config

The release branch for 1.3 was cut before the date mentioned by Jinmei, so the fix has not been released yet. Can you please try again against a build on develop? We hope to have a RC of 1.4 out soon. On Wed, Jan 3, 2018 at 1:23 PM Kirk Lund wrote: > According to the context

Re: Using partition resolver via gfsh command vs XML config

According to the context of where that message is used, the specified className is blank. private static Class forName(String className, String neededFor) { if (StringUtils.isBlank(className)) { throw new IllegalArgumentException(CliStrings

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

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

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

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

Build failed in Jenkins: Geode-nightly #1062

See Changes: [github] GEODE-4170: Index docs are easier to locate (#1208) [bschuchardt] GEODE-4168 Can't get json object stored as PDX using the new protocol [bschuchardt] GEODE-4092 New protocol does not have

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

See Changes: [huynhja] GEODE-4008: Added serialVersionUID to FunctionAdapter (#1119) [github] GEODE-4146: fix XmlEntity matching for JdbcConnectorService (#1215) [bschuchardt] GEODE-4176 locator creates

Using partition resolver via gfsh command vs XML config

Hi all, I'm curious why I'd be running into issues using the gfsh command to create a region using a partition resolver, yet can do so using XML configuration. I've tried a couple of different combinations. I have a partition resolver class that is packaged in a JAR file. I tried the following:

Failed: apache/geode#5370 (micrometer - cfcc175)

Build Update for apache/geode - Build: #5370 Status: Failed Duration: 17 minutes and 3 seconds Commit: cfcc175 (micrometer) Author: Udo Kohlmeyer Message: Changing counter to gauge View the changeset:

Errored: jinmeiliao/geode#157 (deployJar - ccd244b)

Build Update for jinmeiliao/geode - Build: #157 Status: Errored Duration: 20 minutes and 34 seconds Commit: ccd244b (deployJar) Author: Jinmei Liao Message: GEODE-4131: review changes View the changeset:

Re: PRs should always include tests

This is a very important question and it really showcases the biggest problem facing Apache Geode in my opinion. If existing tests don't fail when you change the code, then that's a sign of a serious problem with our tests. Most likely the test isn't actually covering the code and all of its