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

[SCB-352] refactor QpsControllerManager, support operation level qps controll on provider side #577

Merged

Conversation

yhs0092
Copy link
Member

@yhs0092 yhs0092 commented Mar 7, 2018

Follow this checklist to help us incorporate your contribution quickly and easily:

  • Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean install to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

Refactor QpsControllerManager and support operation level qps flow control on provider side.
https://issues.apache.org/jira/browse/SCB-352

compile_warning

@yhs0092 yhs0092 changed the title SCB-352 refactor QpsControllerManager, support operation level qps controll on provider side [SCB-352] refactor QpsControllerManager, support operation level qps controll on provider side Mar 7, 2018
@coveralls
Copy link

coveralls commented Mar 7, 2018

Coverage Status

Coverage increased (+0.05%) to 87.235% when pulling f0a54d3 on yhs0092:support_provider_operation_level_flow_control into e1137b4 on apache:master.

// create "microservice"
createQpsControllerIfNotExist(qualifiedNameKey.substring(0, qualifiedNameKey.indexOf(SEPARATOR)));
// create "microservice.schema"
createQpsControllerIfNotExist(qualifiedNameKey.substring(0, qualifiedNameKey.lastIndexOf(SEPARATOR)));
Copy link
Contributor

Choose a reason for hiding this comment

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

We need to add naming conventions to docs of service name, schema and operation

Copy link
Member Author

Choose a reason for hiding this comment

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

OK. I will add naming convention instructions in gitbook later.

@yhs0092 yhs0092 force-pushed the support_provider_operation_level_flow_control branch from bc04967 to f0a54d3 Compare March 9, 2018 07:07
@yhs0092 yhs0092 force-pushed the support_provider_operation_level_flow_control branch from f0a54d3 to 2e40314 Compare March 12, 2018 03:07
@liubao68 liubao68 merged commit f0fae33 into apache:master Mar 14, 2018
@yhs0092 yhs0092 deleted the support_provider_operation_level_flow_control branch July 23, 2018 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants