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

[ISSUE #3192] replace nacos-config module http client #3523

Merged
merged 7 commits into from
Aug 6, 2020
Merged

[ISSUE #3192] replace nacos-config module http client #3523

merged 7 commits into from
Aug 6, 2020

Conversation

Maijh97
Copy link
Collaborator

@Maijh97 Maijh97 commented Aug 5, 2020

Please do not create a Pull Request without creating an issue first.

What is the purpose of the change

refer: #3192

Brief changelog

Mainly replace the http client used by com.alibaba.nacos.config.server.service.notify.NotifyService and com.alibaba.nacos.config.server.service.notify.AsyncNotifyService .

Verifying this change

Simulate a three-node cluster locally, modify the configuration information on the console, Through debugging, it has been verified that the http client after replacement can work normally.

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

  • Make sure there is a Github issue filed 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 [ISSUE #123] Fix UnknownException when host config not exist. 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 integration-test in test module.
  • Run mvn -B clean package apache-rat:check findbugs:findbugs -Dmaven.test.skip=true to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.

String json = result.content;
SampleResult resultObj = JSONUtils.deserializeObject(json, new TypeReference<SampleResult>() {
if (result.ok()) {
return JSONUtils.deserializeObject(result.getData(), new TypeReference<SampleResult>() {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can unified json utils to Jackson util?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Ok, I will modify

}
AsyncNotifyCallBack asyncNotifyCallBack = new AsyncNotifyCallBack(task);
try {
restTemplate.get(task.url, header, Query.EMPTY, String.class, asyncNotifyCallBack);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should we modified this restTemplate.get method, if any error when execute get, call the callback.onError in the restTemplate.get rather than throw exception?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Ok, very good advice

@Maijh97 Maijh97 requested a review from KomachiSion August 6, 2020 02:17
@KomachiSion KomachiSion added this to the 1.4.0 milestone Aug 6, 2020
@KomachiSion KomachiSion merged commit a64a356 into alibaba:develop Aug 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants