[ 
https://issues.apache.org/jira/browse/GEODE-8700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17235562#comment-17235562
 ] 

ASF GitHub Bot commented on GEODE-8700:
---------------------------------------

pivotal-jbarrett commented on pull request #691:
URL: https://github.com/apache/geode-native/pull/691#issuecomment-730476801


   I am not sure I understand the motivation. Are you saying that you want to 
define the region in `cache.xml` and then later mutate it from the API? I am 
not sure how safe this would be given the general immutable nature of the 
region objects. What is the motivation to split the configuration this way. Our 
general recommendation is to use the API over the XML configuration anyway. The 
server is moving away from the XML configuration to cluster config and API 
config. The API provides the ability to provide an instantiated by the call 
instance of the resolver where the API must use "reflection" of sorts to new 
one up so context is disconnected with the application. 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Add the ability to change the partition resolver
> ------------------------------------------------
>
>                 Key: GEODE-8700
>                 URL: https://issues.apache.org/jira/browse/GEODE-8700
>             Project: Geode
>          Issue Type: New Feature
>          Components: native client
>    Affects Versions: 1.13.0
>            Reporter: Mario Salazar de Torres
>            Assignee: Mario Salazar de Torres
>            Priority: Major
>              Labels: pull-request-available
>
> *AS A* native client contributor
> *I WANT* to be able to mutate partition resolver
> *SO THAT* I don't need to create a shared library to specify one.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to