Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GEODE-10044: Allow FunctionAttributes update #930

Closed

Conversation

gaussianrecurrence
Copy link
Contributor

  • Moved FunctionExecution and OnRegionFunctionExecution into a separate
    file in order to improve readability and code maintenance.
  • Moved ChunkedFunctionExecutionResponse into a separate file in order
    to improve readability and code maintenance.
  • Introduced FunctionAttributes class to improve code readability.
  • Modified code to introduce the usage of FunctionAttributes.
  • Modified TcrMessageTest UT to work with the inclusion of
    FunctionAttributes.
  • Implemented a mechanism to cleanup function attributes.
  • A new exception FunctionAttributesMismatchException is added to be
    thrown whenever the server detects a mismatch for the function
    attributes.
  • Now whenever FunctionAttributesMismatchException is catched while
    executing a function, its function attributes are cleaned up, so the
    client will request an update the next execution.
  • Added a new IT to verify that chaging a function attributes on the
    fly is possible.

@gaussianrecurrence
Copy link
Contributor Author

The rationale behind this change is allowing the server function upgrade scenario, which was previously discussed in here: https://www.mail-archive.com/dev@geode.apache.org/msg26144.html

@lgtm-com
Copy link

lgtm-com bot commented Feb 23, 2022

This pull request introduces 1 alert when merging 2fad8a9 into 9aa78f4 - view on LGTM.com

new alerts:

  • 1 for Too few arguments to formatting function

 - Moved FunctionExecution and OnRegionFunctionExecution into a separate
   file in order to improve readability and code maintenance.
 - Moved ChunkedFunctionExecutionResponse into a separate file in order
   to improve readability and code maintenance.
 - Introduced FunctionAttributes class to improve code readability.
 - Modified code to introduce the usage of FunctionAttributes.
 - Modified TcrMessageTest UT to work with the inclusion of
   FunctionAttributes.
 - Implemented a mechanism to cleanup function attributes.
 - A new exception FunctionAttributesMismatchException is added to be
   thrown whenever the server detects a mismatch for the function
   attributes.
 - Now whenever FunctionAttributesMismatchException is catched while
   executing a function, its function attributes are cleaned up, so the
   client will request an update the next execution.
 - Added new ITs to verify that chaging a function attributes on the
   fly is possible.
 - Re-enabled and fixed TcrMessageTest.testConstructorExecuteFunction to
   ensure TcrMessageExecuteFunction is constructed as expected.
@gaussianrecurrence
Copy link
Contributor Author

I haven't had the time to work on this for a long time or I think I'll have the opportunity to in the near future, hence I am closing this PR, if anyone wants to tackle this issue can take it up from its latest state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant