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-6174: change refid to type and make the default type to be PART… #3130

Merged
merged 1 commit into from Jan 29, 2019

Conversation

jinmeiliao
Copy link
Member

…ITION

Co-authored-by: Peter Tran ptran@pivotal.io

  • change refid to type for better UX
  • add a common config validator interface and use that to validate RegionConfig

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.

@jinmeiliao
Copy link
Member Author

@onichols-pivotal @Petahhh

…ITION

Co-authored-by: Peter Tran <ptran@pivotal.io>

* change refid to type for better UX
* add a common config validator interface and use that to validate RegionConfig
Copy link
Contributor

@onichols-pivotal onichols-pivotal left a comment

Choose a reason for hiding this comment

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

Looks good and all tests are passing. Do we need any additional tests here to cover empty strings or whitespace strings (vs missing region name entirely)? Do we need additional tests to cover invalid region types? What about empty or whitespace region types, are those error or default to PARTITIONED? Do we need any tests here of region names containing punctuation or weird characters or newlines?

@jinmeiliao
Copy link
Member Author

thanks! there is validation on the invalid region types. As to invalid region names, we should have a story to cover that. I've mentioned this to @aditya87 before, but he prefer not to include it just yet.

@jinmeiliao jinmeiliao merged commit c97edf9 into apache:develop Jan 29, 2019
@jinmeiliao jinmeiliao deleted the type branch January 29, 2019 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants