This reminds me of this bug: https://issues.apache.org/jira/browse/GEODE-3460 Although, the comment says that the bug is fixed.
Can you put the jar on the classpath and then create the region using gfsh to help narrow down if the issue is with deploying the jar? Thanks! On Tue, Jan 2, 2018 at 2:17 PM Mark Secrist <[email protected]> wrote: > 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: > > 1. Deployed jar file using 'deploy --j' [success], created region > using command 'create region --name=BookOrder --type=PARTITION > --partition-resolver=....' [Failed] > - io.pivotal.bookshop.partitions.CustomerPartitionResolverPartitionResolver > is an invalid Partition Resolver > 2. Configured region from gfsh using StringPrefixPartitionResolver for > partition resolver [Success] > 3. Un-deployed jar file. Used traditional classpath and XML > configuration [Success] > 4. Deployed jar file using 'deploy' [Success] Configure region with > partition resolver in XML file [Success] > > If it wasn't for the fact that attempt #2 was successful, I'd believe that > maybe it wasn't possible to use the gfsh command to configure a region with > partition resolver. I'm frankly at a loss to understand why this wouldn't > work. > > This is using GemFire 9.2.1 bits by the way... > > Thoughts? > > -- > > *Mark Secrist | Director, **Global Education Delivery* > > [email protected] > > 970.214.4567 Mobile > > *pivotal.io <http://www.pivotal.io/>* > > Follow Us: Twitter <http://www.twitter.com/pivotal> | LinkedIn > <http://www.linkedin.com/company/pivotalsoftware> | Facebook > <http://www.facebook.com/pivotalsoftware> | YouTube > <http://www.youtube.com/gopivotal> | Google+ > <https://plus.google.com/105320112436428794490> >
