You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dubbo.apache.org by li...@apache.org on 2019/07/15 05:48:53 UTC

[dubbo-website] branch master updated: Fix typo (#429)

This is an automated email from the ASF dual-hosted git repository.

lixiaojie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/dubbo-website.git


The following commit(s) were added to refs/heads/master by this push:
     new cf9f34c  Fix typo (#429)
cf9f34c is described below

commit cf9f34c23340c5396a2f0821a381ee586553d0d5
Author: 天璇 <ca...@126.com>
AuthorDate: Mon Jul 15 13:48:49 2019 +0800

    Fix typo (#429)
---
 docs/zh-cn/user/demos/routing-rule.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/zh-cn/user/demos/routing-rule.md b/docs/zh-cn/user/demos/routing-rule.md
index b3eb38e..8472ccf 100644
--- a/docs/zh-cn/user/demos/routing-rule.md
+++ b/docs/zh-cn/user/demos/routing-rule.md
@@ -239,7 +239,7 @@ RpcContext.getContext().setAttachment(Constants.REQUEST_TAG_KEY,"tag1");
 
 #### 降级约定
 
-1. `request.tag=tag1` 时优先选择 标记了`tag=tag1` 的 provider。若集群中不存在与请求标记对应的服务,默认将降级请求 tag为空的provider;如果要该表这种默认行为,即找不到匹配tag1的provider返回异常,需设置`request.tag.force=true`。
+1. `request.tag=tag1` 时优先选择 标记了`tag=tag1` 的 provider。若集群中不存在与请求标记对应的服务,默认将降级请求 tag为空的provider;如果要改变这种默认行为,即找不到匹配tag1的provider返回异常,需设置`request.tag.force=true`。
 
 2. `request.tag`未设置时,只会匹配tag为空的provider。即使集群中存在可用的服务,若 tag 不匹配也就无法调用,这与约定1不同,携带标签的请求可以降级访问到无标签的服务,但不携带标签/携带其他种类标签的请求永远无法访问到其他标签的服务。