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-5884: Adding to function exception list if matching cause #2809

Merged
merged 1 commit into from Nov 8, 2018

Conversation

jhuynh1
Copy link
Contributor

@jhuynh1 jhuynh1 commented Nov 7, 2018

  • Add to exception list If the cause of the FunctionException
    is FunctionInvocationTargetException

Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

  • Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

  • Has your PR been rebased against the latest commit within the target branch (typically develop)?

  • Is your initial contribution a single, squashed commit?

  • Does gradlew build run cleanly?

  • Have you written or updated unit tests to verify your changes?

  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:

Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.

Copy link
Contributor

@nabarunnag nabarunnag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -378,6 +379,22 @@ public ExecuteRegionFunctionOpImpl(String region, Function function,
this.isHA = function.isHA();
}

// For testing only
ExecuteRegionFunctionOpImpl() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a way to test this without adding a new test hook to product code?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the problem is that the product wasn't quite testable in the first place. Yes we can mock around and use the existing constructors, but I think effort is better spent refactoring the class itself instead of munging tests.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll work on the refactoring as a separate commit. I think I'll modify the existing constructors (and new tests) to use a new constructor that assigns the final variables.

@jhuynh1 jhuynh1 merged commit d22e83e into apache:develop Nov 8, 2018
@jhuynh1 jhuynh1 deleted the feature/GEODE-5884 branch November 8, 2018 23:18
mcmellawatt pushed a commit that referenced this pull request Nov 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants