[
https://issues.apache.org/jira/browse/GEODE-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933597#comment-15933597
]
ASF GitHub Bot commented on GEODE-2231:
---------------------------------------
Github user karensmolermiller commented on the issue:
https://github.com/apache/geode-examples/pull/3
Geode devs - this partitioning example has been extensively revised based
on the reviews. Please review again to see if it is time to merge this example
to develop.
A future task that this example (and other examples) will need is a way to
identify a versioned jar file for inclusion on the classpath when starting up
locator/server members. The gradle.properties file includes a version number
(that will go with a release), so at issue is how to acquire that version
number from within bash scripts and such (outside of a gradle build). It'd be
best to change exactly one spot when changing the version number, instead of
hunting down all places where it is embedded. One floated idea was to just use
whatever JAR file ended up in the build/libs directory. We could do that, but
it isn't very robust.
> Create new partitioning example
> -------------------------------
>
> Key: GEODE-2231
> URL: https://issues.apache.org/jira/browse/GEODE-2231
> Project: Geode
> Issue Type: Improvement
> Components: docs
> Reporter: Karen Smoler Miller
> Assignee: Karen Smoler Miller
> Priority: Minor
>
> Add a new example to the geode-examples that demonstrates partitioning.
> The example will use the same structure as the replicated example, starting 2
> servers that host a partitioned region (with no redundant copies). Run the
> producer to populate the region. Run the consumer to see the contents of the
> region. Then, stop one of the servers and run the consumer again to notice
> that only roughly half (with 2 servers and hopefully a reasonable hash) of
> the entries are present.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
