Skip to content

[DUBBO-3650]: Dubbo 2.7.0的provider无法指定客户端默认async#4058

Merged
chickenlj merged 1 commit intoapache:masterfrom
beiwei30:issue3650
May 15, 2019
Merged

[DUBBO-3650]: Dubbo 2.7.0的provider无法指定客户端默认async#4058
chickenlj merged 1 commit intoapache:masterfrom
beiwei30:issue3650

Conversation

@beiwei30
Copy link
Copy Markdown
Member

What is the purpose of the change

fix issue #3650

Brief changelog

XXXXX

Verifying this change

XXXXX

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

  • Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
  • Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
  • Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
  • If this contribution is large, please follow the Software Donation Guide.

@chickenlj chickenlj self-requested a review May 15, 2019 04:25
Copy link
Copy Markdown
Contributor

@chickenlj chickenlj left a comment

Choose a reason for hiding this comment

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

LGTM.

The async property on both sides controls the request behavior on consumer side. When async is absent on consumer side, use the value from provider.

@chickenlj chickenlj merged commit ae669ea into apache:master May 15, 2019
@beiwei30 beiwei30 deleted the issue3650 branch May 15, 2019 04:38
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.

2 participants