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

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

gaussianrecurrence closed pull request #930: GEODE-10044: Allow 
FunctionAttributes update
URL: https://github.com/apache/geode-native/pull/930




> Allow for FunctionAttributes to be updated 
> -------------------------------------------
>
>                 Key: GEODE-10044
>                 URL: https://issues.apache.org/jira/browse/GEODE-10044
>             Project: Geode
>          Issue Type: Improvement
>          Components: native client
>            Reporter: Mario Salazar de Torres
>            Assignee: Mario Salazar de Torres
>            Priority: Minor
>              Labels: pull-request-available
>
> *AS A* geode-native contributor
> *I WANT TO* to reset function attributes on-the-fly whenever a function 
> attributes mismatch is detected on the client
> *SO THAT* FunctionAttributes can be changed during an upgrade scenario
> ----
> *Additional information.* Currently there is no exception being thrown from 
> the server whenever a function attributes missmatch is detected. Instead, a 
> function execution error is send to the client. So it remains to be tackled 
> how the mismatch is going to be detected on the client side.
> *Also, for additional context,* this feature is designed in order to fulfill 
> the following upgrade scenario:
>  # A server function called ExampleFunction is deployed inside a cluster. 
> This server function is defined with isHA=false
>  # Function is executed several times from the client.
>  # After some time, a new version of ExampleFunction jar is deployed. The new 
> version of the server function is defined with isHA=true
>  # After updating the server function, executions for this function inside 
> the client should fail at most once, and after that, execute smoothly with 
> the new function attributes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to